Troubleshooting & FAQ
The workers fail with ERR_CONNECTION_RESET
The proxy is unreachable, or the local relay is not ready. Botify detects this case and does not flag the account (it is not its fault) — it retries with another proxy. Check that your proxies are online and that they really are SOCKS5.
Botify is “not responding” / the VPS is sluggish
Typical symptom of CPU saturation (too many Chrome instances at once). Solutions:
- Reduce the number of workers until it is stable.
- GPU acceleration is already disabled (good for VPS with no GPU).
- Botify protects itself (CPU priority + spawn throttling), but keep some headroom.
My machine isn’t receiving any accounts
Check three things: (1) your CapSolver key is set and funded (Settings → CapSolver) — with no key, no creation is requested for your machine (red alert); (2) your “Accounts to create per day” cap (Accounts page) isn’t 0 and isn’t already reached; (3) your proxies have free slots. See Distribution.
How many accounts per proxy?
Recommended realistic density: a few accounts per proxy (few accounts per IP, like a household).
New accounts take a while to start streaming
That is normal: a new account starts in warmup (the first few days) — it listens to popular playlists to build a credible history before playing your tracks.
Does a banned/expired account stay around?
No: banned or expired accounts are deleted automatically (and reported on Discord if configured) to free up the slot. Suspect accounts are kept and re-tested.
Do I need to install a creation machine?
No. Account creation is centralized and automatic: your streaming machines receive accounts on their own, delivered encrypted. You only install streaming, on a VPS.
Where can I see real-time activity?
The « Activité » (Activity) page: for each worker, the account, the track currently playing and the timer.