Chrome says it cannot connect to the proxy after you entered a socks5:// address
Check Is the type SOCKS5 and does the proxy need a login?
Fix Chrome cannot log in to SOCKS5. Follow steps 2 and 3 and use HTTP.
SOCKS5 Proxy Login in Chrome: Why It Fails and What to Use
Chrome cannot send a SOCKS5 username and password. Use an HTTP proxy in the browser and keep SOCKS5 for tools that support its login.
Why Chrome rejects a SOCKS5 proxy with a login
The SOCKS5 protocol itself allows a login: RFC 1928 lists username/password among its authentication methods. The limit is in the browser, not in your proxy.
The Chromium proxy notes say that no authentication methods are supported for SOCKSv5 in Chrome, and that Chrome will not use credentials embedded in the proxy settings. So writing socks5://LOGIN:PASSWORD@HOST:PORT into a flag or a setting does not log in. Edge and other Chromium-based browsers are built on the same engine, so plan for the same limit.
What you see is usually a page that does not load, or a message that the browser cannot connect to the proxy. Other tools do not share the limit, as the table shows.
Who can use SOCKS5 with a login
| Item | SOCKS5 with login | HTTP proxy with login |
|---|---|---|
| Chrome and Edge | No | Yes (Basic, Digest, Negotiate, NTLM) |
| curl | Yes: socks5h://LOGIN:PASSWORD@HOST:PORT | Yes: http://LOGIN:PASSWORD@HOST:PORT |
| Python Requests | Yes, after pip install "requests[socks]" | Yes: user:password in the proxy URL |
| Puppeteer and Selenium with Chrome | No, same limit as Chrome | Yes, with page.authenticate() or an auth handler |
Read on 11 November 2026 from the Chromium proxy notes, the curl manual page and the Requests documentation. "Yes" means the documentation describes it; test your own versions. The Puppeteer and Selenium rows follow the guides linked below, not a new test.
On Proxy302: use the HTTP port with the same login
The Proxy302 gateway has an HTTP port, 2222, and a SOCKS5 port, 3333. Tested on 4 November 2026: a static ISP per-IP lease connects over the other protocol on that protocol's port with the same username and password, and a rotating residential credential generated as SOCKS5 also works over HTTP on 2222.
The reverse is not safe. A residential credential generated as HTTP failed over SOCKS5 on port 3333 on the main lines, and a per-GB Fixed ISP token connects only over the protocol it was bought with. A datacenter IP carries one protocol: if it is for a browser, choose HTTP when you buy.
Use the same IP in Chrome in 5 steps
Step 1: See which protocol the asset has
Open My assets and copy HOST, PORT, USERNAME and PASSWORD. Port 3333 means SOCKS5, port 2222 means HTTP.
Step 2: Test the login outside the browser
Run the two curl lines below. Replace PORT with 3333 for the SOCKS5 line and 2222 for the HTTP line. Each should print the exit IP.
Step 3: Switch the browser to HTTP
If the HTTP line worked, enter the same HOST with port 2222 and type HTTP in the browser or extension. If it failed, this asset cannot be used over HTTP (for example a per-GB asset or a datacenter IP bought as SOCKS5): generate or buy one with Protocol set to HTTP.
Step 4: Enter the login when the browser asks
Type USERNAME and PASSWORD from My assets when the browser asks for the proxy login.
Step 5: Confirm the exit
Open https://ipinfo.io/json in the browser. The IP and country should be the proxy's, not your own.
Expected result The exit IP differs from your own connection.
Test both protocols with curl
# SOCKS5 with login (the h makes the proxy resolve the host name)
curl -x socks5h://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json
# HTTP with the same login, on the HTTP port
curl -x http://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/jsonExample only: replace the placeholders with the values from My assets. If the password has special characters such as @, write them percent-encoded (%40 for @), because curl URL-decodes the login in the proxy string.
If it still fails
curl works over SOCKS5 on 3333 but the HTTP line is reset or times out
Check Which protocol was the asset issued with, and what type is it (per-IP lease or per-GB)?
Fix Per-GB assets and datacenter IPs keep one protocol. Buy or generate one with Protocol set to HTTP.
407 or the sign-in box keeps coming back
Check Did you type the full username and password, with special characters?
Fix Copy them from My assets instead of typing. In curl, percent-encode special characters.
FAQ
Does Chrome support a SOCKS5 proxy with a username and password?
No. The Chromium proxy notes say no authentication methods are supported for SOCKSv5 in Chrome. A SOCKS5 proxy without a login can work; one with a login needs an HTTP proxy or a tool that supports it.
Can I write the login in the proxy address, like socks5://user:pass@host:port?
Not in Chrome: it does not use credentials embedded in proxy settings. curl and Requests do accept them in the proxy URL.
Which protocol should I choose for a browser?
HTTP. Choose it when you buy or generate the proxy; a datacenter IP or a per-GB Fixed ISP asset keeps the protocol it was bought with.
Why does my SOCKS5 proxy work in curl but not in Chrome?
curl can send the SOCKS5 login and Chrome cannot. The proxy is fine; the browser is the limit.
Prices and limits
A static ISP IP costs US$0.50 for 1 day and US$7.99 for 30 days, the same in every country, and you choose HTTP or SOCKS5 when you buy. There is no free trial; the smallest purchase is one IP for one day.
Read next
Chrome proxy setup
Set a proxy in Google Chrome: system settings, the --proxy-server flag, why SOCKS5 with a login does not work, extensions and a check.
407 Proxy Authentication Required
HTTP 407 Proxy Authentication Required comes from the proxy server, not from the website you are trying to reach.
Proxy address, port, username and password
Every working proxy is described by five basic fields: protocol, host address, port, login, and password.
Puppeteer proxy setup
Set an HTTP proxy in Puppeteer with --proxy-server, page.authenticate and browser contexts, and check the exit IP.
ISP proxies (static residential)
Fixed static ISP proxies: a residential-grade IP that stays the same for the whole term. For social accounts, stores and AI tools. HTTP and SOCKS5.
View options and pricingReference links
5
- Chromium docs: Proxy support in Chrome
Official documentation · Confirmed on:
Read on 11 November 2026: "No authentication methods are supported for SOCKSv5 in Chrome"; Chrome "will not use any credentials embedded in the proxy settings"; HTTP proxies support Basic, Digest, Negotiate and NTLM.
- RFC 1928: SOCKS Protocol Version 5
Official documentation · Confirmed on:
Read on 11 November 2026: lists the commands CONNECT, BIND and UDP ASSOCIATE and the authentication methods no authentication, GSSAPI and username/password; the introduction says the protocol does not forward ICMP messages.
- curl manual page
Official documentation · Confirmed on:
Read on 11 November 2026: -x/--proxy accepts socks4://, socks4a://, socks5:// and socks5h://, and a user and password in the proxy string are URL-decoded (%40 for @); --write-out defines time_namelookup, time_connect (TCP connect to the remote host or proxy), time_appconnect, time_starttransfer and time_total.
- Requests docs: Advanced usage
Official documentation · Confirmed on:
Read on 11 November 2026: a Session reuses the underlying TCP connection to the same host (keep-alive is automatic inside a session); a proxy URL can carry user:password; SOCKS needs pip install "requests[socks]", and socks5 resolves names on the client while socks5h resolves them on the proxy.
- Proxy302 product facts and price list
Product observation · Confirmed on:
Product facts file of the site (values checked against the console, the backend and the price table on 18-19 October 2026, protocol tests of 4 November 2026 and the rotating datacenter line on 10 November 2026): products, prices in US$ (1 PTC = US$1), lease terms, protocols and ports, countries, 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.