How to Fix HTTP 407 Proxy Authentication Error Quickly

Q: How do I test what proxy authentication method the server expects using curl?

Use curl -v --proxy http://proxy:port https://example.com to see if the proxy returns "407 Proxy Authentication Required" and a Proxy-Authenticate header, then try curl -v --proxy-user user:pass --proxy http://proxy:port https://example.com to supply credentials. If the proxy requires NTLM or Negotiate, use curl's --proxy-ntlm or --proxy-negotiate options as appropriate.

Insights AI News How to Fix HTTP 407 Proxy Authentication Error Quickly

AI News

22 Jul 2026

Read 11 min

How to Fix HTTP 407 Proxy Authentication Error Quickly

how to fix HTTP 407 proxy authentication error and restore downloads by fixing proxy login and headers

News

Here’s how to fix HTTP 407 proxy authentication error fast: confirm the proxy address and port, re-enter the correct credentials, clear saved proxy logins, bypass the proxy for trusted sites, and test with curl. For apps, set HTTP(S)_PROXY or send a Proxy-Authorization header. Contact your admin if it still fails. A 407 means your traffic goes through a proxy, but the proxy needs you to sign in. Your browser or app did not send the right login, or the proxy rejected it. The steps below show quick checks for browsers, operating systems, and developer tools so you can get back online quickly.

What the 407 Error Means

A 407 comes from a proxy, not the website. The proxy returns “Proxy Authentication Required.” It also sends a list of auth methods, like Basic, NTLM, Negotiate, or Digest. Your device must answer with a Proxy-Authorization header. If it fails, you keep seeing 407. How it differs: – 401: the website wants you to sign in. – 403: the server blocks you. – 407: the proxy blocks you until you authenticate.

How to Fix HTTP 407 Proxy Authentication Error

Quick checks for everyone

Confirm the proxy address and port with your IT team. A single wrong digit breaks auth.
Re-enter your proxy username and password. Watch for expired passwords.
Restart your browser or app to clear stale proxy sessions.
Turn off VPN briefly to test. Some VPNs change proxy routes.
Try another network (mobile hotspot). If 407 goes away, the issue is on the original network or proxy.

Fix it in your browser

Chrome or Edge (uses system proxy):

Open Settings > System > Open your computer’s proxy settings.
On Windows: Settings > Network & Internet > Proxy. Check the proxy server address and port. Toggle “Use a proxy server” off to test.
On macOS: System Settings > Network > Your network > Details > Proxies. Verify settings or uncheck to test.
Bypass for trusted sites: add 127.0.0.1, localhost, and your intranet domains to “Do not use proxy for” or “Bypass” list.

Firefox (has its own proxy option):

Settings > General > Network Settings.
Select “Use system proxy settings” or set Manual proxy with the correct host and port.
Click OK, then restart Firefox.

Clear saved proxy credentials:

Windows: Control Panel > Credential Manager > Windows Credentials. Remove entries for your proxy host.
macOS: Keychain Access. Search your proxy host. Delete old entries, then retry to re-prompt.
In your browser password manager, remove saved proxy logins if present.

Fix it in your OS or apps

Environment variables (CLI and many apps honor these):

