ERR_PROXY_CONNECTION_FAILED in Chrome means the browser could not resolve the configured proxy's hostname or open a network connection to its address and port. Chrome did not reach the destination website, and it may not have reached the proxy at all.

The fastest fix is to test the same page without the proxy, then verify one proxy's host, port, and protocol outside Chrome. If direct browsing works but both Chrome and a command-line test fail through the proxy, focus on the proxy endpoint, local firewall, network policy, or provider status—not cookies, cache, or the destination site.

Do not remove a work or school proxy without approval. On a managed device, check whether policy or a proxy auto-configuration (PAC) script controls Chrome before changing system settings.

ERR_PROXY_CONNECTION_FAILED: Quick Fix

Work through these checks in order:

1. Open a known working website without the proxy. If direct browsing also fails, repair the underlying internet connection first.
2. Confirm whether you intended to use a proxy. Remove an unknown stale setting; keep an organization-managed setting and contact its administrator.
3. Recopy the proxy host and port. Do not put a URL path, spaces, or the target website's address in the proxy field.
4. Match the protocol: HTTP, HTTPS, or SOCKS5. An HTTP endpoint will not work when labeled as SOCKS5.
5. Test the endpoint with curl from the same computer and network.
6. Temporarily disable only unneeded proxy/VPN extensions or conflicting VPN clients, then retry.
7. Check chrome://policy for managed proxy settings and verify any PAC URL with the administrator.

What the Chrome Error Actually Means

Chromium defines ERR_PROXY_CONNECTION_FAILED as network error -130. It occurs when Chrome cannot create a connection to the proxy server because the proxy name could not be resolved or a socket could not connect. Chromium explicitly distinguishes it from a failure during an HTTP proxy's CONNECT tunnel.

That boundary saves time. This error is usually about the path from Chrome to the proxy, not the path from the proxy to the website.

If Chrome shows a 407 or keeps reopening a credential prompt, use the 407 Proxy Authentication Required guide. If this happens only in browser automation, the Puppeteer proxy server errors guide covers launch arguments and page authentication without turning this Chrome-wide diagnosis into a framework tutorial.

1. Confirm Whether Chrome Should Use a Proxy

First compare direct and proxied access. On a personal device where a proxy is optional, record the current setting and temporarily turn the proxy off. Then fully close Chrome, reopen it, and load two unrelated, reliable sites.

• If both sites work directly, the proxy path is the variable.
• If neither works directly, the proxy error may be only one symptom of a DNS, Wi-Fi, router, firewall, or ISP problem.
• If the proxy is required by an employer, school, or security product, do not bypass it. Ask the administrator to verify the assigned endpoint and PAC configuration.

This test does not prove that a destination permits your activity. It only separates a broken proxy connection from a broken general connection.

2. Check the Proxy Setting Chrome Is Really Using

Chrome normally uses the operating system's network settings, including proxy settings. Open Chrome's settings, search for proxy, and select the option that opens your computer's proxy settings.

Windows 10 and 11

Open Settings > Network & internet > Proxy. Microsoft documents three possible sources: automatic detection, a setup script, and a manual proxy.

• If you do not intentionally use a proxy, turn off an unknown Use setup script or Use a proxy server entry after recording it.
• If you do use one, verify the server name or IP and port against the current provider or administrator details.
• If automatic, script, and manual settings conflict, ask which mode the network expects instead of enabling all three.

For a Windows diagnostic warning rather than Chrome error -130, follow the separate guide for when Windows could not automatically detect the network's proxy settings.

macOS

Open System Settings > Network, select the active network service, choose Details, then Proxies. Apple exposes auto-discovery, PAC, HTTP, HTTPS, and SOCKS settings separately. Enable only the mode and fields your provider or administrator supplied.

Chrome extensions and managed policy

An extension can control proxy settings even when the operating system screen looks correct. Open chrome://extensions, identify proxy or VPN extensions, and disable only those you do not need. Retry with one intended proxy controller active.

