Proxy setup
HTTP 522 connection timed out
HTTP 522 is commonly returned by CDN edges when they cannot finish a connection to the origin. Through a proxy, it can also mean your client never completed the tunnel in time.
Split the path
Test example.com through the proxy. If that works, the proxy is up and the destination or its CDN is slow or blocking. If example.com also times out, check HOST, PORT, and local firewall.
Timeouts
Increase the client timeout for a single diagnostic request. Do not hide a persistent 522 by retrying forever — fix the product, location, or target.
Protocol
Some tools default to SOCKS when you needed HTTP, or the reverse. Match the dashboard protocol to the client setting.
Instructions
1. Reproduce with curl
Add --max-time 30 and -v. Read whether the failure is resolving HOST, connecting to PORT, or waiting on the origin.
2. Change only one variable
Try another location, then another product, keeping the URL fixed.
3. Check the origin without assumptions
If the site is down globally, a proxy will not repair it.
curl -v --max-time 30 -x http://USERNAME:PASSWORD@HOST:PORT https://example.comRelated sections
How to use cURL with a Premip proxy
The fastest way to prove credentials work before you configure a larger client.
How to check your proxy address
Confirm credentials and the exit IP before you put a job into production.
TCP/IP fingerprints and proxy choice
If a site is sensitive to hosting stacks, switch product — do not try to spoof the TCP stack.
All about datacenter proxies
Static hosting IPs for speed and volume when the destination does not require consumer networks.
If you still need help, message us on Telegram or email. Include your account email and, if you have one, your order ID.
Message us
Reach support on Telegram, email, phone, or the contact form. Include your account email and, if you have one, your order ID.