macOS/Linux (temporary): export HTTP_PROXY=http://user:pass@proxy:port and export HTTPS_PROXY=http://user:pass@proxy:port
Windows PowerShell (persist for current user): [Environment]::SetEnvironmentVariable(“HTTP_PROXY”,”http://user:pass@proxy:port”,”User”) and same for HTTPS_PROXY
Unset to test: unset HTTP_PROXY HTTPS_PROXY (macOS/Linux) or remove the variables in Windows Environment Variables.

Popular tools:

Git: git config –global http.proxy http://user:pass@proxy:port
npm: npm config set proxy http://user:pass@proxy:port and npm config set https-proxy http://user:pass@proxy:port
pip: pip install –proxy http://user:pass@proxy:port package-name

Security note: avoid putting credentials in plain text where logs may capture them. Use a credential helper if possible.

Developer and CLI Tips

Test with curl

Use curl to see what the proxy expects:

curl -v –proxy http://proxy:port https://example.com
If you see “407 Proxy Authentication Required” and “Proxy-Authenticate: Basic” (or NTLM/Negotiate), try: curl -v –proxy-user user:pass –proxy http://proxy:port https://example.com

Send the right header

Apps must send Proxy-Authorization, not just Authorization. If you write code, ensure your HTTP client supports proxy auth:

Java: set Proxy and Authenticator or use system properties (http.proxyHost, http.proxyPort, http.proxyUser, http.proxyPassword).
Python requests: proxies={“http”: “http://user:pass@proxy:port”,”https”:”http://user:pass@proxy:port”}
Node: use global-agent, proxy agents, or environment variables.

Match the auth scheme

Some corporate proxies use NTLM or Kerberos (Negotiate):

curl: use –proxy-ntlm or –proxy-negotiate as needed.
Windows apps may auto-auth with your domain login. Make sure you are on the domain and the clock is correct.
If your proxy moved to SSO, basic username:password may no longer work.

PAC and WPAD files

Your system may use a Proxy Auto-Config (PAC) file or auto-detect (WPAD):

Verify the PAC URL in system proxy settings.
Open the PAC file in a browser. Check if your site should go direct or through a specific proxy.
If the PAC is down or wrong, you may get 407. Ask IT to confirm.

Common Causes and How to Spot Them

Wrong password or expired account: You get 407 on all sites. Fix by updating your password or re-entering credentials.
Wrong proxy host/port: You see instant 407 or timeouts. Confirm settings with IT.
Switched networks (home vs office): Old proxy set in your OS causes 407 at home. Disable or remove the proxy when offsite.
HTTPS tunneling blocked: CONNECT on 443 is not allowed by proxy policy. You may browse HTTP but fail on HTTPS. Ask IT to allow CONNECT.
Kerberos/NTLM mismatch: Only some apps fail. Use a client that supports your proxy’s auth or enable negotiate/NTLM.
Clock skew: Kerberos auth fails if your device clock is off. Sync time and try again.
Credential cache issues: Browser saved old details. Clear credentials and restart.

Prevent It from Coming Back

Use “Use system proxy settings” in apps so one change fixes all.
Store proxy credentials in your system keychain or a credential manager.
Add bypass rules for localhost and trusted internal domains.
Avoid hardcoding credentials in scripts. Read from env vars or secure stores.
Document proxy details: host, port, auth type, and who to contact.

When to Call Your Network Admin

Your credentials work on one device but not another.
You need NTLM/Kerberos and your tool does not support it.
The PAC file is wrong or offline.
You need a site added to the allowlist or need CONNECT enabled.
You suspect a VPN or firewall rule is blocking proxy auth.

A final word: the fastest way for how to fix HTTP 407 proxy authentication error is to verify the proxy host and port, re-enter valid credentials, clear old logins, and test with curl or another app that shows headers. If you still see 407, match the proxy’s auth scheme or ask your admin to confirm your access.

(Source: https://arstechnica.com/ai/2026/07/linus-torvalds-to-critics-of-ai-coding-in-linux-fork-it-or-just-walk-away/)

For more news: Click Here

FAQ

Q: What does HTTP 407 proxy authentication error mean? A: A 407 means your traffic goes through a proxy that requires authentication and the proxy returns “Proxy Authentication Required.” The proxy also sends a list of auth methods and expects the client to send a Proxy-Authorization header, so if the browser or app does not send the right login the proxy will reject the request and you keep seeing 407. Q: What is the fastest way to fix HTTP 407 proxy authentication error? A: The fastest way for how to fix HTTP 407 proxy authentication error is to verify the proxy host and port, re-enter valid credentials, clear old logins, and test with curl or another app that shows headers. If that does not resolve it, match the proxy’s auth scheme (Basic, NTLM, Negotiate) or contact your network admin. Q: How do I fix a 407 error in Chrome, Edge, or Firefox? A: For Chrome or Edge open Settings > System > Open your computer’s proxy settings and verify the proxy address and port or toggle “Use a proxy server” off to test. For Firefox go to Settings > General > Network Settings and either select “Use system proxy settings” or set Manual proxy with the correct host and port, then restart the browser. Q: How can I clear saved proxy credentials on Windows and macOS? A: On Windows open Control Panel > Credential Manager > Windows Credentials and remove entries for your proxy host. On macOS open Keychain Access, search your proxy host, delete old entries, then retry to re-prompt for credentials. Q: How do I test what proxy authentication method the server expects using curl? A: Use curl -v –proxy http://proxy:port https://example.com to see if the proxy returns “407 Proxy Authentication Required” and a Proxy-Authenticate header, then try curl -v –proxy-user user:pass –proxy http://proxy:port https://example.com to supply credentials. If the proxy requires NTLM or Negotiate, use curl’s –proxy-ntlm or –proxy-negotiate options as appropriate. Q: How can I set proxy credentials for command-line tools and apps? A: Set HTTP(S)_PROXY environment variables, for example export HTTP_PROXY=http://user:pass@proxy:port on macOS/Linux or use PowerShell’s [Environment]::SetEnvironmentVariable(“HTTP_PROXY”,”http://user:pass@proxy:port”,”User”) on Windows, and unset them to test. Many tools also accept tool-specific settings such as git config –global http.proxy http://user:pass@proxy:port, npm config set proxy http://user:pass@proxy:port and npm config set https-proxy http://user:pass@proxy:port, or pip install –proxy http://user:pass@proxy:port package-name. Q: Why do some applications still get a 407 error while others work? A: Some apps fail because the proxy uses NTLM or Kerberos (Negotiate) and the client does not support that auth scheme. Other causes include wrong proxy host/port, expired passwords, PAC/WPAD misconfiguration, HTTPS CONNECT being blocked, clock skew for Kerberos, or credential cache issues. Q: When should I contact my network administrator about persistent 407 errors? A: Contact your admin if your credentials work on one device but not another, if your tool needs NTLM/Kerberos support it doesn’t have, or if the PAC file appears wrong or offline. Also ask them to add a site to the allowlist, enable CONNECT for HTTPS tunneling, or investigate VPN or firewall rules blocking proxy authentication.