Fix Proxy Connection Errors: 407, Timeout and DNS

Start with the connection details

Check that the order is complete and the rental is still active. Compare protocol, host, port, username and password with the delivered details, including unwanted spaces from copying.

Test one proxy against one destination and change a single variable at a time. Importing a larger list before fixing the first connection makes diagnosis harder.

HTTP 407: proxy authentication

A 407 response means the proxy requires authentication or did not accept the authentication supplied. Use the proxy username and password in the correct fields, not the destination account credentials.

Confirm that the application supports the required authentication method. SOCKS clients may report a different error rather than HTTP 407. Share the error text with support, not the password.

Timeout versus connection refused

A timeout means the operation did not finish within the allowed time. “Connection refused” is a different result and can indicate that the requested port is not accepting the connection.

Check the address, port, local network and service status. If a firewall or managed network is involved, ask the network administrator. Use bounded test times rather than rapid repeated retries.

DNS resolution and address families

Distinguish failure to resolve the proxy hostname from failure to resolve the destination. Check whether your client resolves names locally or asks the proxy to do so.

For IPv6, test the exact destination endpoint. The main website, login host and API may not all have the same network support.

Read the destination response separately

Determine whether the response came from the proxy or the destination. A destination’s 403 response can relate to authorization, request structure or service policy, even when the proxy connection succeeds.

For a 429 response, follow the destination’s documented request limits and retry timing. Buying another IP is not a substitute for complying with those limits.

Prepare a useful support request

Provide a concise, redacted report. Remove passwords, access tokens and private customer data from screenshots and logs.

• Order or connection identifier.
• Application version and selected protocol.
• Exact error message or HTTP status.
• Test date, time and destination address.
• Whether the same test works in another compatible client.

Common questions

Should I buy a new proxy after a 407 error?

First check the proxy credentials and authentication method. A new address will not fix incorrectly entered credentials.

Why does one website work while another fails?

Destinations can differ in network support, authorization and request policies. Compare the actual error and endpoint.

Should I send my proxy password to support?

Do not include passwords in a general support report. Use the order identifier and a redacted error message.