Next open chrome://policy and look for proxy-related policy. If Chrome says Managed by your organization, a policy can override user choices. Copy the policy name and value for the administrator; repeatedly editing the system proxy will not beat a mandatory policy.

3. Verify Host, Port, Protocol, and Credentials

A proxy address needs a reachable host and the correct listening port. Private proxies usually also need a username and password, but those credentials are not part of the host field.

Suppose the provider gives you:

proxy.example.com:8080:USERNAME:PASSWORD

The connection details are:

Host: proxy.example.com
Port: 8080
Protocol: HTTP (confirm with the provider)
Username: USERNAME
Password: PASSWORD

Check for these common mistakes:

• A copied comma, space, slash, or quotation mark in the host or port.
• A dashboard hostname paired with a port from a different proxy product.
• An HTTP proxy entered in a SOCKS field, or a SOCKS5 proxy entered as HTTP.
• An expired endpoint, canceled plan, or region gateway no longer assigned to the account.
• A proxy restricted by client-IP allowlisting while your public IP has changed.

Do not change an HTTP proxy to HTTPS just because the destination starts with https://. Chrome can load HTTPS destinations through an HTTP proxy by using the CONNECT method. The proxy scheme describes how Chrome connects to the proxy, not the destination URL.

Chrome's manual proxy settings also do not use credentials embedded in the proxy server value. Let Chrome's normal authentication flow prompt for credentials, or use the structured authentication method required by your extension or automation tool. If you only need to rearrange list fields, the proxy converter avoids manual copy errors.

Chrome does not support SOCKS5 username/password authentication. A successful authenticated SOCKS5 test in curl therefore does not prove that Chrome can use the same endpoint directly. Use a provider-supported HTTP proxy, a source-IP-allowlisted SOCKS5 endpoint, or a local client that handles the upstream authentication.

4. Test the Proxy Outside Chrome

Test from the same machine and network where Chrome fails. This keeps office egress rules, home router behavior, DNS, and firewall policy constant.

For an authenticated HTTP proxy:

curl -v --noproxy "" --proxy-user USERNAME \
  --proxy "http://proxy.example.com:8080" \
  https://ipv4.unknownproxies.com/ip

For SOCKS5 with proxy-side hostname resolution:

curl -v --noproxy "" --proxy-user USERNAME \
  --proxy "socks5h://proxy.example.com:1080" \
  https://ipv4.unknownproxies.com/ip

Replace USERNAME with your proxy username. curl prompts for the password, so it does not appear in the command. --noproxy "" clears bypass rules for this test, including NO_PROXY and no_proxy, so the IP check must use the selected proxy. This override requires curl 7.53.0 or later.

Read the earliest failure, not just the final line:

• Could not resolve proxy points to the proxy hostname, DNS, or a typo.
• Connection refused usually means the host answered but nothing accepted a connection on that port.
• Connection timed out points to an unreachable route, blocked port, firewall, or offline endpoint.
• 407 proves the proxy answered and moves the problem to credentials or account authorization.
• A returned IP address proves the basic proxy route works outside Chrome.

Do not put real proxy passwords in shell commands, tickets, or screenshots. Do not share unredacted verbose output. Redact credentials and share timestamps, the proxy hostname, port, protocol, and exact error instead.

5. Isolate Extensions, VPNs, Firewalls, and Security Software

If curl works but Chrome fails, compare Chrome's unique layers:

1. Disable an unneeded proxy or VPN extension and restart Chrome.
2. Disconnect a separate VPN if the proxy is not supposed to run inside it.
3. Try a fresh Chrome profile with no extensions.
4. Check whether endpoint security or a local firewall blocks Chrome but allows the terminal.
5. Test another network, such as a phone hotspot, if policy allows it.

Change one variable at a time. Turning off every security control at once can hide the cause and leave the device exposed. On managed systems, have the administrator review firewall or endpoint-security logs instead of disabling protection.

If every client fails only on one office or cloud network, the network may block the proxy port or destination. If the same proxy fails from multiple unrelated networks, the endpoint or provider route is the stronger suspect.

