When the proxy will not connect

This page covers errors where your request does not get through at all: refused connections, timeouts and TLS errors. For 407 and 403 replies, see What a 407 or 403 message means.

Start with one clean test

Test from the same machine that runs your job, with curl and the -v option:

curl -v -x "http://USERNAME:PASSWORD@HOST:PORT" https://api.ipify.org

Use the host, port, username and password from the proxy's page in the dashboard. If this prints an IP address, the proxy works, and the problem is in your tool's settings.

Common errors

Failed to connect, or connection refused (curl exit code 7)

Nothing answered at that host and port from where you are.

1. Copy the host and port again from the proxy's page.
2. Check that a firewall on your network or server allows outgoing connections to that port.
3. Check that the proxy is still Active in the dashboard.

Connection timed out (curl exit code 28)

The proxy or the website did not answer in time.

1. Try once more. A connection can be slow now and then.
2. Give your tool a longer timeout. In curl, use --connect-timeout and --max-time.
3. If every request times out, check Checking whether something is down.

An SSL or TLS error (curl exit code 35)

Your proxy address probably starts with https://. Write it with http://. Your traffic to https websites is still encrypted inside the tunnel.

CONNECT tunnel failed, response 407 (curl exit code 56)

The proxy did not accept the login. Go to What a 407 or 403 message means.

SOCKS errors, or no reply at all

The protocol in your tool may not match the proxy. See Using SOCKS5 instead of HTTP.

Still not working?

Write to support@proxypanda.io with the full curl -v output. Before you send it, remove your password and delete any line that contains Proxy-Authorization, because that line carries your login in encoded form. How to reach us, and what to include lists what else helps.