Browser Setup · 1 min read

How to Set Up a Proxy in Chrome and Firefox

A browser proxy routes just that browser's traffic through a remote server, hiding your origin IP for web requests. Here is how to point Chrome and Firefox at an authenticated SOCKS5 or HTTP proxy and confirm it actually works.

System proxy vs. browser extension

There are two ways to send a browser through a proxy, and the difference is scope. A system proxy — set in your operating system's network settings — is followed by Chrome, Edge, and most desktop apps at once. A browser-level proxy, such as Firefox's built-in settings or a FoxyProxy extension, affects only that one browser and leaves everything else on your direct connection.

That last point matters: a browser proxy does not hide your IP in other apps, your download client, or your terminal. If you want every app on the device covered, use the WireGuard VPN instead. For per-site or per-tab control, an extension wins.

MethodScopeBest for
System proxy settingsWhole OS (Chrome + most apps)One proxy for everything on the machine
Firefox native settingsFirefox onlyIsolating a single browser
FoxyProxy extensionThat browser, per-site rulesSwitching proxies and per-domain routing

All examples below use the placeholder host proxy.s4m.online — port 1080 for SOCKS5 and 3128 for HTTP — with your account's USER:PASS. See paid proxies for credentials, or the free proxy list to experiment (use at your own risk).

Firefox: native proxy settings

Firefox has its own proxy configuration, independent of the operating system.

Open Network Settings

Go to Menu, then Settings, search for proxy, and click Settings next to Network Settings.

Pick manual configuration

Select Manual proxy configuration. For SOCKS5, fill SOCKS Host proxy.s4m.online and Port 1080, then choose SOCKS v5. For HTTP, set HTTP Proxy proxy.s4m.online and Port 3128.

Route DNS through the proxy

Tick 'Proxy DNS when using SOCKS v5' so name lookups travel through the proxy and your real DNS does not leak.

Save and authenticate

Click OK. On the first request Firefox shows a login box — enter your s4m USER and PASS. It remembers them for the session.

Chrome: FoxyProxy extension

Chrome follows the OS proxy by default; an extension keeps the change inside Chrome and handles auth.

Install FoxyProxy

Add FoxyProxy Standard from the Chrome Web Store. It gives per-browser control without touching OS settings and handles SOCKS5 authentication that Chrome's system dialog does not.

Add the proxy

Open FoxyProxy options, click Add, and set a title like s4m. Choose proxy type SOCKS5 (or HTTP).

Enter host, port, and auth

Host proxy.s4m.online, Port 1080 for SOCKS5 or 3128 for HTTP. Add your Username and Password (USER:PASS).

Enable it

Click the FoxyProxy toolbar icon and select your s4m entry. To proxy all of Chrome via the OS instead, use Settings, then System, then Open your computer's proxy settings.

Verify the proxy

Confirm requests actually exit through the proxy IP, not yours.

bash
# Test the SOCKS5 proxy — socks5h resolves DNS through the proxy too
curl -x socks5h://USER:[email protected]:1080 https://api.ipify.org

# Test the HTTP proxy
curl -x http://USER:[email protected]:3128 https://api.ipify.org

# Expected output: the proxy's IP address, not your home/office IP.
# In the browser, open an IP-check page — it should show the same proxy IP.
# Reminder: only this browser is proxied; other apps still show your real IP.

Common issues

Login keeps failing

Re-check USER:PASS with no stray spaces. Credentials come straight from your s4m account, and a rotated password breaks any saved browser login.

IP check still shows you

The proxy may not be enabled, or the entry is toggled off. Turn the FoxyProxy entry on, reload the page, and re-run the check.

DNS looks like it is leaking

Use SOCKS5 with 'Proxy DNS' ticked in Firefox, or socks5h in curl, so lookups go through the proxy rather than your local resolver.

FAQ

Questions, answered

Do Chrome and Firefox support SOCKS5 with a username and password?

Yes. Firefox prompts for the username and password natively on the first request. Chrome's OS proxy dialog does not handle SOCKS5 auth well, so use the FoxyProxy extension, which stores the credentials for you.

Does a browser proxy hide my IP everywhere on my device?

No. It only affects the browser you configured. Other apps, background services, and your terminal keep using the direct connection. For whole-device coverage, use the s4m WireGuard VPN instead.

Should I use the SOCKS5 or the HTTP port?

SOCKS5 on port 1080 handles all TCP traffic and can route DNS through the proxy (socks5h), so it is the safer default. HTTP on port 3128 is fine for plain web browsing.

The IP-check page still shows my real IP or leaks DNS. Why?

Make sure the proxy is actually enabled, then enable 'Proxy DNS' in Firefox or use socks5h with curl. If a site forces a different route, toggle the extension entry off and on and reload.

Are s4m proxies residential or datacenter?

They are authenticated SOCKS5 and HTTP datacenter proxies, billed metered and pay-as-you-go. An optional dedicated personal IP add-on can be bound to a proxy or to the VPN.

Proxies that hide your origin IP

s4m runs authenticated SOCKS5 and HTTP datacenter proxies — metered, pay-as-you-go, with an optional dedicated personal IP you can bind to a proxy or the VPN. Need every app covered instead of one browser? The VPN routes the whole device. Check plans on the pricing page.

People found this page by searching for

Real search phrases this page answers — the linked ones open the page that covers them in depth.