FAQ

I clicked OK on the update prompt and nothing happened — is it frozen?

No. It is downloading the new build (about 35MB). Before 2.0.46 nothing was shown during the download, so on a slow connection it looked frozen.

From 2.0.46 you get a “Downloading the new version… N%” bar at the top of the screen. Meanwhile keep using the tool normally — import accounts, change settings, run automation. It only installs once the download finishes, and if automation is running it waits for the run to end.

The image pack download keeps timing out part-way?

Fixed in 2.0.41. The app used to put a 10-minute limit on the whole download. The pack is 373MB, so any connection slower than roughly 0.6 MB/s got cut off mid-way — typically around 30%. That was our limit, not a fault on your line.

From 2.0.41 the download only stops if the network is silent for 90 seconds, it streams straight to disk (much less memory), and most importantly it resumes — if it breaks, pressing Download again continues from where it stopped instead of starting over.

On an older build: just press Download again, or update first and then download.

The Start button is greyed out?

It means a required update is pending. The app downloads it in the background — just close and reopen and the button works again. Hovering over the button shows the reason.

From 2.0.39 the app blocks the run up front instead of letting you click and then quietly doing nothing. This also prevents a run being cut off half-way when the pending update installs and restarts the app.

From 2.0.44, if automation is running the update does not install immediately — it waits for the run to finish, so your run is never cut off mid-way.

Clicking Delete / Rename / Reset does nothing?

Fixed in 2.0.38. Buttons that ask for confirmation — delete accounts, delete group, rename group, clear task results, clear tags, reset the seeding round, change a group's mode after it has coverage — used the browser's own dialog, which the application window cannot display. The result: nothing happened and no error was shown.

From 2.0.38 these buttons show an in-app confirmation box (destructive actions in red). If a button seems dead on an older build, update to the latest version.

The app suddenly asks for the license key again?

Fixed in 2.0.38. Before that, a temporary problem on the license server (a restart, a dropped connection, a corporate network blocking the request) was misread as “licence revoked”, and the stored key was deleted — so you had to type it in again even though nothing was actually wrong.

From 2.0.38 the app tells the two situations apart: it only clears the key when the server gives a definite answer (expired or genuinely blocked). When the server simply cannot be reached, the key is kept and the app keeps running on its grace period. If you are still asked for the key, the licence really has expired or been blocked — contact your seller.

The most common questions when operating GAIO Tool. Where an answer points to a specific screen (Dashboard, Logs, License…), open the matching section of this manual for the full detail.

Does the app auto-update?

Yes. The server sets a minimum version (minVersion); if your running build is older, an orange banner appears at the top of the window reading "A new version is required…" and the updater downloads the new build automatically. While that banner is up, automation is blocked — this is why some old (or tampered) builds won't run. After the download, you may need to restart the app to apply it. If the admin sets minVersion = 0, the gate is off.

Do I lose my key when I change PCs?

The license is tied to each machine's Machine ID (the first 20 characters, shown in the License modal). A new PC has a different Machine ID, so the old key won't activate automatically. On the new PC, open the License modal, send your new Machine ID to the seller to be re-issued / transferred. Don't share your key with another machine — activation requires the license server to be reachable (offline attempts show "Cannot reach license server").

How many threads / how many accounts per run?

There are two different limits. The number of parallel threads (how many browsers run at once) is set in the Automation tab — pick it to match your machine's CPU and RAM. The max accounts per run is set by your license (the Max accounts per run field in the License modal). If you select more than that and click Start, a warning modal appears: only the first N accounts run and the rest are skipped — and this hard cap is always enforced by the orchestrator even if you click Continue.

Why turn on "Change Language [En]"?

Automation finds Google's buttons and menus by their English labels. If an account's Google interface is in another language, the selectors won't match and steps get silently missed. The change-language task sets each account's Google interface to English so every later step finds the right button. (Note: the EN / VI buttons at the top-right of the header are different — they change the language of the GAIO app itself, not the Google account.)

Are the sample content pools safe to share?

The sample content that ships with the installer (default content pools, names, avatars) is generic and safe to share. But once you've loaded your own real data (channel names, emails, niches, video IDs…), that file is no longer safe to send to anyone — it exposes your operation's identity. Rule of thumb: sharing the original samples is fine; sharing a pool you've filled with real data is not.

The image pack didn't finish downloading?

On the first run, the installer ships without the image pack, so the app downloads it and shows an indigo banner reading "Downloading the image pack for the first time — you can keep using the tool." This banner is non-blocking — you can use every feature while it downloads, and it disappears when finished. If it never completes, check the connection to the content server (the banner only runs when the server is reachable); restart the app to let it resume.

Just created profiles and now they won't start?

You do not need to open each profile by hand. Re-verified on the current GPMLogin build: profiles made with Create missing profiles start straight from the app, the browser comes up and accepts automation normally.

A profile that fails to start is almost always a proxy problem, not a profile problem. GPMLogin says “Cannot connect to proxy” and the account shows Proxy Dead.

What to do, in order:

1. Check whether the proxy is alive — expired or out-of-bandwidth proxies are by far the most common cause. Test it in a browser or a proxy checker before suspecting the software.
2. Replace the proxy for the failing accounts (select them → Actions → Set Proxy), then run again.
3. If an account has no proxy and still fails, open that profile once inside the GPMLogin app — its error message names the cause more precisely.

An account got Verify / Disabled — what now?

Verify (amber card) means Google is asking to verify — usually phone, a challenge, or a captcha. This needs manual handling (a real phone number); automation can't clear it. Disabled (red card) means Google has locked the account; re-running does not recover it — the only path is an appeal, and success rates are typically low. When Disabled climbs across runs, stop and inspect your proxies, behavior, and frequency before continuing — that's the root cause, not the individual accounts.

My proxy keeps failing?

Check in order: (1) the proxy is still alive and in the right format host:port or host:port:user:pass; (2) the IP has a good reputation (not blacklisted) — prefer residential / ISP / mobile; (3) if the proxy egresses over IPv6, the target site must have an AAAA record or it's unreachable (a commonly-missed cause for non-Google sites); (4) keep each account's proxy region stable — a sudden region change makes Google revoke the session (Signed out). A proxy's address doesn't tell you its real egress; ask api6.ipify.org through the proxy itself to see the exit IP.

Where is my data stored?

All accounts, statuses, results and settings are stored locally in a SQLite database on your machine (nothing is pushed to a cloud). Browser profiles (fingerprints, cookies, sessions) are managed separately by GPMLogin. Because the data lives on your machine, back it up before reinstalling the app or switching machines, and remember that changing machines changes your Machine ID (see the key question above).