Add your proxy connection
- Open the proxy manager and select + Add Proxy.
- Choose the connection type supplied by your provider: HTTP, SOCKS4 or SOCKS5.
- Enter one connection per line in Proxy List. The form accepts
host:port:username:password; use the authentication details required by your provider. - Optionally set the network type, location, tags, expiry date and notes to help you identify the connection.
- Select Add Proxies. Open a browser profile, go to Proxy and select the saved proxy, then save the profile.
Do not publish your proxy list or include live credentials in screenshots. If your provider uses IP allowlisting, confirm the machine is allowed to connect.
HTTP, SOCKS4 and SOCKS5: which should you choose?
Use the protocol offered by your provider and supported by the browser you intend to run. A host and port do not tell you the protocol; copying the right address into the wrong protocol field can still fail.
| Connection type | Practical consideration |
|---|---|
| HTTP | Common for web browsing. Confirm whether the provider supports HTTPS destinations and which authentication method it requires. |
| SOCKS4 | An older SOCKS protocol. Verify the provider's address and authentication requirements rather than assuming SOCKS5 settings apply. |
| SOCKS5 | A newer SOCKS protocol. Actual authentication, DNS and traffic behavior depend on the provider and browser integration. |
Residential, datacenter, mobile and ISP describe the network source rather than the connection protocol. Choose based on a legitimate network requirement and verify the provider’s terms.
Verify the launched browser
- Launch the profile after saving its proxy settings.
- Visit an IP-check page you trust and compare the displayed public IP with the expected endpoint from your provider.
- Check the reported location and the browser timezone. Locations inferred from IP addresses can be approximate.
- Check WebRTC behavior separately when it matters to your workflow. See the WebRTC settings guide.
- Close and reopen the profile to confirm the configuration persists.
An IP check only confirms what that check can observe. It is not proof that every kind of traffic uses the proxy or that a website cannot associate two sessions.
Troubleshoot connection failures
For authentication errors, recheck the username, password and allowlist. For timeouts, check the host, port, provider status and whether the subscription has expired. For an unexpected IP, confirm that you launched the intended profile and saved its proxy assignment.
When asking support for help, share the protocol and exact error with credentials removed. Next, organize your profiles so each workspace uses the intended connection.