Skip to content

Guides · Connect and debug

Fix ERR_PROXY_CONNECTION_FAILED and PAC errors in Chrome

ERR_PROXY_CONNECTION_FAILED means Chromium could not resolve the proxy’s name or connect a socket to it. Start with the proxy selected by Chrome, then check its host, port and network reachability. Chromium explicitly separates this error from an HTTP CONNECT failure, so changing a password is not the first diagnostic. The related ERR_MANDATORY_PROXY_CONFIGURATION_FAILED means a required PAC script failed, and has its own section below.

By PortproofPublished Updated

Short answers

What causes ERR_PROXY_CONNECTION_FAILED?

Chromium defines it as failure to create a connection to the proxy: either resolving its name or connecting a socket. A wrong address, closed port or inaccessible network route can fit that stage. The code alone does not identify which one occurred.

Is it the same as ERR_TUNNEL_CONNECTION_FAILED?

No. ERR_TUNNEL_CONNECTION_FAILED refers to establishing a tunnel through a proxy Chrome has already reached. An HTTP CONNECT response such as 407, 403 or 502 belongs to that later stage. Record the actual response, then follow the ERR_TUNNEL_CONNECTION_FAILED guide.

What is ERR_MANDATORY_PROXY_CONFIGURATION_FAILED?

Chromium uses it when a mandatory proxy configuration cannot be used: currently, a required PAC script could not be fetched, parsed or executed. Check the script and whoever supplied it rather than repeatedly editing a manual proxy password.

Should I disable the proxy?

Remove a stale proxy that you added to your own unmanaged device if you no longer need it. For a required school or work configuration, ask the administrator to repair the route. Record the old settings and exact error before making a change.

These definitions and desktop settings labels were checked against Chromium’s current main-branch source on 4 October 2026. This is a documentation-checked diagnostic, not a recorded test in a specific Chrome release. Record your installed version from chrome://version; labels and configuration sources can differ.

Read the code before changing settings

Different errors point to different stages
Message or codeStart here
ERR_PROXY_CONNECTION_FAILEDThe configured proxy’s hostname, listener port and network route.
ERR_MANDATORY_PROXY_CONFIGURATION_FAILEDThe required PAC URL or script; see the automatic-configuration section below.
ERR_TUNNEL_CONNECTION_FAILEDThe ERR_TUNNEL_CONNECTION_FAILED guide, then the CONNECT tunnel diagnostic for the proxy’s response.
407 Proxy Authentication Required or a proxy sign-in promptThe 407 guide or prompt guide.

A page saying only Unable to connect to the proxy server gives less evidence than the error code. Keep the code printed with it, the failed URL’s hostname and the time. Chromium’s network error definitions distinguish proxy connection, tunnel and mandatory-configuration failures.

Find the proxy Chrome is actually using

  1. Open chrome://settings/system. When system settings supply the route, the control is labelled Open your computer's proxy settings.
  2. If an extension supplies the settings, inspect that extension’s active proxy entry. Make sure you are checking the Chrome profile that failed.
  3. If an administrator controls the route, inspect chrome://policy and send the proxy policy details to the administrator. Keep required rules in place.
  4. If you launch Chrome from a shortcut, test runner or script, inspect any proxy launch options there. A system setting change may not alter that launch configuration.

On Windows 10 or 11, the system pane is Settings > Network & internet > Proxy. On macOS Tahoe 26, select the active network service in System Settings > Network, then Details > Proxies. Record whether the route uses a manual server, PAC URL or automatic discovery. The proxy settings guide explains those modes.

The Chromium settings source documents the system control and indicators for extension or administrator control. Its proxy documentation identifies policy, launch options, extensions and system settings as possible configuration sources.

Check the host and port together

  1. Copy the gateway hostname again from the supplied connection details. Keep a URL scheme or credential URL out of a separate hostname field.
  2. Compare the protocol and port as a pair. For Portproof’s authenticated HTTP route, use host gw.portproof.org and port 7000 from the connection builder.
  3. If the proxy runs on your computer, confirm that its local process is running and listening on the configured port. An old local proxy entry can remain after the app stops.
  4. If the server is on an organisation’s network, check whether the required network or VPN connection is available. Ask the administrator about permitted access to that host and port.

For an authenticated Portproof connection in Chrome, choose the HTTP endpoint. Chromium does not support SOCKS5 username/password authentication. An HTTPS destination can use an HTTP proxy through CONNECT; the destination scheme is not a reason to replace the gateway protocol or port.

Compare one explicit curl request

If you intentionally use Portproof, run this bounded check in an interactive POSIX terminal. Replace the username label with the complete generated username. curl asks for the proxy password; do not append it to the command. It makes one small request to the echo endpoint with certificate verification enabled.

