Fix HTTP 407 Proxy Authentication Required by checking the proxy login first, then the browser, app, VPN, and network settings. The error means the request reached a proxy server, but the proxy refused to pass it on without valid credentials; MDN defines 407 as a client error response tied to proxy authentication [source: MDN].
TLDR: HTTP 407 usually appears when a browser, API tool, operating system, or app is using a proxy but lacks the right username, password, token, or domain format. For example, in a 75-person office, even 10 expired Windows passwords can trigger repeated 407 errors across browsers, package managers, and update tools. The fastest fix is to confirm the proxy address, port, and credentials, then clear cached logins and retest outside the VPN. If only one app fails, its own proxy settings are probably wrong.
What HTTP 407 means
HTTP 407 Proxy Authentication Required is not the same as a normal website login error. A website usually returns 401 Unauthorized when it wants credentials. A proxy returns 407 when it sits between the user and the internet and demands authentication before forwarding traffic.
That proxy might belong to a company, school, hotel, cloud provider, local debugging tool, or security product. It may inspect traffic, filter sites, log access, cache content, or route requests through a controlled gateway.
Honestly, it feels like a small typo should not break an entire workday, but proxy settings are unforgiving. One wrong port, one expired password, or one missing domain prefix can add 30 seconds to every failed page load.
Common causes of HTTP 407
- Wrong proxy username or password: The most common cause. A password reset may not update saved browser or system credentials.
- Expired credentials: Corporate accounts often force password changes every 60 or 90 days.
- Bad proxy address or port: A proxy such as proxy.company.com:8080 will fail if the host or port is mistyped.
- Missing domain name: Some networks require DOMAIN\username instead of just username.
- VPN conflicts: A VPN can route traffic through a proxy that the device cannot authenticate against.
- App-specific proxy settings: Tools like Git, npm, Docker, Postman, curl, Python, or Java may ignore browser settings.
- Cached stale credentials: Browsers and operating systems may keep old proxy passwords.
- Proxy policy changes: IT may switch authentication methods, ports, or allowed IP ranges.
Step 1: Confirm the proxy details
The first check should be boring, but it saves time. The user or support team should confirm the exact proxy host, port, protocol, and login format.
A correct setup may look like this:
- Host: proxy.example.com
- Port: 8080
- Protocol: HTTP or HTTPS
- Username: EXAMPLE\jsmith
- Password: current network password
If the proxy was copied from an old email, support wiki, or chat thread, it may be outdated. It drives teams crazy that old proxy pages stay indexed in internal search for years.
Step 2: Re-enter proxy credentials
The next fix is to remove the saved login and enter it again. This matters after password changes. The browser may still send the old password without asking.
On Windows, the user can check Credential Manager and remove saved entries tied to the proxy host. Then the browser or app should prompt for credentials again.
On macOS, the user can open Keychain Access, search for the proxy host, and delete old internet password entries. After that, the next request should ask for a new login.
In managed offices, the user may need to sign out and sign back in. Some systems only refresh network tokens after a full restart.
Step 3: Check browser proxy settings
If the error appears only in a browser, its proxy setting may be wrong. Chrome and Edge often use the operating system proxy settings. Firefox can use its own settings.
- Open the browser settings.
- Search for proxy.
- Check whether the browser uses system settings or a manual proxy.
- Disable a manual proxy if it is not required.
- Restart the browser and test again.
If automatic proxy detection is enabled, the device may use a PAC file. A broken PAC file can send traffic to the wrong proxy. In that case, IT should test the PAC URL and confirm the returned rules.
Step 4: Test without VPN or security software
A VPN can cause HTTP 407 when it forces internet traffic through a corporate proxy. Security tools can do the same. The user should disconnect from the VPN, wait a few seconds, and try the page again.
If the error disappears, the issue is probably tied to VPN routing, split tunneling, or corporate access rules. If the user must stay on the VPN, support needs to confirm that the account has proxy access from that VPN group.
For remote staff, this is a common pattern. The browser works at home. Then the VPN connects. Suddenly every site asks for proxy credentials or shows 407. The fix is rarely the website. It is usually the tunnel or proxy policy.
Step 5: Fix app-specific proxy settings
Many developer tools have their own proxy configuration. A browser may work while a terminal command fails with 407. That means the app is not using the right credentials.
curl can test a proxy like this:
curl -x http://proxy.example.com:8080 https://example.com
If credentials are required, the command may need:
curl -x http://username:password@proxy.example.com:8080 https://example.com
For Git, old proxy values can be checked with:
git config --global --get http.proxy
They can be removed with:
git config --global --unset http.proxy
For npm, proxy settings can be checked with:
npm config get proxy
npm config get https-proxy
Then the user should update or delete stale values. Passwords inside config files are risky, so teams should prefer secure credential managers when possible.
Step 6: Check server-side or API proxy code
HTTP 407 also appears in backend services. A script, container, or API client may call the internet through a proxy but forget to send the Proxy-Authorization header.
This often happens after moving code from a laptop to a server. The laptop has system proxy credentials. The server does not. The request then fails before it even reaches the target API.
Teams should check environment variables such as:
- HTTP_PROXY
- HTTPS_PROXY
- NO_PROXY
The NO_PROXY value matters for internal services. If it is missing, a service may send private network requests to a proxy by mistake.
Step 7: Ask IT to check proxy logs
If the user has tried fresh credentials and correct settings, the proxy logs are the next stop. Logs can show whether the proxy rejected the username, blocked the device IP, denied the group, or required a different authentication method.
Useful details for IT include:
- The exact time of the failed request
- The user account
- The device name
- The network or VPN used
- The target URL
- The full error message
Quick checklist
- Confirm proxy host and port.
- Use the correct username format.
- Re-enter the current password.
- Clear saved proxy credentials.
- Restart the browser or device.
- Test with VPN off.
- Check app-level proxy settings.
- Ask IT to review proxy logs.
FAQ
What is HTTP 407 Proxy Authentication Required?
It is an HTTP response from a proxy server. The proxy is asking for valid credentials before it forwards the request to the destination site.
Is HTTP 407 caused by the website?
Usually, no. The proxy blocks the request before it reaches the website. The issue is normally in network, proxy, VPN, browser, or app settings.
How is HTTP 407 different from HTTP 401?
401 comes from the destination server and asks for website or API credentials. 407 comes from a proxy and asks for proxy credentials.
Why does 407 appear after a password change?
The browser, operating system, or app may still store the old password. Removing saved credentials and signing in again often fixes it.
Can a VPN trigger HTTP 407?
Yes. A VPN may route traffic through a corporate proxy that requires authentication. If the user lacks proxy access on that VPN profile, 407 can appear.
How can developers fix 407 in scripts or tools?
They should check environment variables, app proxy settings, and authentication headers. Tools such as Git, npm, Docker, curl, Java, and Python may each need separate proxy configuration.