Which credentials to use#
Use a distinct session identifier for each independent workflow, where the assigned gateway supports it. Confirm the permitted duration and location parameters in your connection details. A residential device can disconnect before the requested duration; a sticky session is not a guarantee of the same IP for days. For a fixed address, compare a dedicated static product.
Chrome and Chromium#
- Chrome uses the operating system's proxy settings by default; change them there (below) and every Chromium browser follows.
- For one dedicated profile, start Chrome with flags:
--proxy-server=\"http://res.proxy-cyber.com:9000\" --user-data-dir=/tmp/proxprofile. The first navigation asks for the username and password. - SOCKS5 with remote DNS:
--proxy-server=\"socks5://res.proxy-cyber.com:9001\" --host-resolver-rules=\"MAP * ~NOTFOUND , EXCLUDE res.proxy-cyber.com\"keeps DNS from leaking (whitelisted IP required: Chrome cannot send SOCKS5 credentials). - Extensions such as SwitchyOmega switch profiles per site and store credentials, useful when you alternate between direct and proxied browsing.
Firefox#
- Settings → Network Settings → Manual proxy configuration.
- HTTP Proxy
res.proxy-cyber.com, port9000, tick "Also use this proxy for HTTPS". Or SOCKS Hostres.proxy-cyber.com, port9001, SOCKS v5, and tick Proxy DNS when using SOCKS v5. - In
about:config, setmedia.peerconnection.enabledtofalseto stop WebRTC from revealing your real address. - Firefox asks for the proxy credentials on the first request and can remember them per profile.
macOS#
System Settings → Network → your interface → Details → Proxies: enable Web Proxy (HTTP) and Secure Web Proxy (HTTPS) with res.proxy-cyber.com and port 9000, tick "Proxy server requires password" and enter the sticky username and password. Safari and most apps follow the system setting; some command-line tools do not, use the environment variables instead.
Windows#
Settings → Network & Internet → Proxy → Manual proxy setup: address res.proxy-cyber.com, port 9000. Windows has no field for credentials; Edge and Chrome will prompt on first use, or whitelist your IP. Add localhost;127.* to the exceptions.
A PAC file for selective proxying#
function FindProxyForURL(url, host) {
// Only these sites go through the German exit; everything else is direct
if (dnsDomainIs(host, ".example.de") || shExpMatch(host, "*.shop-example.de")) {
return "PROXY res.proxy-cyber.com:9000";
}
return "DIRECT";
}Point the browser or OS at the PAC URL (a local file works in Firefox; Chrome and Windows prefer an http:// URL). Credentials are still prompted or whitelisted.
Verify before you trust it#
- Open an IP-echo page: the address must be the exit, in the country you asked.
- Open a WebRTC leak test: only the exit should appear.
- Check the browser's language and time zone match the exit if the site cares about consistency.
Questions people ask#
Why does the browser keep asking for the proxy password?
A wrong password, or a username with a typo in a parameter: the gateway answers 407 and the browser re-prompts. Test the same credentials with cURL to see the exact gateway code.
Can I use a different exit per tab?
Not with browser settings alone: the proxy is per profile or per system. Run separate profiles, or use an extension with per-site rules.