Quick Answer
A 407 Proxy Authentication Required error means the proxy received your request but rejected the credentials. The fix is almost always in how the username and password are sent: check they're correct, match your authentication method (user:pass vs. IP whitelist), use the right scheme, and URL-encode special characters in the password.
What 407 Actually Means
Unlike a 403 (the target site blocked you), a 407 comes from the proxy itself, before your request ever reaches the target. The proxy is saying: I can see you, but you haven't authenticated. That's good news — it means the host and port are reachable. The problem is narrow and almost always credential-related.
Work through the six causes below in order; the first two fix most cases.
1. Wrong or Missing Username / Password
The most common cause. Re-copy both values from your GermanProxy.io account and confirm there's no trailing space. In a proxy URL they go before the host:
http://USER:PASS@PROXY_HOST:PORT
If USER, PASS, PROXY_HOST or PORT is missing or mistyped, you get a 407.
2. Your Method Is IP Whitelist, Not user:pass
Many providers offer two authentication methods: username/password or IP whitelisting (the proxy trusts requests from your own IP, with no credentials). If your account is set to whitelist mode and you send user:pass — or vice versa — you get a 407.
- Using user:pass? Make sure credentials are included in every request.
- Using IP whitelist? Confirm your current public IP is on the allowlist. If your IP changed (home ISP, VPN, new location), re-add it.
3. Scheme Mismatch (HTTP vs SOCKS5)
Sending HTTP-style auth to a SOCKS5 port (or the reverse) can surface as a 407 or a connection failure. Confirm you're using the scheme that matches the port — http:// or socks5:// — exactly as shown in your account.
4. Special Characters in the Password
If your password contains characters like @, :, /, # or %, they break the proxy URL because those characters have meaning in a URL. URL-encode them — for example @ becomes %40, # becomes %23. Most languages have a helper (urllib.parse.quote in Python, encodeURIComponent in JS) to encode the password before building the URL.
5. Credentials Stripped by a Library or Tool
Some HTTP clients don't forward proxy credentials embedded in the URL and need them set explicitly — for example page.authenticate() in Puppeteer, or proxy-authorization headers elsewhere. If the URL looks right but you still get 407, set the credentials through your tool's dedicated auth method instead.
A common Puppeteer trap: Chrome ignores credentials in the proxy URL entirely, and page.authenticate({ username, password }) must run before the first page.goto() — call it after that first navigation and the 407 sticks. The per-tool guides cover this: Python, Node.js, Puppeteer, Selenium, Scrapy.
6. Plan Expired or Endpoint Changed
If nothing above applies, confirm your plan is active and the endpoint details haven't changed. An expired plan or rotated endpoint will refuse authentication. Check your account, or reach support.
Verify the Fix
Once you've adjusted the credentials, test with a single request to an IP-echo endpoint before re-running your whole pipeline. A clean response showing a German mobile IP means authentication is working. For a full configuration check — IP, DNS, WebRTC and more — see how to test your mobile proxy setup.
FAQ
Is a 407 the same as being blocked by the website?
No. A 407 comes from the proxy before your request reaches the target; a 403 or 429 comes from the target site. A 407 is an authentication issue, not a blocking issue.
I'm sure my password is right — why still 407?
The most common hidden cause is an unencoded special character in the password, or a tool that strips URL credentials. Try URL-encoding the password, or setting credentials through your client's dedicated auth method.
Could it be my firewall or antivirus?
Occasionally. Local security software can interfere with proxy auth. Temporarily test from a clean environment to isolate whether the 407 is from your setup or the credentials.
Does GermanProxy.io use user:pass or IP whitelist?
Both methods are available — check which one your endpoint is configured for in your account, and authenticate to match it.
Get a German Mobile Proxy
Need a German mobile proxy with straightforward authentication and real support? Browse plans — HTTP/SOCKS5/OpenVPN, fair-use 20 GB/day, 4.8★ on Trustpilot.
Get a German mobile proxy: Real 4G/5G IPs from Germany, fair-use 20 GB/day — see German 4G/5G mobile proxy options or start with a dedicated 5G proxy.