How to set a proxy in RoxyBrowser

RoxyBrowser is an anti-detect browser: every profile runs with its own fingerprint, its own cookies — and its own proxy, so each account looks like a separate user to the platform. Proxies live in the built-in Proxies manager, and RoxyBrowser supports HTTP, HTTPS, SOCKS5, and SSH connections. This guide covers adding proxies one by one and in bulk, testing them, and assigning one to each profile.

Before you start: proxy details and ports

You'll need your proxy IP address and port. Both are listed in your Dashboard — open your active subscription to see the full connection details. The port depends on the protocol and how you want to authenticate:

Authentication	HTTP port	SOCKS5 port	Good for
Username / password credentials from your Dashboard	8080	1080	The usual choice — RoxyBrowser has username and password fields built in
IP whitelisting no login required	8085	1085	Machines with a static IP — leave the username and password fields empty

With IP whitelisting, you first add your machine's IP address to the whitelist in the Dashboard — after that the proxy accepts connections from it with no credentials.

Step 1. Add proxies to the Proxies manager

Open the Proxies page in RoxyBrowser and click Add. There are two ways to enter a single proxy:

Manually. Select the IP type (IPv4), pick the protocol — HTTP or SOCKS5 — and fill in the Proxy host, Port, Username, and Password fields. On the whitelist ports, leave the last two empty. The refresh URL field is only for rotating proxies that change IP via a link — our proxies don't need it, so leave it blank.

Via Intelligent Recognition. Paste the proxy as a single line and RoxyBrowser parses the fields automatically:

For a whole package, use bulk import: export your list from the Dashboard — the field order and delimiter are configurable at export, so the file comes out in exactly the format above, one proxy per line. Paste the lines into the import box, pick an IP detection channel, tick deduplication if you want it, and click Parse.

Step 2. Test the proxies

Each parsed proxy has a Test action, and the list view has Test All in the upper-right corner — run it after any import. Proxies that fail get filtered out in one click with Delete Failed, but with a fresh list from the Dashboard the usual cause of a failure isn't the proxy — it's a port/authentication mismatch, covered in the last section.

Step 3. Assign a proxy to each profile

When creating a profile, choose Use proxy and pick a saved proxy from the Proxies manager (or add a new one on the spot). For existing profiles, select one or several in the profile list and use Assign existing proxies — RoxyBrowser distributes the saved proxies across the selected profiles. The profile's browser window will route all traffic, cookies, and logins through that IP.

If something doesn't work

The most common causes: a proxy failing the connectivity test usually means the port doesn't match the authentication method (see the table) — credentials with port 8085 or an empty login with port 8080 both fail; on the whitelist ports, check that your machine's IP is actually whitelisted in the Dashboard; if Intelligent Recognition splits the line wrong, check that the fields are separated by colons with no spaces; and if the proxy tests fine but the profile shows your real location, make sure the profile is set to Use proxy and the right proxy is selected. If none of these is it, message us in live chat right on this page — we'll help you get connected.