Skip to content
ProxyHub

Common proxy mistakes: authentication, protocol, DNS leaks and timezone

Published · 4 min read

When a proxy “doesn't work”, the proxy is almost always fine: it's a configuration detail. A badly copied password, the wrong protocol, DNS leaving through your own network or a browser set to another country's timezone. Here are the mistakes we see most often in support, how to recognise them from the symptom and how to fix them in a few minutes.

From symptom to cause

Before changing settings at random, look at exactly what happens. Each symptom points to a specific cause:

SymptomLikely causeWhat to do
407 Proxy Authentication RequiredWrong username or password, or wrong formatCopy the credentials again from the client area; encode special characters
Connection closed straight away or “wrong version number”A protocol different from the proxy's, or https:// in front of the proxySame protocol as the client area, http:// scheme
Timeout with no responseWrong host or portCheck host:port on the proxy page
Right IP, but the test shows your network's DNSDNS leakSOCKS5 with remote DNS (socks5h)
The browser test shows your real IPWebRTC leakDisable or set WebRTC in the profile
Captchas and checks with a clean IPMismatched timezone, language or fingerprintAlign the profile with the proxy's country

Authentication: the 407 error

A 407 error means the proxy received the request but didn't accept the credentials. The most common causes:

  • Wrong format: some tools want host:port:user:password, others user:password@host:port. In the client area, under “Ready to paste”, you can choose between the URL format (http://user:password@host:port) and host:port:user:password.
  • Extra spaces or characters copied along with the password.
  • Special characters in a URL: if the password contains @, : or #, it has to be encoded inside a URL (for example @ becomes %40).
  • Another proxy's credentials: with several proxies it's easy to paste the username and password of the wrong one.
Terminal
# Password with @: inside a URL it must be encoded (@ becomes %40)
curl -x "http://USER:pa%40ss@HOST:PORT" https://api.ipify.org

Wrong protocol and scheme

Every ProxyHub proxy works with the protocol you choose in the client area, HTTP or SOCKS5. If the tool uses the other one, the connection opens and closes straight away, or you get a garbled response. The full comparison is in HTTP vs SOCKS5.

Another frequent mistake is writing the proxy with https:// in front. The scheme says how to talk to the proxy, not to the site: for an HTTP proxy you use http:// even when visiting https sites, because the encrypted connection to the site travels inside the proxy.

Terminal
# HTTP proxy: http:// scheme even for https sites
curl -x "http://USER:PASSWORD@HOST:PORT" https://api.ipify.org

# SOCKS5 proxy
curl -x "socks5h://USER:PASSWORD@HOST:PORT" https://api.ipify.org

DNS and WebRTC leaks: when your network shows through

With SOCKS5 the site's name can be resolved on your computer, by your provider's DNS servers, before going through the proxy: that's a DNS leak. The site sees the proxy's IP, but tests show your network's and your country's DNS.

  • In scripts and cURL use socks5h:// instead of socks5://: the h means the name is resolved by the proxy.
  • In Firefox turn on the option to send DNS through the proxy when using SOCKS v5.
  • With an HTTP proxy the problem doesn't arise: the site's name travels in the request and the proxy resolves it.

WebRTC, which browsers use for calls and video, can reveal your real IP even when the rest of the traffic goes through the proxy. In antidetect browsers it's set in the profile; to check, open the What is my IP page with the proxy on.

Mismatched timezone, language and fingerprint

An Italian IP with the browser on New York time and US English is a mismatch that anti-fraud systems notice straight away, even when the IP is perfectly clean.

  • Browser timezone and language matching the proxy's country. Antidetect browsers can set them from the IP.
  • A TCP/IP fingerprint consistent with the profile's operating system: a Windows browser with a smartphone fingerprint looks off. You can choose it for each proxy in the client area; the reasons are in TCP/IP fingerprint.
  • No VPN on top of the proxy: it adds another IP and another country to the same session.

Rotation and half-done setups

  • Changing IP during a session expires logins and carts: rotate between sessions. A change is possible once every 60 seconds per proxy. See IP rotation.
  • A proxy set up only partly: the system proxy doesn't apply to every program. Some apps ignore it, and many command-line tools only read the HTTP_PROXY and HTTPS_PROXY variables.
  • No check: always check the IP from inside the tool you'll use, not from another window.

The full step-by-step checklist is in How to test a proxy.

Frequently asked questions

Why do I get a 407 error?

The proxy didn't accept the credentials. Copy the username and password again from the client area, check there are no spaces and that the format is the one the tool expects; if the password contains characters such as @ or :, it must be encoded inside a URL.

The proxy works in the browser but not in my program: why?

Usually the program doesn't use the system proxy, or it uses a different protocol. Set the proxy directly in the program, with the same protocol as the client area, and check the IP from inside the program.

How can I tell if I have a DNS leak?

Run a DNS test with the proxy on: if your provider's or your country's DNS servers appear, DNS isn't going through the proxy. With SOCKS5 use socks5h or the program's remote DNS option.

Try a 5G mobile proxy

Dedicated smartphone, unlimited traffic, real carrier IPs. Live in seconds.

See plans

Or pick a country:

Read next

All articles