Using your proxy in Chrome or Firefox, with nothing to install

Your four values

Everything starts on your proxy's card in the panel. The copy button hands you a line in this format:

frproxy.com:15007:your_username:your_password

That is host, port, username, password. Every proxy carries two ports, one HTTP and one SOCKS5, with the same credentials and the same exit IP. The SOCKS port is the HTTP port plus 50: if your HTTP port is 15007, your SOCKS port is 15057.

Every one of our proxies requires a username and a password. None is open, none authorises by IP address. That detail is not paperwork: it decides what works in which browser, and it rules out half the recipes you will read elsewhere.

No browser does authenticated SOCKS5

This is the fact that rules out half the recipes you read elsewhere, including on this site until this revision. Neither Chrome nor Firefox implements SOCKS5 authentication (RFC 1929): your proxy's SOCKS port is out of reach of both.

Measured on 2026-09-05 with Firefox 154: facing a SOCKS5 server that demands a username, the browser announces a single method, "no authentication". When authentication is forced on it anyway, it sends nothing at all: the code is not there. The same test with curl announces the method and hands over the credentials, so it is the browser that is missing it, not the server.

What that means in practice: in a browser, use the HTTP port. For SOCKS5 you need a real SOCKS client (Proxifier), a WireGuard tunnel, or an antidetect browser, which ships its own network stack.

Firefox: the HTTP port, in five clicks

Firefox has its own setting, independent of the system: it does not touch the rest of the machine.

☰ → Settings → General → at the very bottom, Network Settings → Settings…

Tick Manual proxy configuration.
HTTP Proxy: frproxy.com, Port: your HTTP port (15007 in our example).
Tick Also use this proxy for HTTPS.

On the HTTP port it is the proxy that resolves domain names: your internet provider does not see the list of sites you visit.

On the first page load, Firefox asks for the username and password. Let it save them.

If it asks again at every start, about:config → signon.autologin.proxy → true. Firefox then replays the saved credentials without showing the prompt.

One profile per context

A proxy setting applies to all of Firefox. To separate two contexts, two proxies and two sets of cookies, use two profiles: about:profiles → Create a New Profile → Launch profile in new browser. Both windows run side by side, each with its own proxy, history and logins.

WebRTC

A WebRTC call can open its connection outside the proxy and hand your real address to the page. In about:config: media.peerconnection.ice.proxy_only → true. WebRTC keeps working, but only through the proxy. Details in WebRTC and DNS leaks.

Chrome, Edge, Brave: a fallback method

These three share the same engine, so the same rules and the same two refusals.

Refusal 1: no authenticated SOCKS5, like Firefox and for the same reason. And here the failure is not always announced: users report a silent fallback to a direct connection, the page loads, and your real IP is what loaded it. Never conclude from a page that opens: check.

Refusal 2: no password on the command line. On the HTTP port, Chromium ignores the username:password@ part of a proxy URL. Writing --proxy-server="http://user:pass@frproxy.com:15007" transmits nothing. There is no command-line switch that supplies those credentials.

So the HTTP port it is, with a mandatory login prompt on the first load:

chrome.exe --proxy-server="http://frproxy.com:15007" --user-data-dir="C:\chrome-frproxy"

On macOS:

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
  --proxy-server="http://frproxy.com:15007" --user-data-dir="$HOME/chrome-frproxy"

On Linux:

google-chrome --proxy-server="http://frproxy.com:15007" --user-data-dir="$HOME/.chrome-frproxy"

--user-data-dir is not optional. It gives this instance its own cookies, separate from your everyday Chrome. And above all, without it, if Chrome is already running your command merely opens a tab in the existing window: the proxy is ignored, with no warning whatsoever. It is the number one cause of "I followed the steps and my IP did not change".

Treat this shortcut as troubleshooting, not as an installation. It gets you through a one-off test, or a machine you do not want to install anything on. Day to day, retyping the password at every launch wears thin fast: on Chrome, Edge and Brave the real answer is an extension that stores the credentials and replays them for you, see FoxyProxy.

Checking in thirty seconds

Open https://api64.ipify.org in the configured window. You should read the IP shown on your proxy's card in the panel.

Do not use api.ipify.org without the 64: that service only answers over IPv4. Our proxies exit over IPv4 and IPv6; on an IPv6 exit the short version stays silent and you conclude there is a fault where there is none. The subject is covered in Checking that your proxy works.

If nothing loads, the error message names the cause: see 407, timeout, connection refused.

What this method does not do

It does not change your fingerprint. Canvas, WebGL, installed fonts, resolution, time zone, language: all of it stays your machine's. Two accounts opened this way, even behind two different proxies, are linked in a single request. For several identities you need an antidetect browser: AdsPower, Dolphin{anty}, BitBrowser.

It only covers the browser. Your scripts, your desktop clients and the rest of the system go out over your usual connection, see Proxifier.

For a single account to look after, it is free, it takes five minutes, and it is enough.