Skip to content

ERR_SOCKS_CONNECTION_FAILED: Causes and Fixes in Chrome

Chrome could not finish the SOCKS handshake with your proxy: how to find out why and fix it.

What the error means

Chrome shows ERR_SOCKS_CONNECTION_FAILED when it cannot complete the connection to a SOCKS proxy for the page you opened. The Chromium error list describes it as a failure to establish a connection to the SOCKS proxy server for a target host.

In the Chromium code the error is returned when the proxy closes the connection during the first greeting, when its first reply byte is not SOCKS version 5, when it picks an authentication method other than none, and when its answer to the connect request is malformed or a refusal. So the page never loaded because the conversation with the proxy broke down, not because the website was unreachable.

The 3 most common causes

1. The proxy needs a username and password. Chrome greets the proxy with a single offer, no authentication, and the Chromium notes say no authentication methods are supported for SOCKSv5. A proxy that answers with the username/password method (or with no acceptable method) ends the handshake. This is the usual cause with a paid proxy, and a login written into socks5://LOGIN:PASSWORD@HOST:PORT is not used by Chrome.

2. The port belongs to another protocol. If you type an HTTP proxy port into a socks5:// setting, the reply does not start with SOCKS version 5 and Chrome gives up. On Proxy302 HTTP is port 2222 and SOCKS5 is port 3333, and each asset in My assets is shown with one protocol.

3. The proxy is not answering properly: a mistyped host or port, a firewall that cuts the connection, an expired lease, or a proxy that closes the connection straight away. Chrome cannot tell these apart, so test the same details outside the browser.

Which Chrome proxy error is it

Which Chrome proxy error is it
ItemCodeWhat failedFirst thing to check
ERR_SOCKS_CONNECTION_FAILED-120The SOCKS conversation with the proxySOCKS login, port, protocol
ERR_SOCKS_CONNECTION_HOST_UNREACHABLE-121The SOCKS proxy could not reach the websiteThe site and the IP's route to it
ERR_PROXY_CONNECTION_FAILED-130The connection to the proxy itselfHost, port, firewall, system proxy
ERR_TUNNEL_CONNECTION_FAILED-111An HTTP proxy would not open a tunnelLogin and status from curl -v

Names and meanings from the Chromium net error list, read on 16 November 2026. Only the first two rows are SOCKS errors.

Test the SOCKS5 details with curl

# SOCKS5 with login (DNS is resolved by the proxy)
curl -v -m 20 -x socks5h://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json

# The same IP over the HTTP port, which Chrome can use with a sign-in prompt
curl -v -m 20 -x http://LOGIN:PASSWORD@HOST:2222 https://ipinfo.io/json

# A working proxy prints the exit IP, country and network as JSON.

Example only: replace LOGIN, PASSWORD, HOST and PORT with the values from My assets. On Windows PowerShell use curl.exe. If curl works over SOCKS5 but Chrome fails, the cause is the missing SOCKS5 login support in Chrome.

Fix it in 5 steps

  1. Step 1: Copy the details again

    Open My assets (the console page that holds everything you bought) and copy HOST, PORT, USERNAME and PASSWORD instead of typing them.

  2. Step 2: Run the curl test

    Use the SOCKS5 command above with the same host and port Chrome uses.

    Expected result Either the exit IP as JSON, or a curl error that names the failing step.

  3. Step 3: Match protocol and port

    SOCKS5 is port 3333 and HTTP is port 2222. If the port belongs to an HTTP asset, set it as an HTTP proxy, not socks5://.

  4. Step 4: Give Chrome an HTTP proxy

    Chrome cannot log in to SOCKS5. Use an HTTP asset on port 2222, or set the HTTP proxy in the system and answer the sign-in prompt. A per-IP static lease from Proxy302 also answers on port 2222 with the same login (tested 4 November 2026).

  5. Step 5: Still failing? Check the asset and send a ticket

    In My assets check that the lease is running. If curl fails too, send a ticket with the order number: a failed asset is reissued.

Symptom by symptom

curl over SOCKS5 works, Chrome shows -120

Check Compare: does the SOCKS5 asset need a login? Chrome has no SOCKS5 login.

Fix Use an HTTP asset on port 2222 in Chrome and keep SOCKS5 for curl, Python or other tools that support a login.

Stop when Do not keep editing the socks5:// line with the login inside: Chrome ignores it.

curl over SOCKS5 fails too

