ERR_NO_SUPPORTED_PROXIES most commonly appears when Chrome, Yandex Browser, or automation tools on Chromium (Selenium, Puppeteer, Playwright) receive a SOCKS5 proxy with a username and password. The proxy itself may be functioning correctly; however, the Chromium-based browser simply cannot handle SOCKS5 authentication using a username and password. There are three solutions: use the same proxy with the HTTP protocol, where the username and password are understood by Chrome, set up a local forwarder without a password, or switch to a browser that supports SOCKS5 with authentication. Below, we will explore the source of the error and how to resolve it in the browser and in the code.
What the error means and who it affects
In the source code of Chromium, the error is briefly described as: NO_SUPPORTED_PROXIES, code −336, meaning "there are no supported proxies in the provided list." The browser has gone through everything provided in the settings and has not found a single proxy through which it can connect. Up to this point, the site has not even been requested, so the error is not related to any blocking on the site's side.
It is most commonly encountered by:
- those who launch Chrome with the flag
--proxy-server=socks5://user:pass@host:port; - developers using Selenium, Puppeteer, and Playwright who pass SOCKS5 proxies with authentication;
- users of Yandex Browser, Edge, Brave, Opera, and Vivaldi: all of them are built on Chromium and behave similarly;
- those who entered a SOCKS5 proxy with a password in a Chrome extension and received an error instead of a page.
Why this happens: Chromium does not send SOCKS5 credentials
The SOCKS5 protocol is described in RFC 1928, and authentication with a username and password is outlined in a separate RFC 1929. When connecting, the client first informs the proxy of the authentication methods it supports: "no authentication" (code 0x00) or "username and password" (code 0x02). Chromium only offers the first option. If the proxy requires a password, no agreement can be reached, and the connection is terminated.
Chrome does not use the username and password embedded directly in the address like socks5://user:pass@host. This is a well-known limitation that has been lingering in the Chromium tracker as issue 40323993, and there is currently no fix.
With HTTP proxies, the situation is different: when the proxy responds with a 407 code and requests authentication, Chrome displays a login and password input window, and extensions and automation tools can fill them in automatically. Therefore, the same proxy works with HTTP, but when using SOCKS5 with a password, it results in ERR_NO_SUPPORTED_PROXIES.
How this looks in automation tools
| Tool | SOCKS5 with username and password | HTTP with username and password |
|---|---|---|
| Chrome and Chromium-based browsers | No, ERR_NO_SUPPORTED_PROXIES error | Yes, via authentication window or extension |
| Playwright (Chromium) | No: the username and password fields are described only for HTTP proxies in the documentation | Yes, via username and password fields |
| Puppeteer | No, the same error in Chromium | Yes, via page.authenticate() |
| Selenium + ChromeDriver | No, the same error in Chromium | Yes, via extension or local forwarder |
| Firefox | Yes, via extensions using the API proxy.onRequest | Yes |
For more details on HTTP proxies with passwords specifically in Selenium, there is a separate analysis: how to pass the proxy username and password in Selenium and Chrome.
What changing the protocol solves and what it does not
It is important to understand that the error refers to the method of connection, not the quality of the proxy. By changing the protocol or connection scheme, you eliminate ERR_NO_SUPPORTED_PROXIES, but you do not change how the site evaluates your IP.
- Solves: the browser starts connecting to the proxy, pages open through the desired IP and country.
- Does not solve: if after fixing the site shows a captcha or 403, the reason lies in the IP's reputation or the browser fingerprint. This is a separate issue, and the protocol does not affect it.
- Does not solve: UDP traffic. Calls in messengers and online games over UDP do not go through HTTP proxies, and Chromium only handles TCP connections over SOCKS5.
How to fix it: step by step
Method 1. Switch the same proxy to HTTP
The quickest way. Many providers offer the same proxy for both HTTP(S) and SOCKS5, with the same username and password. At ProxyCove, each proxy works with both protocols.
- Open the proxy data in your provider's personal account and find the address and port for the HTTP protocol.
- Replace the scheme
socks5://in the settings withhttp://and set the port for HTTP if it differs. - For Chrome without extensions, launch the browser with the flag
--proxy-server=http://host:portwithout the username in the address. Upon the first request, Chrome will display the login and password input window. - In Playwright, pass the proxy like this:
proxy: { server: 'http://host:port', username: '…', password: '…' }. - In Puppeteer, launch the browser with
--proxy-server=http://host:portand callpage.authenticate({ username, password })before navigating to the site. - Check the result: open any IP checking service and ensure that the proxy's IP is displayed, not yours.
Method 2. Local forwarder without a password
If you need SOCKS5 specifically, for example, due to software that only works with it, a local forwarder is placed between the browser and the proxy. It listens on a port on your computer without a password, while connecting to the remote proxy with the username and password.
- Install a forwarder. A popular option is the console utility gost. In the Python library Pydoll, there is a built-in SOCKS5Forwarder for this purpose.
- Run it so that local access is without authentication, while the outgoing connection leads to your proxy with the username and password. For gost, it looks something like this:
gost -L socks5://127.0.0.1:1080 -F socks5://user:pass@host:port. - In Chrome or in the code, specify
--proxy-server=socks5://127.0.0.1:1080, without the username and password. - Check the IP as in the first method.
Only listen to the forwarder on 127.0.0.1. If you open it on all interfaces, anyone on the network can connect to your proxy without a password, and the traffic will be deducted from your balance.
Method 3. IP-based authentication
Some providers allow you to add your IP to a whitelist, allowing the proxy to accept connections without a username and password. Chrome accepts such SOCKS5 connections without errors. The downside is that this method only works for static external IPs: on home internet with a changing address or in the cloud with floating addresses, access will be lost. Check with your provider if this feature is available in their dashboard or support.
Method 4. Use Firefox instead of Chrome
Firefox can pass the SOCKS5 username and password through extensions that use the API proxy.onRequest. If the task is manual rather than automation on Chromium, this is the simplest workaround.
What type of proxy to choose
The protocol itself does not affect the type of proxy: both residential, mobile, and datacenter proxies are usually available via both HTTP(S) and SOCKS5. The choice depends on the task:
- Residential proxies — IPs from home providers. Suitable for sites with anti-bot measures, scraping stores, accessing services from the desired country. Cost $2.70 per GB.
- Mobile proxies — IPs from telecom operators, which thousands of real subscribers use. Useful if the site strictly checks IPs. Cost $3.80 per GB.
- Datacenter proxies — the cheapest ($1.50 per GB) and fastest. Good for APIs, testing, and sites without strict protection, but they are more often recognized as server proxies.
For browsers and automation on Chromium, it is more practical to use HTTP(S): all tools from the table above work with it, and no additional forwarder is needed. Remember that only web traffic over TCP goes through HTTP proxies. Calls and games that operate over UDP will not work through it.
Common mistakes
- Username and password in the flag address.
--proxy-server=http://user:pass@host:portdoes not work even for HTTP: Chrome does not take credentials from the address. They need to be entered in the authentication window, through an extension, or via the tool's API. - Confused port. Many providers have different ports for HTTP and SOCKS5. Using the HTTP protocol on the SOCKS port will result in a connection error, even if the username and password are correct.
- Old extension with SOCKS5. An extension for Chrome may allow entering a username and password for SOCKS5, but the browser will still not pass them. If a SOCKS5 proxy with a password is set in the profile, switch it to HTTP.
- Forwarder exposed to the outside. A local SOCKS5 without a password should only listen on 127.0.0.1.
- Confusion with other errors. ERR_PROXY_CONNECTION_FAILED and ERR_TUNNEL_CONNECTION_FAILED mean that the proxy was selected, but the connection could not be established with it or through it. These are different reasons: incorrect address, port, exhausted traffic, or a refusal on the proxy's side.
Conclusion
ERR_NO_SUPPORTED_PROXIES in Chromium-based browsers almost always means one thing: you provided a SOCKS5 proxy with a username and password, and Chromium does not support such authentication. The quickest solution is to switch the same proxy to HTTP, where Chrome, Playwright, and Puppeteer can input the password. If SOCKS5 is specifically needed, set up a local forwarder or use Firefox. ProxyCove proxies work with both HTTP(S) and SOCKS5 with payment per gigabyte of traffic, so you can choose the protocol based on the tool, not the other way around.
