Troubleshooting
Diagnose failed visits, missing analytics data and proxy problems.
Diagnose failed visits, missing analytics data and proxy problems.
- Traffic is not showing in Google Analytics Check the GA4 Realtime report first, not the standard reports, which lag by up to 48 hours. The three most common causes…
- Proxies keep failing or the success rate is low Free public proxies die constantly, so a success rate of 20 to 40 percent is normal for them. Shorten the Re-check proxies…
- "Browser executable not found" The engine your project is set to has no browser installed. Open the Engines panel and install or reinstall that engine, or…
- License activation failed Most activation failures are a copy-paste problem, a firewall blocking overrider.io, or a key already bound to a different computer. Licenses bind…
- Antivirus is blocking OverRider Browser automation looks like malware to heuristic scanners, so false positives are common. Add the OverRider installation folder and its browser engines…
- High CPU or memory use Each simultaneous visit is a full browser process, so memory scales directly with thread count. Lower the threads, and turn off Load…
- Traffic continued after I stopped a project OverRider ends its browser processes when you stop a project, so traffic stops within moments. It has no cloud component and no…
- Visits finish too quickly A Visits Based project runs flat out until it reaches the target count — there is no pacing. To slow it down,…
No matching articles.