Crypto
03 Mar 2026
Read 13 min
how to fix HTTP 407 error and restore web access *
how to fix HTTP 407 error and restore web access by fixing proxy authentication quickly and reliably.
HTTP 407 means a proxy server is blocking your request until you sign in. To get back online, confirm whether you actually need a proxy, update or remove proxy settings, enter the right credentials, set proxy variables for apps, and check VPN or company login. Follow these steps on how to fix HTTP 407 error quickly.
You try to open a page or run a tool, and it fails with “Proxy Authentication Required” or “Could not download page (407).” This status code means a proxy sits between you and the site. The proxy wants you to authenticate first. Sometimes the fix is as simple as removing an old proxy entry. Other times you must log in or set the right credentials for your browser or app. This guide shows how to fix HTTP 407 error in simple steps and restore your web access with confidence.
Browsers: A popup asks for proxy credentials, or pages do not load.
Apps and tools: curl, npm, pip, Git, Maven, and more fail with 407 or “Proxy Authentication Required.”
Logs and services: “Could not download page (407)” or update checks that time out.
Common causes include:
Wrong or old proxy settings left in your system or app.
Expired or changed password, or locked account.
VPN or corporate login not active, so the proxy rejects you.
Authentication type mismatch (Basic vs NTLM/Kerberos).
Firewall or security agent intercepting and requiring auth.
Do you need a proxy? If you are at home or on mobile, turn proxy off. If you are on a company network, keep it on.
Restart your browser or app. Try a private window to clear old auth.
Re-enter credentials when prompted. Use your current company username and password.
Sign in to VPN or your company portal. Some proxies accept only network-joined or VPN traffic.
Sync your device time. Bad time breaks Kerberos and other auth.
Remove stale proxy entries in system or app settings. Then add the correct ones if needed.
If nothing works, ask IT to check your account, groups, or proxy logs.
Open Settings > Network & Internet > Proxy.
If you do not need a proxy, turn “Use a proxy server” off. Also turn off “Automatically detect settings” if it causes loops.
If you need a proxy, turn it on and enter the address and port. If you have a PAC file (Automatic configuration script), add its URL.
Check “Don’t use the proxy server for local addresses” or add exceptions for intranet sites.
Close and reopen the browser. When asked, enter your domain credentials.
Go to System Settings > Network > select your network > Details > Proxies.
Uncheck all proxy boxes if you do not need a proxy.
If you do need one, check the right protocols (HTTP, HTTPS) and enter the host and port, or add the PAC file URL.
Apply changes, restart the browser, and sign in if prompted.
Open Settings > General > Network Settings > Settings…
Choose “No proxy” if you do not need one, or “Use system proxy settings.”
For manual proxy, set HTTP Proxy and “Use this proxy server for all protocols” if required.
Add “No proxy for” exceptions (for example, localhost, 127.0.0.1, intranet.local).
HTTP_PROXY and HTTPS_PROXY: Set to http://username:password@proxy-host:port
NO_PROXY: Domains to bypass (for example, localhost, 127.0.0.1, .corp.local)
If your password has special symbols, URL-encode them (for example, replace @ with %40).
curl: curl -x http://user:pass@proxy:port https://example.com
wget: Add proxy and credentials in your .wgetrc or use command-line options.
git config –global http.proxy http://user:pass@proxy:port
git config –global https.proxy http://user:pass@proxy:port
Use NO_PROXY to skip proxy for your Git server if it is internal.
npm config set proxy http://user:pass@proxy:port
npm config set https-proxy http://user:pass@proxy:port
yarn config set proxy and https-proxy similarly.
For NTLM proxies, consider using a helper like CNTLM or a corporate connector.
pip install –proxy http://user:pass@proxy:port package-name
Or define it in pip.conf (Linux/macOS) or pip.ini (Windows).
Maven: Add proxy with credentials in settings.xml.
Gradle: Set systemProp.http.proxyHost, systemProp.http.proxyPort in gradle.properties.
If your company proxy uses NTLM/Kerberos and your tool does not support it well, use a local bridge (CNTLM or similar) that handles enterprise auth and forwards to your tool.
VPN/Zero Trust: Connect your VPN or ZTNA client. Some proxies only allow traffic from managed networks.
Captive portals: On public Wi‑Fi, open a non-HTTPS site (http://neverssl.com) to trigger the login page before trying your apps.
Security agents: Web shields or SSL inspection may inject a proxy step. Update the agent, trust its root certificate, and ensure your account is active.
Certificates: If the proxy does HTTPS inspection, install the company root CA so your apps can validate it.
Time and SSO: Kerberos and SSO break when device time is off. Sync time and retry.
Account status (locked, expired password, disabled group).
Policy blocks for the site or app you are using.
Authentication type mismatch or negotiation failure.
Recent changes to PAC/WPAD, proxy hostname, or port.
Load issues or outages on the proxy cluster.
Turn off the manual proxy in system settings.
Restart the browser. You are back online.
Install and configure CNTLM to use your Windows credentials.
Point npm’s proxy to http://localhost:3128 (CNTLM default).
Test npm install again. It works.
Unset HTTP_PROXY and HTTPS_PROXY, or set the correct values.
Add NO_PROXY for internal services.
Restart the job. Downloads succeed.
Use auto-proxy (PAC) where possible. It adapts when networks change.
Store proxy host, port, and PAC URL in your documentation.
Keep VPN and SSO clients updated. Renew passwords before they expire.
Set NO_PROXY for localhost and internal domains to avoid needless proxy hops.
For teams, standardize environment variables and tool configs in onboarding guides.
Learning how to fix HTTP 407 error is about two things: knowing when you need a proxy and giving it the right credentials. Start with the quick checklist. Remove stale proxy settings if you do not need them. Add the correct details if you do. Sign in to VPN or SSO when required. If the error persists, contact your network admin to verify your account and proxy policy. With these steps, you can resolve the issue fast and restore full web access.
What HTTP 407 Means and Why It Stops You
HTTP 407 is like a gate. Your traffic goes through a proxy. The proxy requires a username and password, or it uses your system sign-in. If the proxy does not get valid credentials, it refuses the request. You may see this in:How to fix HTTP 407 error: Quick checklist
Use this simple flow before deep troubleshooting:Fix It in Your Browser
Windows (Chrome, Edge, Brave, etc.)
Browsers on Windows use system proxy settings.macOS (Safari, Chrome, Firefox)
Firefox special note
Firefox can use its own proxy settings:Fix It in Apps and Developer Tools
Some tools do not read system proxy settings. You must set them in the app or environment.Environment variables (common on Windows, macOS, Linux)
curl and wget
Git
npm and yarn
Python pip
Java tools (Maven/Gradle)
Check Network and Security Layers
When the Problem Is on the Proxy Side
If you did everything right and still get 407, the proxy may be at fault. Share the exact timestamp, your IP, and a failing URL with IT. Ask them to check:Real-World Fix Scenarios
Home network after a work trip
You turned on a manual proxy at the office. At home, pages break with 407. Solution:Developer tool fails with “407 Proxy Authentication Required”
npm cannot reach the registry behind an NTLM proxy. Solution:“Could not download page (407)” on a server
A CI runner inherited HTTP_PROXY from an old image. The proxy is not reachable. Solution:Prevent 407 Headaches Next Time
For more news: Click Here
FAQ
Q: What does HTTP 407 “Proxy Authentication Required” mean?
A: HTTP 407 means a proxy sits between your device and the destination site and is blocking the request until you authenticate. The proxy typically requires a username and password or uses your system sign-in and will refuse requests without valid credentials.
Q: Why do I get “Could not download page (407)” when opening pages or running tools?
A: This error appears when a proxy between you and the site requires authentication and blocks the connection, which causes browsers and tools to fail. For quick guidance on how to fix HTTP 407 error, confirm whether you need a proxy, re-enter credentials, and check VPN or company login.
Q: How can I fix HTTP 407 error quickly in my browser on Windows or macOS?
A: On Windows, open system Proxy settings and either turn the proxy off if you don’t need it or enter the correct address/port or PAC file, then restart the browser and sign in when prompted. On macOS, go to Network > Details > Proxies, disable proxies if unnecessary or configure the correct protocols and host/port, apply changes, and restart the browser.
Q: How do I set proxy credentials for command-line tools like curl, npm, pip, or Git?
A: Many developer tools do not read system proxy settings, so set HTTP_PROXY and HTTPS_PROXY environment variables to http://username:password@proxy-host:port or use tool-specific config options like curl -x and npm config set proxy. Also add NO_PROXY for domains to bypass the proxy and URL-encode any special characters in your password.
Q: What should I do if my company uses NTLM or Kerberos authentication and I see a 407?
A: If your proxy uses NTLM or Kerberos and the tool lacks native support, use a local bridge such as CNTLM or a corporate connector that handles enterprise authentication. Also ensure your device time is synced and that you are signed into VPN or SSO, because Kerberos and SSO can fail when time or sign-in is incorrect.
Q: My CI job reports “Could not download page (407)”; how can I fix that on a server or runner?
A: Check for inherited HTTP_PROXY and HTTPS_PROXY environment variables from images and unset them or set the correct values, then add NO_PROXY for internal services and restart the job. This resolves cases where a runner uses stale proxy settings that are not reachable.
Q: When should I contact IT about a persistent proxy 407 error and what info should I provide?
A: Contact IT after you have checked local settings, re-entered credentials, and tried VPN/SSO but still see 407, and provide a timestamp, your IP, and a failing URL so they can inspect proxy logs. Ask them to verify account status, policy blocks, authentication negotiation, and recent PAC/WPAD or proxy changes.
Q: What can I do to prevent future occurrences of HTTP 407 errors?
A: Use an auto-proxy PAC where possible, document proxy host/port and PAC URLs, keep VPN and SSO clients updated, and set NO_PROXY for localhost and internal domains to avoid needless proxy hops. For teams, standardize environment variables and tool configurations and include a simple checklist on how to fix HTTP 407 error in onboarding guides.
* The information provided on this website is based solely on my personal experience, research and technical knowledge. This content should not be construed as investment advice or a recommendation. Any investment decision must be made on the basis of your own independent judgement.
Contents
