Per-site routing
FoxyProxy's URL patterns let one site run through a US residential IP while another uses your direct connection. Save a ProxyOmega profile per country and match it to the domains that need it.
Integration Proxy manager
FoxyProxy Integration
FoxyProxy is one of the fastest ways to switch a browser between your real connection and a residential proxy without touching the operating system. This guide walks through adding a ProxyOmega endpoint as a FoxyProxy profile, choosing HTTP or SOCKS5, and enabling it per-tab or for every request. Everything below uses the exact fields FoxyProxy shows in its current options screen.
- 200+countries
- 1.5M+residential IPs
- SOCKS5on every port
FoxyProxy
What is FoxyProxy?
FoxyProxy is a browser extension for Chrome, Firefox, and Edge that manages proxy profiles inside the browser instead of at the operating-system level. You store one or more proxy servers, then flip between them from a toolbar menu. It is popular because it keeps your normal browsing on your real connection while sending only the tabs you choose through a proxy.
The extension comes in two forms. FoxyProxy Standard is the full version with unlimited profiles and URL-pattern matching, so different sites can automatically use different proxies. There is also a Basic version with a single proxy. For working with ProxyOmega you will want Standard, since it lets you save separate profiles for different countries or plans and switch between them in one click.
Because FoxyProxy works at the browser layer, it affects only the browser it is installed in. Other applications on your machine keep using your normal connection. That scoping makes it a clean choice for account management, ad verification, price checking, and any workflow that lives entirely inside a browser tab.
FoxyProxy
Why pair FoxyProxy with residential proxies
A proxy manager is only as good as the network behind it. FoxyProxy handles the switching; ProxyOmega supplies the residential IP addresses that make requests look like ordinary home traffic. Pairing the two gives you granular, per-tab control over which residential exit each site sees.
Clean, real IPs
ProxyOmega residential addresses are sourced from real consumer connections, so sites treat them like genuine visitors rather than datacenter ranges that are easy to flag.
One click on and off
Testing whether a block is IP-based? Toggle the profile from the toolbar and reload. No system settings to unwind, no restart required.
FoxyProxy
How to add ProxyOmega to FoxyProxy
Grab your credentials from the ProxyOmega dashboard first. Your username is your account username plus any targeting parameters; your password is the account API key shown in the dashboard, not your login password. Then follow these steps.
- Install FoxyProxy Standard from the Chrome Web Store or Firefox Add-ons, then click its toolbar icon and choose Options.
- Open the Proxies tab and click Add to create a new profile.
- Give it a Title such as ProxyOmega US so you can recognise it in the menu.
- Set Proxy Type to HTTP for the simplest setup, or SOCKS5 if you need it (see the next section).
- In Hostname / IP enter the endpoint for your plan, for example residential.proxyomega.com for Budget Unlimited.
- In Port enter a port in your plan's range, for example 10000 (Budget Unlimited uses 10000-10199).
- Enter your Username, appending any targeting parameters dash-separated, for example youruser-country-us.
- Enter your Password, which is the API key from your dashboard.
- If you chose SOCKS5, tick Proxy DNS (send DNS through the proxy) so lookups do not leak.
- Click Save, then open the toolbar menu and select the profile to route traffic through it. Verify at a site like ipinfo.io that the IP has changed.
FoxyProxy
Choosing HTTP vs SOCKS5 and a plan
Every ProxyOmega port serves HTTP, HTTPS, and SOCKS5 on the same port, so you never change the port number when you switch protocol; you only change the Proxy Type field in FoxyProxy. For most browser work, HTTP is the path of least resistance. On Chrome specifically, the browser's proxy API does not reliably forward SOCKS5 username and password credentials, so if you are on Chrome and using authenticated access, choose HTTP or authenticate by IP whitelist instead. Firefox handles SOCKS5 authentication cleanly, and there SOCKS5 with Proxy DNS enabled is a good default when you want DNS resolution to happen at the exit.
Picking a plan is about the target, not the protocol. Match the workload to the product below.
| Workload | Plan | Why |
|---|---|---|
| General browsing and rotating IPs | Budget Unlimited | Fresh residential IP per port; add -country-us to target a country |
| High-throughput browser sessions | Premium Unlimited | Higher-speed residential on premium.proxyomega.com:8000 |
| City, state, or ASN precision, pay per GB | Platinum | Fine-grained targeting on platinum.proxyomega.com:20228 |
| Mobile-only sites or app views | Mobile | Real 4G/5G carrier IPs on mobile.proxyomega.com:20229 |
| A fixed IP for logins or allowlists | Static ISP | One stable US IP (Dallas) on isp.proxyomega.com, ports 30000-30099 |
FoxyProxy
Troubleshooting
Most FoxyProxy issues come down to credentials, the username suffix, or which IP you are connecting from. Work through the cards below before assuming the proxy itself is down.
Connection refused / 407
A 407 means authentication failed. Confirm the password field holds your dashboard API key, not your login password, and that the username's targeting parameters are valid. A malformed suffix such as an unsupported country code returns 407 as well. If you use IP whitelisting instead of a password, remember that once any IP is whitelisted only those IPs may connect, so a connection from an address that is not on the list is refused.
IP hasn't changed
Make sure the profile is actually selected in the toolbar menu, not just saved. If you set URL patterns, confirm the site you are testing matches one. Reload the page after switching, and check ipinfo.io rather than a cached result.
DNS or WebRTC leaks
On SOCKS5, tick Proxy DNS so lookups travel through the proxy. WebRTC can still reveal your real IP; disable it in the browser or use an extension if leak-tight routing matters for your task.
FAQ
Frequently asked questions
Does FoxyProxy support SOCKS5 with ProxyOmega?
Yes. Set Proxy Type to SOCKS5 and enter the same host, port, username, and password. On Chrome, note that the browser may not forward SOCKS5 credentials reliably, so HTTP is the safer choice there; Firefox handles SOCKS5 authentication without issue.
What do I put in the username and password fields?
The username is your ProxyOmega account username plus any dash-separated targeting parameters, for example youruser-country-de. The password is the API key shown in your dashboard, not your website login password.
How do I target a specific country?
Append -country- followed by the two-letter code to your username, such as youruser-country-gb. For a sticky IP, add -session- with an ID and -ttl- with a duration in minutes, for example youruser-session-abc123-ttl-10.
Which port should I use?
Use a port in your plan's range: Budget Unlimited is 10000-10199, Premium Unlimited is 8000, Static ISP is 30000-30099. Each port serves HTTP, HTTPS, and SOCKS5, so you never need a separate SOCKS port.
Can I route only certain sites through the proxy?
Yes. In FoxyProxy Standard, add URL patterns to a profile so matching domains use the proxy while everything else uses your direct connection. This is ideal for verifying one site or managing specific accounts.
Why does one site work and another shows my real IP?
Check whether the working site matches a URL pattern and the other does not. If you are in the mode that uses one proxy for all URLs, make sure that profile is selected in the toolbar rather than the Disabled or Direct option.
Route your browser through real residential IPs Start routing today.
Add a ProxyOmega endpoint to FoxyProxy in under two minutes.
ProxyOmega