Most failures fall into three categories. Identify which one you have before changing any settings.
01Authentication errors
Credentials contain a trailing space from copy-paste
IP whitelisting is enabled but your egress IP changed
The line has expired — check its status in the console
02Timeouts
Timeouts usually mean the request never reached the proxy. Test with curl -v to see whether the connection is established, then confirm the port matches the protocol.
03Connection refused
A refused connection almost always means the wrong port or a line that is not yet provisioned. Wait a minute after purchase and re-check the line details.
Fastest checkRun the same curl command with and without the proxy. If the direct request also fails, the problem is your local network, not the proxy.
FAQFrequently asked
How soon can I use an IP after purchase?
Lines are generated in about 1–3 minutes. Check "My IPs" in the console for the assigned address.
Which protocols are supported? Which one should I use?
Both HTTP and SOCKS5 are supported. For anti-detect browsers and desktop clients, SOCKS5 has better compatibility.
What happens when a line expires?
Forwarding stops immediately. Enable expiry reminders and renew in advance — the IP stays the same after renewal.
Can I use the same line for several accounts?
Technically yes, but it is not recommended. Sharing one IP increases the risk of linking accounts. Use a dedicated static IP per account or profile.
Do you support IP whitelisting?
Yes. You can authenticate by username and password or by whitelisting your egress IP. Whitelisting suits servers with a fixed IP.
Can one environment use the same proxy across sessions?
Yes for static residential lines. Rotating lines require a sticky session token to keep the same exit IP across requests.