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 are stored in the built-in Proxies manager, and RoxyBrowser supports HTTP, HTTPS, SOCKS5, and SSH connections.
Before you start: proxy details and ports
All the necessary information about proxies purchased from us is in your personal cabinet, in the services section - https://papaproxy.net/panel/clientarea.php?action=products. The port depends on how you authenticate:
| Authentication |
HTTP port |
SOCKS5 port |
Good for |
Username / password
credentials from your personal cabinet |
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 |
What IP whitelisting is and how to set it up is described here.
Step 1. Add proxies to the Proxies manager
Open the Proxies page in RoxyBrowser and click "Add". To enter a proxy manually, select the IP type (IPv4), pick the protocol — HTTP or SOCKS5 — and fill in the Proxy host, Port, Username, and Password fields. 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.
A faster way is Intelligent Recognition: paste the proxy as a single line and RoxyBrowser parses the fields automatically:
123.45.67.89:8080:your-login:your-password
For a whole package, use bulk import. Export your list from the personal cabinet — 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 added proxy has a "Test" action, and the list view has a "Test All" button in the upper-right corner — run it after any import. Proxies that fail get removed in one click with "Delete Failed", but with a fresh list 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.
The rule that keeps accounts alive: one profile — one dedicated IP, permanently. Platforms cross-check the IP history of every account, so profiles shouldn't share proxies or hop between them. That's the use case our dedicated proxies are built for — each IP is reserved exclusively for you, starting from a single proxy. For large profile farms, datacenter packages from 100 IPs keep the per-proxy price low.
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 personal cabinet; 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.