Check Check host, port and that the IP is still leased.

Fix Copy the details again from My assets, try the other protocol port, then send a ticket with the order number.

Stop when If both ports fail for a lease that has not expired, stop and send the ticket.

Chrome shows -121 instead

Check The proxy answered; the site or the IP's route to it is the problem.

Fix Open another website through the same proxy. If only one site fails, that site is the cause.

Stop when If every site fails, treat it as an IP problem and send a ticket.

-120 only on one device

Check Look for another proxy app, extension or policy on that device.

Fix Turn off the extra proxy tool, check chrome://net-internals/#proxy and the system proxy settings.

Stop when If a second device works with the same details, the first device's settings are the cause.

How to do it with Proxy302

For a browser, buy a static ISP IP with the HTTP protocol (port 2222), because Chrome supports no login for SOCKS5. Copy HOST, PORT, USERNAME and PASSWORD from My assets, enter them in the browser, and confirm the exit at https://ipinfo.io/json. Keep SOCKS5 (port 3333) for tools that can send a SOCKS5 login.

A static ISP IP costs US$0.50 for one day and US$7.99 for 30 days, about US$0.27 a day (7.99 / 30), the same in every country. There is no free trial, and the smallest purchase is one IP for one day.

FAQ

What does ERR_SOCKS_CONNECTION_FAILED mean?

Chrome could not establish a connection to the SOCKS proxy server (error -120). The handshake with the proxy failed before the website was reached.

Why does it happen with a SOCKS5 proxy that has a login?

Chrome offers only the no-authentication method and supports no SOCKS5 login, so a proxy that requires a login ends the handshake.

How is it different from ERR_SOCKS_CONNECTION_HOST_UNREACHABLE?

-121 means the SOCKS proxy was reached but could not connect to the website. -120 means the connection to the proxy itself failed.

Is it the same as ERR_TUNNEL_CONNECTION_FAILED?

No. That error comes from an HTTP proxy that would not open a tunnel; see the separate guide for reading its status.

Does it help to change the port to 1080?

1080 is only the default SOCKS port in Chrome. Use the port shown for your asset: 3333 for SOCKS5 and 2222 for HTTP on Proxy302.

Reference links

5
  1. Chromium source: net error list (net_error_list.h)

    Official documentation · Confirmed on:

    Read on 16 November 2026: SOCKS_CONNECTION_FAILED (-120) is a failure to establish a connection to the SOCKS proxy server for a target host; SOCKS_CONNECTION_HOST_UNREACHABLE (-121) is the SOCKS server failing to connect to the target because that host is unreachable; PROXY_CONNECTION_FAILED (-130) is a failure to create a connection to the proxy server; TUNNEL_CONNECTION_FAILED (-111) is a tunnel through the proxy that could not be established.

  2. Chromium docs: Proxy support in Chrome (net/docs/proxy.md)

    Official documentation · Confirmed on:

    Read on 16 November 2026: Chrome supports SOCKS5 with scheme socks5://, default port 1080; no authentication methods are supported for SOCKSv5 in Chrome; Chrome will not use credentials embedded in the proxy settings; name resolution is always done on the proxy side; SOCKS5 relays TCP only, not UDP; --proxy-server takes URIs such as socks5://mysocks:1080.

  3. Chromium source: SOCKS5 client socket (socks5_client_socket.cc)

    Official documentation · Confirmed on:

    Read on 16 November 2026: the Chrome SOCKS5 client sends the greeting bytes 05 01 00, offering only the no-authentication method; it returns ERR_SOCKS_CONNECTION_FAILED when the server closes during the greeting, when the first reply byte is not version 5, when the chosen method is not 00, and on a malformed or failed connect reply.

  4. RFC 1928: SOCKS Protocol Version 5

    Official documentation · Confirmed on:

    Read on 16 November 2026: the client lists the methods it supports and the server picks one; X'00' is no authentication, X'02' is username/password, X'FF' means no acceptable method and the client must then close the connection.

  5. Proxy302 product facts and price list

    Product observation · Confirmed on:

    Product facts file of the site, checked 16 November 2026: gateway ports HTTP 2222 and SOCKS5 3333; each static IP asset is issued with one protocol; per-IP static leases also answer on the other protocol with the same login (tested 4 November 2026), newly bought per-GB Fixed ISP on both protocols; static ISP per-IP prices; no free trial.

Ready to try it?

Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.