Work through the checks below to identify whether the problem comes from the proxy details, authentication, application, destination website, or local network.

1. Confirm that the proxy is active

Open Overview or My Proxies in your Proxy-Cheap dashboard and confirm that the proxy has not expired and is ready to use.

Copy the current server address, port, username, and password directly from the dashboard. Use your proxy credentials—not the email address and password used to log in to your Proxy-Cheap account.

2. Check the connection details

• Make sure the server address and port are in the correct fields.
• Re-enter the username and password without extra spaces.
• If you recently regenerated the proxy password, update it in every browser, application, or automation tool using that proxy.
• Do not use a custom port. Use the port shown in your dashboard.

3. Check the authentication method

For username/password authentication, confirm that authentication is enabled in the application and that the current proxy credentials are being used.

For IP whitelist authentication, add the public IP address of the network making the connection. If you changed Wi-Fi networks, internet providers, VPN servers, or mobile connections, your public IP may have changed and may need to be added again.

Authentication availability depends on the proxy type. Use the method displayed for the selected proxy in your dashboard.

4. Check the protocol

Make sure the application is configured for the protocol shown in your dashboard, such as HTTP or SOCKS5.

If you recently changed the proxy protocol, update the application configuration as well. Not every proxy type or application supports every protocol.

SOCKS5 supports TCP connections, but Proxy-Cheap does not provide SOCKS5 UDP relay. Applications that require UDP may therefore fail even when the proxy itself is active.

5. Test outside the application

If possible, test the proxy with a simple command-line request. Replace the placeholders with the details shown in your dashboard.

HTTP with username/password:

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

SOCKS5 with username/password and remote DNS:

curl -v -x socks5h://USERNAME:PASSWORD@HOST:PORT https://api64.ipify.org

If you use IP whitelist authentication, remove USERNAME:PASSWORD@ from the command.

If the command works but your browser or application does not, the issue is most likely in that application’s proxy settings or protocol support.

6. Check the destination website

Try more than one destination. A specific website may block proxy traffic, restrict an IP, rate-limit requests, or be temporarily unavailable.

If you are using an IPv6-only proxy, the destination must be reachable over IPv6. A website that only supports IPv4 will not work through an IPv6-only proxy.

7. Check the local network

Firewalls, antivirus software, company networks, internet providers, and regional network restrictions can block proxy connections. If permitted, test from another device or network to isolate the cause.

Port 25 is blocked and custom ports cannot be opened. Use the endpoint and port provided in your dashboard.

Contact Support

If the proxy still does not connect, contact our Live Chat Support or email support@proxy-cheap.com. Include the proxy ID or order ID, protocol, authentication method, application used, exact error, and approximate time of the failed test.

Do not send your proxy password.