6. Check PAC Scripts and Collect a Chrome NetLog

A PAC script chooses a proxy per URL. A stale PAC URL, script error, or unexpected DIRECT/proxy rule can make behavior differ by destination. If the PAC file is organization-owned, provide the failing URL and timestamp to its administrator rather than editing the script locally.

For a repeatable Chrome-only failure, open chrome://net-export/, start logging, reproduce the error once, and stop logging. A NetLog can show proxy resolution and connection events that ordinary DevTools does not capture early enough.

Treat NetLog files as sensitive. They can contain browsing and network metadata even when exported in a sanitized mode. Share them only with a trusted administrator or support team through an approved channel.

7. Reset Only After You Identify the Layer

Clearing cookies and browsing history rarely fixes ERR_PROXY_CONNECTION_FAILED because the failure happens before Chrome reaches the website. Prefer the smallest reset that matches the evidence:

• Restart Chrome after correcting a proxy setting.
• Restart the computer if an OS proxy service or VPN client is stuck.
• Flush DNS only when the proxy hostname fails to resolve while known hostnames resolve normally.
• Reset Chrome settings only when an extension or changed browser preference remains the likely cause.
• Use a full Windows network reset only after safer connection and proxy checks fail; it can remove adapters and require VPN software to be reconfigured.

Replacing the proxy is reasonable when its hostname, port, protocol, and authorization are correct but the endpoint remains unreachable across multiple allowed networks. Buying or rotating more proxies will not fix a typo, blocked outbound port, conflicting policy, or wrong protocol.

Prevent the Error From Returning

For repeatable browser and automation work:

• Store host, port, protocol, and credentials as separate fields.
• Test one endpoint before importing a full proxy list.
• Monitor DNS resolution, TCP connection time, authentication results, and plan expiry separately.
• Keep a known direct test and a known proxy test for comparison.
• Record which extension, policy, PAC script, or command-line flag owns the proxy setting.
• Stop automated retries after repeated connection failures; fast retries do not revive an unreachable socket.
• Keep one proxy identity stable during login or other multi-step sessions.

Once a working route is proven, choose residential proxies for legitimate workflows that need rotating or sticky consumer-style IPs, or compare ISP proxy plans for stable dedicated routes. Neither product type overrides destination rules, account permissions, local network policy, or site terms.

FAQ

Is ERR_PROXY_CONNECTION_FAILED caused by the website?

Usually no. Chrome emits it when it cannot resolve or connect to the configured proxy endpoint. The destination website normally has not received the request.

Why does Chrome fail when other browsers work?

Chrome may be using a proxy extension, managed policy, PAC result, command-line flag, or profile-specific configuration that the other browser does not use. Compare the effective proxy settings, then test a fresh Chrome profile.

Does clearing the Chrome cache fix the error?

Usually not. Cache and cookies affect content after a connection exists. This error occurs earlier, while resolving or connecting to the proxy.

What is the difference between ERR_PROXY_CONNECTION_FAILED and ERR_TUNNEL_CONNECTION_FAILED?

ERR_PROXY_CONNECTION_FAILED means Chrome could not establish the connection to the proxy itself. ERR_TUNNEL_CONNECTION_FAILED means a proxy tunnel could not be established, so check HTTPS tunneling, proxy responses, destination reachability, and authentication.

Can a new proxy fix ERR_PROXY_CONNECTION_FAILED?

Yes, if the configured endpoint is offline, expired, unreachable, or no longer assigned. A new proxy will not fix the wrong scheme, a typo, local firewall rules, conflicting extensions, or mandatory organization policy.

Conclusion

Fix ERR_PROXY_CONNECTION_FAILED by proving the direct connection first, finding the proxy setting Chrome actually uses, and validating one host, port, and protocol outside the browser. The decisive test is simple: if the proxy also fails in curl, repair the endpoint or network path; if it works there, isolate Chrome's extension, policy, profile, PAC, or authentication layer.

Technical references: Chromium network error definitions, Chromium proxy support, Microsoft Windows proxy settings, and Apple macOS proxy settings.