Common Proxy Errors

When working with proxies, you may encounter various errors. Here's how to identify and resolve the most common ones.

407 Proxy Authentication Required

Cause: The proxy server requires authentication, but valid credentials were not provided.

Solution:

• Verify your username and password in the HypeProxy.io dashboard.
• Make sure you're including the credentials in the correct format: username:password@proxy-host:port.
• If using IP whitelisting, confirm your current IP is authorized in the dashboard.

Connection Refused (ECONNREFUSED)

Cause: The proxy server is not accepting connections on the specified port.

Solution:

• Double-check the proxy host and port from your dashboard.
• Ensure your firewall or network isn't blocking outbound connections on the proxy port.
• Try connecting to a different proxy port if available.

Connection Timeout

Cause: The proxy server didn't respond within the expected time.

Solution:

• Check your internet connection.
• Verify the proxy is online via the HypeProxy.io dashboard.
• If using a mobile proxy, the device may be temporarily offline — wait a moment and retry.
• Try increasing the timeout value in your client configuration.

502 Bad Gateway

Cause: The proxy received an invalid response from the target server.

Solution:

• The target website may be temporarily down. Try again later.
• If persistent, try rotating your IP address — the current IP may be blocked by the target site.

503 Service Unavailable

Cause: The target server is overloaded or temporarily unavailable.

Solution:

• Wait and retry the request.
• Implement retry logic with exponential backoff in your scripts.

SSL/TLS Errors

Cause: Certificate verification failed when connecting through the proxy.

Solution:

• Ensure you're using HTTPS protocol for HTTPS targets.
• Update your client's certificate store.
• Verify your proxy configuration uses the correct protocol (HTTPS or SOCKS5).

DNS Resolution Failure

Cause: The proxy or your system can't resolve the target domain.

Solution:

• If using SOCKS5, use socks5h:// instead of socks5:// to resolve DNS through the proxy.
• Check that the target URL is correct and the domain exists.

Slow or Hanging Requests

Cause: Network congestion, proxy overload, or target site throttling.

Solution:

• Rotate your IP address and retry.
• Switch between HTTPS and SOCKS5 protocols.
• Check the proxy response time via the API: GET /Utils/GetResponseTime/{proxyId}.
• If the issue persists, contact HypeProxy.io support.

General Troubleshooting Steps

1. Verify credentials: Log into the dashboard and confirm your proxy details.
2. Test without proxy: Ensure the target site is accessible without a proxy.
3. Try a different protocol: Switch between HTTPS and SOCKS5.
4. Rotate IP: Request a new IP via the dashboard or API.
5. Check status: Visit the HypeProxy.io status page for any ongoing issues.