GameLoop / TAC login fails with 'Domain is empty' error
When opening GameLoop / TAC, or signing into CODM / PUBG Mobile through the emulator, the login flow fails immediately with the message "Domain is empty". The error blocks all online matchmaking — offline single-player content still works.
Common triggers reported in the community:
- Sign-in attempt from regions where the emulator's CDN routing is restricted (UAE, certain MENA countries, parts of Asia, India).
- Whether the user has VPN ON or OFF doesn't matter — the failure persists either way.
- Clearing the GameLoop cache by itself doesn't fix it.
- Reinstalling the emulator doesn't fix it.
- The error message wording varies slightly: "Domain is empty", "no globel" / "no global" warning, login screen with no proceed button.
Solutions
solution #518
Switch the GameLoop region selector to "Global" at login. On the Smart Tool's Game Version dropdown — and on GameLoop's own login screen — pick Global instead of Garena or VNG. Countries missing from CDN routing (e.g., UAE) cause the empty-domain error when the country dropdown isn't matched against the CDN's allowlist.
Confirmed fix in multiple reports — caesarsalad in UAE finally got "holy shit its working" after switching to Global.
solution #519
Clear GameLoop cache, then switch region. If "Global" alone doesn't unstick the login:
- GameLoop settings → Engine → Clear Cache
- Restart GameLoop
- On the login screen, pick Global
solution #520
Switch your DNS to Cloudflare 1.1.1.1. Some ISPs route emulator traffic through DNS chains that drop the CDN handshake silently. Per ӃryptønPsychø's tip: install the Cloudflare 1.1.1.1 app or set DNS manually to 1.1.1.1 / 1.0.0.1 in Windows network settings. Reboot, then retry.
solution #521
Run GameLoopHub's COD Mobile Smart Tool before launch. The tool resets stale GameLoop config / session state that occasionally triggers the domain-empty error after region switches. Click Apply FPS + Apply Keymap + Restore DB, then launch via the tool's "Launch CODM" button. Open Smart Tool →
solution #522
Connect to a US-server VPN if region + DNS fixes don't help. A subset of regions can't reach the CDN even with Global selected. Connect to any reputable VPN with a US exit node, then retry login. Once you're logged in, you can disconnect the VPN — the session token persists.
Comments (0)
Sign in to_leave_comment