Check the intended HTTP proxysh
curl_status=0
curl --disable --silent --show-error \
  --proxy 'http://gw.portproof.org:7000' \
  --proxy-user 'YOUR_FULL_PROXY_USERNAME' \
  --noproxy '' \
  --connect-timeout 5 --max-time 15 \
  --output /dev/null \
  --write-out 'connect_status=%{http_connect} target_status=%{response_code}\n' \
  'https://api.portproof.org/v1/echo-ip' || curl_status=$?
printf 'curl_exit=%s\n' "$curl_status"

This uses the diagnostic pattern in the existing curl guide; no new live-gateway or browser test is claimed here. --disable comes first to skip a default curl configuration file, and the explicit proxy with an empty exclusion list fixes the route for this check. Windows PowerShell needs curl.exe and adapted shell syntax. curl option reference.

Choose the next diagnostic from the result
Observed resultNext step
Proxy name cannot resolve; connection is refused or times outUse connection refused and timeouts. Keep the exact message as well as the exit number.
connect_status=407The gateway answered. Follow the 407 guide for authentication and gateway-code checks.
CONNECT returns 403, 502 or 503Follow the CONNECT guide. Distinguish the tunnel response from a later website response.
CONNECT succeeds and the expected endpoint respondsCompare Chrome’s selected gateway, profile and authentication handling with this explicit request.
A certificate validation errorCheck the destination hostname, clock and trusted CA configuration. Keep TLS verification enabled.

A curl success confirms that curl reached the specified gateway for that request. It does not prove Chrome selected it. Conversely, curl against a manual host does not evaluate Chrome’s PAC script. For version-specific curl numbers and measured local examples, use the linked refusal and CONNECT guides.

ERR_MANDATORY_PROXY_CONFIGURATION_FAILED: a required PAC failed

ERR_MANDATORY_PROXY_CONFIGURATION_FAILED appears when Chrome must use a proxy auto-configuration (PAC) script and cannot: the script could not be downloaded, could not be parsed, or failed when it ran. Because the configuration is mandatory, Chrome does not fall back to a direct connection. The proxy servers named in the script may be perfectly healthy; the failure comes earlier. Chromium error definition.

Find where the PAC setting comes from

  1. Open chrome://policy and look for proxy policies such as ProxySettings, ProxyMode or ProxyPacUrl. A value set there comes from an administrator, and the PAC is usually mandatory by design.
  2. Open chrome://net-internals/#proxy. In Chrome 158 and later it shows the proxy settings Chrome is applying, including a PAC URL. Earlier versions show only the controls to re-apply settings after a fix and to clear proxies Chrome has marked as bad; read the PAC URL from the policy or system settings in the other steps, or record a NetLog (see the report section below), whose Proxy view shows the settings.
  3. Open chrome://settings/system. If an extension controls the proxy, Chrome names it; an extension can set a mandatory PAC script through the proxy API.
  4. On Windows 10 or 11, check Settings > Network & internet > Proxy for Use setup script and its script address, and for Automatically detect settings. On macOS, check System Settings > Network, the active service, Details > Proxies and the Automatic proxy configuration URL.

Check that the script can be fetched and run

  • Fetch failure: open the PAC URL itself in a browser or with a plain request from the same network. A 404, a sign-in page, a certificate error or a host that only resolves on a company network or VPN all stop the script from loading.
  • Parse failure: the response must be JavaScript defining FindProxyForURL(url, host). An HTML error page served with a 200 status still fails as a script.
  • Execution failure: an exception inside FindProxyForURL, or a helper call the script relies on that throws, makes evaluation fail. Ask the script owner to test it with the failing URL’s hostname.

Record the PAC URL, the configuration source and the time, then report them to whoever owns the script. A script which cannot be obtained or evaluated is a different case from a valid script which selects an unreachable proxy; the second case typically shows ERR_PROXY_CONNECTION_FAILED instead. Chrome PAC reference.

Do not clear a required script or add a direct fallback merely to suppress the message; that changes the intended route instead of repairing the configuration. On your own unmanaged device, remove a PAC URL you added and no longer need, then re-apply settings from chrome://net-internals/#proxy and reload one small page.

Keep a useful report

Record the UTC time, Chrome version, exact error code, configuration source, proxy host and port without credentials, destination hostname and the curl result if tested. If an authorised comparison from another network works, report that difference. Share passwords, API keys and credential URLs with neither a screenshot nor a public bug report.

If those details do not explain the route, Chromium’s NetLog instructions describe a capture with chrome://net-export. Use the default privacy mode, reproduce only the small failing request, then stop. Review the capture before sharing; sensitive URLs can still be present.

Sources and scope

Primary references checked on 4 October 2026: Chromium network errors, proxy behaviour, Chrome proxy API and curl documentation. Chromium main-branch definitions are not a verification of every installed Chrome release.

What is not allowed

Test only endpoints you are permitted to access and follow the acceptable-use policy.

More in Connect and debug

Show 25 more

Buy mobile and residential proxy GB

Choose your GB or reserve a mobile device.

Buy pool GB Try 1 GB for EUR 1.49

Once per customer. Cryptocurrency network minimums and fees vary.