Error 522

​

Why this happens

• The target server is overloaded or temporarily unavailable.
• The target uses Cloudflare or a similar CDN that is rejecting the connection.
• The target is rate-limiting or blocking incoming connections based on IP reputation, volume, or fingerprinting.
• A firewall or security rule on the target is dropping the request before it completes.
• DNS resolution delays or network congestion between the exit node and the target.

​

What you can try

• Retry the request. Transient 522 errors often resolve on a subsequent attempt with a different exit node.
• Rotate your session. If you are using sticky sessions, switch to a rotating session or start a new sticky session to get a different IP.
• Try a different location. Some targets respond differently depending on the geographic origin of the request.
• Adjust your geo-targeting parameter.
• Reduce request frequency. If you are sending a high volume of requests to the same target, slow down or add delays between requests.
• Check the target directly. Verify that the target website is online and reachable outside of the proxy to rule out a general outage.
• Switch protocols. If using HTTP, try HTTPS (or vice versa) to see if the target handles one better than the other.