- Host
- gw.prokso.com
- Port
- 823 HTTP · 824 SOCKS5 — new IP per request · 10000–20000 sticky session, HTTP(S) and SOCKS5
- Username and password
- in your dashboard, on the plan page
Your dashboard generates ready-made lines in the format you need: choose the country, IP type and protocol.
- Host gw.prokso.com, ports 823 (HTTP), 824 (SOCKS5), 10000–20000 (sticky sessions, HTTP or SOCKS5)
- The username and password are in your dashboard on the plan page
- After setup, check your IP on the My IP page
A step-by-step guide to connecting Prokso proxies in Google Chrome. It takes a few minutes.
Step 1. Get the proxy details from your dashboard
Open your plan and copy the host gw.prokso.com, port, username and password. Port 823 is HTTP and 824 is SOCKS5 (both give a new IP for every request); ports 10000–20000 keep one IP (sticky session) for up to 120 minutes and work as both HTTP and SOCKS5 (each port is a separate address). Set the country in the username: username__cr.ua.
Step 2. Open the system proxy settings
Chrome uses the system proxy. In Chrome open Settings → System → Open your computer's proxy settings — the Windows or macOS window opens.
Step 3. Enter the host and port
Turn on manual proxy setup and enter gw.prokso.com and port 823 (or a sticky port 10000–20000 if you need one IP).
Step 4. Enter the username and password
When you open the first website, Chrome asks for the proxy username and password — paste them from your dashboard. If the prompt doesn't appear, use the IP whitelist or the SwitchyOmega extension.
Step 5. Check that it works
Open the My IP page: it should show the proxy's IP address and country, not yours. If the connection fails, double-check the port and protocol, and look up error codes on the Error codes page.
What you should know about proxies in Chrome
Chrome has no proxy settings of its own: it uses the system ones. This means a proxy turned on for Chrome also starts to apply to other programs on the computer that read the system settings. When you finish working, turn the proxy off in the system. Otherwise updates and background programs will spend your plan's traffic.
The system settings accept an HTTP proxy. For SOCKS5 with a username and password, Chrome needs a separate tool: an extension such as SwitchyOmega.
If Chrome does not open sites through the proxy
- The login prompt did not appear. Chrome does not always show it. Turn on the IP whitelist (no password) in your dashboard or set up the proxy through an extension.
- ERR_PROXY_CONNECTION_FAILED. Chrome could not reach the proxy: check the host and port. A breakdown is on the page for this error.
- ERR_TUNNEL_CONNECTION_FAILED. The proxy refused the connection, most often because of the username and password or because the traffic ran out. More details are on the error page.
- A VPN or another proxy extension is running. They take over the settings. Turn them off while you test.
Different proxies for different tasks
The system proxy is the same for the whole browser. If you need different addresses in different tabs, or a separate proxy for only some sites, use an extension with profiles and rules. If you need isolated profiles with their own fingerprint, that is a job for an antidetect browser.
FAQ
Can I set a proxy only for Chrome?
No, Chrome always uses the system proxy. To apply it only in the browser, install the SwitchyOmega extension — its guide is in this section.
Does Chrome support SOCKS5 with a password?
No, only without one. For SOCKS5 switch on the IP whitelist or use HTTP port 823.
Does the proxy work in Incognito mode?
Yes. Incognito mode does not change the network settings: it uses the same system proxy. Extensions are turned off in Incognito by default, so a proxy set through an extension will not work there until you allow it in the extension's settings.
Why does My IP show the proxy while the site still detects my country?
A site looks at more than the IP. The time zone, the browser language, and saved cookies are still yours. Also run the <a href="/en/tools/webrtc-leak-test">WebRTC leak test</a> and open the site in a clean profile.