Nginx Proxy Manager 2.17.0 shipped on November 12, 2026, with rate limiting on its login endpoints and a fix that blocks a remote code execution path. That makes this a good week to check which version you’re running. Most people searching “proxy manager” want this free tool for putting self-hosted apps online with HTTPS, so most of this guide covers it: install, security, troubleshooting and alternatives. Shorter sections cover browser proxy switchers and paid scraping proxy managers.
Key takeaways
- Nginx Proxy Manager (NPM) is the easiest way to put Plex, Jellyfin or Home Assistant online with free SSL.
- If you run NPM 2.9.14 to 2.15.1, update now. CVE-2026-40519 lets a logged-in attacker run commands on the server.
- Forward only ports 80 and 443 on your router. Port 81 is the admin panel and stays on your LAN.
- There’s no separate NPM download. You pull the jc21/nginx-proxy-manager Docker image.
- SwitchyOmega no longer works in Chrome. ZeroOmega, FoxyProxy and Proxy Switcher and Manager are the Manifest V3 options.
Fact-checked
We checked these key facts against the sources named, on November 16, 2026:
- Version 2.17.0, released November 12, 2026 (source: github.com)
- Map NPM to other host ports, for example 8080:80 and 8443:443 (source: nginxproxymanager.com)
- Then forward the router’s external 80 to 8080 and 443 to 8443 (source: nginxproxymanager.com)
- Version 2.16 is already outside the CVE-2026-40519 affected range (source: tenable.com)
- If your ISP blocks port 80, the DNS challenge is the only reliable route (source: nginxproxymanager.com)
Which proxy manager do you actually need?
“Proxy manager” can mean three different kinds of software, and they barely overlap. Pick yours by the job you need done.
- You want to reach Plex, Home Assistant or Jellyfin from outside your home over HTTPS. You need Nginx Proxy Manager. That’s most of this page.
- You want to switch proxies inside your browser. You need an extension such as ZeroOmega. Jump to the browser section.
- You run a scraping or data project on paid proxies. You need a provider such as Bright Data, Oxylabs, Decodo or IPRoyal, and possibly Bright Data Proxy Manager to run them on your own machine.
- You just need to find or turn off a proxy on your PC or phone. The device settings table near the end covers every major OS.
Reverse proxy vs forward proxy in plain English
A reverse proxy sits in front of your servers and handles traffic coming in from the internet. A forward proxy sits in front of you and sends your outgoing traffic out through another IP address.

Nginx Proxy Manager is a reverse proxy. Someone visits jellyfin.yourdomain.com, and NPM receives the request, handles the certificate and passes it to the right machine on your network.
Browser switchers and scraping proxies are forward proxies. Your request leaves through a different IP, so the target site sees that IP and not yours.
The tools at a glance
Here are the main tools in each category: what they do, who they suit and where you manage them.
| Tool | Type | Who it’s for | Where it runs | Cost | Admin address |
|---|---|---|---|---|---|
| Nginx Proxy Manager | Reverse proxy with free Let’s Encrypt SSL | Homelabs, small teams self-hosting | Docker, Proxmox LXC, NAS | Free, open source | Server IP, port 81 |
| ZeroOmega | Browser proxy switcher | Anyone changing browser proxies | Chrome, Edge | Free | Extension options page |
| Bright Data Proxy Manager | Local manager for Bright Data proxies | Scraping teams | Your PC or server | Free software, paid proxies | 127.0.0.1:22999 |
| Bright Data | Residential, ISP, mobile proxies | Large-scale data collection | Cloud | About $8/GB list | Web dashboard |
| Oxylabs | Residential proxies and scraper APIs | Mid to large scraping teams | Cloud | $6/GB down to $2.50/GB | Web dashboard |
| Decodo (formerly Smartproxy) | Residential proxies | Budget-conscious teams | Cloud | $3.75/GB down to $2/GB | Web dashboard |
| IPRoyal | Residential proxies, traffic doesn’t expire | Irregular or small projects | Cloud | $7.35/GB for 1 GB | Web dashboard |
How the recommendations were weighed
The self-hosting tools were judged on ease of setup, security track record and how actively they’re maintained, in that order. For scraping providers, published pricing at entry and volume levels counted most. Management tooling came next, then how well each fits a given team size. Vendors that hide all their prices rank lower, because you can’t budget without a sales call. Browser extensions had to work on current Chrome (Manifest V3) and come from a publisher you can identify.
What Nginx Proxy Manager does
Nginx Proxy Manager is a free web interface for Nginx. It sends traffic to your self-hosted services and gets free, auto-renewing HTTPS certificates without you writing config files. Jamie Curnow (GitHub handle jc21) created it. It ships as the Docker image jc21/nginx-proxy-manager, and the interface is built on the Tabler UI kit.

Think of NPM as a doorman for your home network. Every visitor arrives at one front door, ports 80 and 443. The doorman reads which name they asked for and walks them to the right apartment.
Did you know?
The project’s GitHub README says its goal was to make reverse proxying with SSL “so easy that a monkey could do it.”
Here’s what you get:
- Proxy hosts: map a domain such as ha.example.com to an internal address such as 192.168.1.20:8123.
- Redirection hosts: send one domain to another.
- Streams: forward raw TCP and UDP ports, which some game servers need.
- 404 hosts: catch requests for domains you don’t serve.
- Free SSL: Let’s Encrypt certificates through Certbot, renewed automatically.
- Access lists: HTTP basic auth and IP allow or deny rules. Since 2.16 these can also apply per path.
- Multiple users: separate accounts with permissions, plus an audit log of changes.
- Log viewer: since 2.16, you can read logs in the web UI without opening a shell.
NPM isn’t for everyone. If you manage infrastructure as code, a GUI that stores settings in a database is awkward to track in Git. And if you run dozens of containers that change often, Traefik’s automatic discovery saves time.
What you need before you start
You need three things:
- A domain or free subdomain. A domain from any registrar works. So does a free DuckDNS subdomain.
- Router access, so you can forward ports 80 and 443.
- A machine running Docker. A mini PC, a Raspberry Pi 4 or 5, a NAS or a Proxmox VE host all work.
Supported hardware and the armv7 cutoff
NPM 2.14 and later run on amd64 and arm64 only. Node.js dropped 32-bit ARM (armhf) support, so the project followed. The 2.14.0 release came out on February 17, 2026.
If you have an older armv7 board, such as a Raspberry Pi 2 or a 32-bit OS on a Pi 3, you can only use the 2.13.7 tag. That version misses every later security fix, including the CVE-2026-40519 patch. Moving to a 64-bit OS on supported hardware is the better long-term fix.
Install Nginx Proxy Manager with Docker in 10 minutes
The quickest route is a Docker Compose file with three ports and two folders. There’s no separate installer or download for NPM: Docker pulls the jc21/nginx-proxy-manager image from Docker Hub the first time you start it. The steps below use Docker Compose v2 (the docker compose command).
Before you start
If anything else on the machine already uses ports 80 or 443, such as another web server or a NAS interface, NPM won’t start. Free those ports first or map NPM to different ones.
Create a folder named npm. Inside it, save this as docker-compose.yml:
services:
app:
# 2.17.0 is the current release (November 12, 2026).
# Use a newer 2.17.x patch tag if the releases page lists one.
image: 'jc21/nginx-proxy-manager:2.17.0'
restart: unless-stopped
ports:
- '80:80'
- '443:443'
- '192.168.1.50:81:81'
environment:
TZ: 'America/New_York'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
Install steps
- Replace 192.168.1.50 with your server’s LAN IP address.
- On the GitHub releases page, check for a 2.17.x patch newer than 2.17.0.
- Run docker compose up -d inside the npm folder.
- Run docker compose ps and confirm the container shows “running”.
- If it doesn’t, run docker compose logs -f app and read the errors.
If the logs show nginx failing to start with an unknown “forward_host” variable, you’ve hit the startup bug reported on November 12 in GitHub issue #6043 against 2.17.0. Change the tag to the latest 2.16.x, recreate the container and watch the releases page for a fixed 2.17 patch. Version 2.16 is already outside the CVE-2026-40519 affected range.
docker-compose.yml explained line by line
Each line has one job:
- image: the official image with a fixed version number. A fixed tag means an update only happens when you choose it. Avoid
lateston a server you rely on. - restart: unless-stopped: brings NPM back after a reboot.
- ’80:80′ and ‘443:443’: the public ports for HTTP and HTTPS traffic.
- ‘192.168.1.50:81:81’: the admin panel, reachable only on your LAN IP. The official example uses plain
'81:81', which listens on every network interface. - ./data:/data: the database, proxy host settings and logs.
- ./letsencrypt:/etc/letsencrypt: your certificates and private keys.
| Port | Purpose | Forward on router? |
|---|---|---|
| 80 | HTTP traffic and Let’s Encrypt HTTP challenge | Yes |
| 443 | HTTPS traffic to your services | Yes |
| 81 | Nginx Proxy Manager admin panel | Never. Use your LAN, a VPN such as Tailscale or WireGuard, or a proxy host with an access list |
First login on port 81
Open http://192.168.1.50:81 in a browser on your LAN. According to NPM’s official setup docs, the first run generates JWT keys, sets up the database and then creates the admin account.
On current versions, a setup screen asks you to create the first user. The advanced config docs also describe environment variables (INITIAL_ADMIN_EMAIL and INITIAL_ADMIN_PASSWORD) that create that user at startup and skip the screen. That’s handy if you rebuild NPM from a script.
Older versions used the default login [email protected] with the password changeme, as the project’s earlier setup docs stated. If you install an old tag, you’ll be asked to change both right away. Do it before anything else.
Turn on two-factor authentication
Version 2.13.6 added built-in TOTP two-factor authentication. Open your user menu in the top-right corner of the admin panel, find the two-factor option, and scan the QR code with an authenticator app such as Microsoft Authenticator, Google Authenticator or Aegis.
Turn it on for every account. A stolen password should not be enough to get in, and since 2.17.0 the login endpoints are rate limited too, which slows down password guessing.
Other ways to install: Proxmox LXC, Synology, Unraid
NPM runs well on Proxmox VE, Synology DSM, Unraid and TrueNAS. Each platform has one catch worth knowing before you start.
| Platform | Install route | The catch | Fix |
|---|---|---|---|
| Proxmox VE 8.4 to 9.2 | Community Scripts LXC installer | Script runs as root on the hypervisor | Read the script before running it |
| Proxmox VE (Docker in LXC) | Docker inside an LXC container | Docker won’t start | Enable nesting in the container Options |
| Synology DSM 7.2+ | Container Manager | DSM already uses 80 and 443 | Remap ports or use macvlan |
| Unraid | Community Applications store | Unraid web UI may use 80 or 443 | Change the template’s ports |
| TrueNAS SCALE | Apps catalog | Data on non-persistent storage | Point paths at a persistent dataset |
Proxmox VE LXC
The Proxmox VE Community Scripts project has a one-line installer that builds a dedicated LXC container for NPM. VirtualizationHowto reported in October 2026 that the scripts support Proxmox VE 8.4, 9.0, 9.1 and 9.2.
The scripts run as root on your hypervisor, so download the script and read it before you run it. If you’d rather run the Docker image inside an LXC, enable the nesting feature in the container’s Options tab, or Docker won’t start.
To reach the Proxmox web UI itself through NPM, set the scheme to https, use port 8006, and turn on Websockets Support so the noVNC console works. Put an access list on that host. Your hypervisor’s login page shouldn’t be open to the whole internet.
Synology NAS
Synology works, but DSM already uses ports 80 and 443 for its own web services. In Container Manager on DSM 7.2 and later, you have two clean options:
- Map NPM to other host ports, for example 8080:80 and 8443:443. Then forward the router’s external 80 to 8080 and 443 to 8443.
- Give NPM its own LAN IP with a macvlan network, so it can use 80 and 443 directly.
Option 1 is easier and the one to pick if you’re new to Docker networking. Option 2 is tidier, but the NAS host can’t talk to a macvlan container without an extra bridge interface. That trips people up when NPM needs to proxy a service running on the NAS itself.
Unraid and TrueNAS
On Unraid, install NPM from the Community Applications store and change the template’s ports if the Unraid web UI already uses 80 or 443. TrueNAS SCALE lists it in its apps catalog. On both, make sure the /data and /etc/letsencrypt paths point to a persistent dataset, not temporary storage. Otherwise an app update can wipe your hosts and certificates.
Put your first service online with HTTPS
Publishing a service takes four steps: forward two ports, point a domain at your home IP, add a proxy host and request a certificate. Expect about 15 minutes the first time.
Port forwarding
On your router’s port-forwarding page, forward TCP 80 and TCP 443 to the NPM machine’s LAN IP. Nothing else.
Some ISPs block incoming port 80, and CGNAT (where you share a public IP with other customers) blocks all incoming traffic. If either applies to you, use the DNS challenge described below. With CGNAT you’ll also need a tunnel or VPN to reach your services at all.
Pointing your domain at home (DuckDNS, Cloudflare, Route 53)
Your domain needs an A record pointing at your public IP address. Pick one of these:
- DuckDNS: a free subdomain such as myhome.duckdns.org. A small updater keeps it current when your home IP changes.
- Cloudflare: free DNS hosting for your own domain, with an API that NPM’s DNS challenge supports.
- Amazon Route 53: paid DNS from AWS, useful if your company already runs on AWS.
Create the proxy host
With ports open and DNS pointing home, add the host in NPM:
- Go to Hosts > Proxy Hosts > Add Proxy Host.
- Enter the domain name, for example
jellyfin.example.com. - Set the scheme (usually
http), the forward hostname or IP (192.168.1.30) and the port (8096). - Turn on Block Common Exploits and, for apps that need it, Websockets Support.
- On the SSL tab, choose Request a new SSL Certificate. Turn on Force SSL and HTTP/2 Support, agree to the Let’s Encrypt terms and save.
- Test from outside your network (see the tip below).
Test from cellular, not Wi-Fi
Turn Wi-Fi off on your phone and open the domain over cellular data. Many home routers don’t support NAT loopback, so a test from inside your network can fail even when the setup works, or succeed while outside access is broken.
Wildcard certificates and DNS challenge
The DNS challenge proves you own the domain by creating a TXT record through your DNS provider’s API. It doesn’t need port 80 at all. It’s also the only way to get a wildcard certificate such as *.example.com, which covers every subdomain at once.
On the SSL tab, turn on Use a DNS Challenge, pick your provider (Cloudflare, Route 53, DuckDNS and many more) and paste an API token. For Cloudflare, create a token limited to Zone:DNS:Edit for that single zone, so a leaked token can’t touch your other domains.
Is Nginx Proxy Manager safe? Security status in November 2026
Yes. NPM is safe if you run a current version (2.16 or later, ideally 2.17.0), keep port 81 off the internet and turn on 2FA. Older versions have serious published flaws, so the version you run matters more than anything else.
Known vulnerabilities and fixed versions
These are the published CVEs worth knowing in November 2026.
| CVE | Affected versions | What it allows | Severity | Fix status |
|---|---|---|---|---|
| CVE-2026-40519 | 2.9.14 to 2.15.1 (per NVD) | Authenticated OS command injection, remote code execution | 7.5 High (ZeroPath), 7.7 (vuln.today) | Fixed in commit a5db5ed. Run 2.16 or later |
| CVE-2026-50892 | 2.14.0 (the only version listed) | Users with certificate read access can download TLS private keys | 6.5 Medium (Strix) | No fixed version named in the published record |
| CVE-2025-50579 | 2.12.3 | CORS misconfiguration (Origin header not validated) exposes JWT tokens to other domains | 5.3 Medium (vuln.today) | Not present in current releases |
CVE-2026-40519 matters most. NIST’s National Vulnerability Database (NVD) places the flaw in the backend setup code, and ZeroPath’s write-up describes it as an authenticated remote code execution. An attacker needs a login first, which is exactly why a weak password plus an exposed port 81 is so dangerous. The 2.17.0 release notes also list a fix to escape ordering “to block RCE”, a further hardening step on top of the 2.16 fix.
CVE-2026-50892 is a broken access control flaw in the certificate download endpoint. The CVE record names only 2.14.0 as affected and doesn’t name a fixed version. A published reference for the CVE describes a user with read-only certificate access getting a ZIP file that includes the private key. Anyone holding that key could impersonate your site’s TLS endpoint. If you’re the only user, the risk is low. If you’ve handed accounts to colleagues, run the newest release, give certificate permissions only to people who need them, and rotate any certificate you think was exposed.
Nginx Proxy Manager versions and what changed
Here’s how the recent releases compare, from the official release notes and release coverage.
| Version | Released | Key changes | Notes |
|---|---|---|---|
| 2.13.6 | 2026, before 2.14 | Built-in TOTP two-factor authentication | First version with 2FA |
| 2.13.7 | 2026, before 2.14 | Maintenance | Last tag for armv7 |
| 2.14.0 | February 17, 2026 | armv7 dropped | Listed for CVE-2026-50892 |
| 2.15 | June 2026 | Debian 13 “Trixie” base image, security fixes | 2.15.1 and earlier hit by CVE-2026-40519 |
| 2.16 | September 2026 | Built-in log viewer, per-path access lists, updated Certbot support, security fixes | DNS plugins may need dependency tweaks |
| 2.17.0 | November 12, 2026 | Rate limiting on auth endpoints, escape-ordering fix to block RCE, reuseport for performance, denied requests return 403 instead of 404 | Breaking changes for EdgeDNS, Beget and Infomaniak DNS plugins. Startup bug in issue #6043 |
Which version to run now: 2.17.0, or a newer 2.17.x patch if the releases page lists one. If you use the EdgeDNS, Beget or Infomaniak DNS plugin, or you hit the “forward_host” startup error, stay on the latest 2.16.x for now. Either way, move off anything at 2.15.1 or below.
Hardening checklist
Go through this list once and your install is safer than most:
- Never forward port 81 on your router. Bind it to your LAN IP, as in the compose file above, and reach it remotely over Tailscale or WireGuard.
- Turn on 2FA for every user.
- Give each person their own account with only the permissions they need. Hold back certificate access on multi-user installs because of CVE-2026-50892.
- Put an access list on sensitive services such as Proxmox, router admin pages and NAS panels. An IP allow list for your VPN range works well.
- Keep Block Common Exploits on for every host.
- Update within days of a security release.
- Back up
./dataand./letsencrypton a schedule, not only before upgrades.
How to update without breaking things
Updating means changing one tag and recreating the container. A few minutes of preparation means you can always roll back.
Back up before every upgrade
Copy the ./data and ./letsencrypt folders after docker compose down and before you change the tag. They hold every host, user and certificate, so with a copy you can roll back in minutes.
- Read the release notes for every version between yours and the target.
- Stop the stack with
docker compose downand copy both folders somewhere safe. - Change the image tag in
docker-compose.yml. - Run
docker compose pull, thendocker compose up -d. - If you use a DNS challenge, renew one certificate by hand to confirm the plugin still works. The 2.17.0 release notes warn that DNS plugins may need dependency tweaks.
If something breaks, put the old tag back, restore the folders and start again.
Fix the most common Nginx Proxy Manager problems
Most NPM problems come from four things: port 80 not reachable from outside, a wrong forward address, Cloudflare settings fighting your certificate, or a plugin change after an upgrade.
| Symptom | Likely cause | Fix |
|---|---|---|
| “Internal Error” requesting SSL | Let’s Encrypt can’t reach port 80 | Check port forwarding, test from cellular, or use DNS challenge |
| 502 Bad Gateway | Wrong IP, port or scheme | Use the LAN IP, not localhost, and the right http or https scheme |
| Cloudflare 525 | SSL handshake failed between Cloudflare and NPM | Get a valid cert on NPM, set Cloudflare SSL to Full (strict) |
| Can’t reach admin panel | Port 81 bound to a different IP, or a firewall | Check the ports line and the host firewall |
| Certificate not renewing | Port 80 closed later, or DNS token expired | Reopen 80 or refresh the API token |
| nginx won’t start on 2.17.0, unknown “forward_host” variable | Bug reported in GitHub issue #6043 | Roll back to your 2.16.x tag until a patch ships |
| DNS plugin errors after upgrading | Plugin dependency changes (EdgeDNS, Beget, Infomaniak flagged in 2.17.0) | Check GitHub issues, or roll back to your pinned tag |
| 403 where you used to see 404 | 2.17.0 now returns 403 for denied requests | Expected behavior; check your access list rules |
SSL “Internal Error”
The question comes up constantly in r/selfhosted: “Internal Error when requesting SSL certificate in NPM, what am I doing wrong?” Usually Let’s Encrypt’s servers can’t reach your port 80.
Work through it in order. First, confirm the domain’s A record already points at your public IP. Newly created records can take a few minutes to spread, and requesting too early fails. Second, test port 80 from outside your network. Third, if you use Cloudflare, turn off the orange-cloud proxy while requesting, or switch to the Cloudflare DNS challenge. If your ISP blocks port 80, the DNS challenge is the only reliable route.
502 Bad Gateway
A 502 error means NPM can’t reach the service behind it. Inside a container, localhost points at NPM itself, not at your server, so use the server’s LAN IP. Services that only speak HTTPS, such as Proxmox on port 8006, need the scheme set to https.
Home Assistant users often see an “SSL protocol error” or a 400 error after switching to NPM, because Home Assistant rejects proxied requests until you trust the proxy. Add use_x_forwarded_for: true and a trusted_proxies entry with NPM’s IP under http: in configuration.yaml. Then restart Home Assistant and turn on Websockets Support in NPM.
Locked out of the admin panel
First, check you’re using the right IP and port 81, and that a firewall isn’t blocking it. NPM has no reset-password button. The community-documented fix is editing the user table in data/database.sqlite with the sqlite3 tool. Stop the container and back up the whole data folder before you touch it. If you’re not comfortable editing a database by hand, restoring your last backup of ./data is the safer route.
Nginx Proxy Manager vs Caddy vs Traefik
Pick NPM if you want a web interface. Pick Caddy if you’re comfortable with a short config file. Pick Traefik if you run lots of Docker containers and want routing set by labels on each container. Plain Nginx is the engine underneath NPM, so it’s a web server you configure by hand rather than a manager.
| Nginx Proxy Manager | Caddy | Traefik | |
|---|---|---|---|
| How you configure it | Web GUI | Caddyfile (a few lines per site) | Docker labels or YAML |
| Automatic HTTPS | Yes, per host in the UI | Yes, on by default | Yes, after resolver setup |
| Learning curve | Lowest | Low | Highest |
| Fits version control (Git) | Poor | Excellent | Excellent |
| Best for | Beginners, small homelabs | Tidy setups, developers | Large, changing container fleets |
Did you know?
In an August 2025 r/selfhosted poll of about 2,500 votes, Nginx Proxy Manager got 657 votes, narrowly ahead of plain Nginx at 634. Caddy had 515 and Traefik 498.
Is Traefik worth the extra setup over NPM? Only if your containers change often enough that clicking through a UI becomes a chore. Caddy’s reputation for being “magic” is fair: two lines give you a working HTTPS site. The strongest case against NPM is that its settings live in a database, which makes them harder to review, copy or rebuild than a text file. That’s why some people start on NPM and move to Caddy once they have more than a dozen hosts.
Browser proxy managers for Chrome, Edge and Firefox
A browser proxy switcher sends your browser’s traffic through a proxy you choose, with rules for which sites use which proxy. In current Chrome and Edge, the working options are Manifest V3 extensions such as ZeroOmega, FoxyProxy and Proxy Switcher and Manager. The classic SwitchyOmega no longer runs.

After Manifest V2: what still works
Google phased out Manifest V2, the older extension platform. Chrome 138 was the last version that could run MV2 extensions. As of August 31, 2026, Google had removed every remaining MV2 extension from the Chrome Web Store, according to its Chrome for Developers deprecation timeline.
SwitchyOmega was an MV2 extension, so it’s gone. ZeroOmega is a community fork rebuilt for Manifest V3, with the same profiles and auto-switch rules, and it imports SwitchyOmega backups. Firefox still supports MV2 add-ons and has proxy settings built in under Settings > General > Network Settings > Settings.
Proxy switcher extensions compared
These three switchers are on the Chrome Web Store and built for Manifest V3. Store details change, so check the listing’s publisher and last update before installing.
| Extension | Publisher | Works in current Chrome | Rule-based switching | Best for |
|---|---|---|---|---|
| ZeroOmega | Community fork of SwitchyOmega | Yes, MV3 | Auto Switch profiles with host and URL rules | Former SwitchyOmega users |
| FoxyProxy | FoxyProxy, long-running Firefox add-on team | Yes, MV3 version | URL pattern rules | Using one tool in Chrome and Firefox |
| Proxy Switcher and Manager | yokris.dev, open source | Yes, side panel based | Inline PAC scripts | A lighter switcher, about 100,000 users per ExtScope |
The Chrome Web Store has many look-alike names (“Proxy Switcher”, “Proxy manager and switcher”, “Proxy Switcher And Manage”) from different publishers, with far fewer users. Match the developer name, not just the title.
Set up a proxy profile and auto-switch rule in ZeroOmega
ZeroOmega’s main strength is sending only certain sites through a proxy and everything else direct. Here’s how to set that up:
- Install ZeroOmega from the Chrome Web Store, then right-click its toolbar icon and choose Options.
- Click New profile, name it (for example “work-proxy”), choose Proxy Profile and click Create.
- Pick the protocol (HTTP, HTTPS or SOCKS5), enter the server and port, add any addresses to bypass, and click Apply changes.
- Open the auto switch profile. Add a condition such as host wildcard
*.example.comthat points to “work-proxy”, set the default to Direct, and click Apply changes. - Click the toolbar icon and select auto switch. Visit a matching site and an IP-check page to confirm only the matched site goes through the proxy.
Choosing a safe proxy switcher
A proxy extension can see and redirect every site you visit, so treat it like any app that handles passwords.
- Check the developer, user count and recent reviews on the store listing.
- Avoid listings from unknown publishers that reuse the SwitchyOmega name or logo. Copycats appeared after the original disappeared.
- Install only from the Chrome Web Store, Edge Add-ons or Mozilla’s add-on site.
- Remove switchers you no longer use.
If your browser starts sending you to odd pages after you install an extension, remove it and work through a Chrome malware removal guide before anything else.
Where to find (or turn off) proxy settings on your device
Each operating system keeps its proxy settings in one menu, and Chrome and Edge use the system proxy rather than their own. A proxy you never set up is a warning sign.
| Device | Menu path |
|---|---|
| Windows 11 | Settings > Network & internet > Proxy |
| Windows 10 | Settings > Network & Internet > Proxy |
| macOS Ventura and later | System Settings > Network > Wi-Fi or Ethernet > Details > Proxies |
| iPhone | Settings > Wi-Fi > (i) next to your network > Configure Proxy |
| Android | Settings > Network & internet > Internet > gear icon > edit > Advanced options > Proxy |
| Chrome | Settings > System > Open your computer’s proxy settings |
| Edge | Settings > System and performance > Open your computer’s proxy settings |
On Windows, turn off Use a proxy server under Manual proxy setup unless your workplace set it, and check Use setup script too. Samsung and other Android makers word their menus slightly differently.
Adware and some info-stealers set a system proxy or setup script so they can route your traffic through their servers. If you find one you didn’t add, turn it off, then run a full scan with Microsoft Defender or your security app.
Scraping proxy providers for businesses
For scraping at scale, you rent large pools of IP addresses and manage rotation, location targeting and sessions through each provider’s dashboard or API. Bright Data has the deepest tooling, Oxylabs gets cheapest at steady volume, Decodo has the lowest entry price, and IPRoyal suits bursty use because its traffic doesn’t expire.
Price and tooling
| Provider | Entry residential price | Volume price | Manager tooling | Best for | Watch out for |
|---|---|---|---|---|---|
| Bright Data | About $8/GB pay as you go | About $5/GB on $1,999/month plan | Dashboard, API, open-source Proxy Manager | Large teams, complex targeting | Highest list price |
| Oxylabs | $30/month for 5 GB ($6/GB) | $2,500 for 1,000 GB ($2.50/GB) | Dashboard, API, scraper APIs | Mid to large steady workloads | Subscription-first |
| Decodo | $11.25 for 3 GB ($3.75/GB) | $2/GB on 1,000 GB plan | Dashboard, API, browser extension | Small teams on a budget | $2/GB only at top tier |
| IPRoyal | $7.35/GB for 1 GB | $1.75/GB from 10 TB | Dashboard, API | Occasional or bursty projects | High small-purchase rate |
| Zyte API | Usage-based per request | Volume discounts on commitments | API with Proxy Mode | Teams who want unblocking handled | Cost varies by target site |
All prices are for residential proxies as published or reported in 2026. Promotions change often, so check the provider’s checkout page before you sign up.
Network size, coverage and trials
The figures below are advertised by the vendor or reported by the comparison site Proxyway, checked November 2026. They aren’t independently verified.
| Provider | Advertised residential pool | Countries | Trial or low-commitment start |
|---|---|---|---|
| Bright Data | 400M+ IPs | 195 | Free trial, no credit card required (per Bright Data) |
| Oxylabs | 175M IPs | 195+ | Trial on request |
| Decodo | 115M IPs | 195 | Short trial reported; confirm terms at signup |
| IPRoyal | 32M IPs | 195+ | 1 GB pay-as-you-go purchase, traffic never expires |
Treat pool size as a marketing number. Proxyway’s own testing found 3.24 million unique IPs in its Oxylabs residential test, far below the advertised pool. What counts for your project is success rate on your target sites and how many IPs you get in the countries you need. A short paid test tells you more than the headline figure.
Bright Data
Bright Data is the largest and most full-featured provider, built for companies that need residential, ISP, datacenter and mobile IPs in one account. Residential traffic lists at about $8/GB pay as you go, and monthly plans at $499, $999 and $1,999 bring that down to roughly $7, $6 and $5 per GB.

Its advantage is targeting and tooling. Bright Data says you can target by country, state, city, ZIP code, mobile carrier and ASN (the network an IP belongs to), and that city, state and ZIP targeting cost nothing extra. Add team accounts and the free Proxy Manager covered below. The drawback is cost: compared with Oxylabs, Bright Data charges more per GB at most tiers.
Oxylabs, Decodo and IPRoyal
Oxylabs suits teams with steady monthly volume. Published residential plans run $30 for 5 GB ($6/GB), $100 for 20 GB ($5/GB), $500 for 125 GB ($4/GB) and $2,500 for 1,000 GB ($2.50/GB). Self-serve plans are monthly subscriptions, so it’s a poor fit if you only scrape occasionally. It also sells scraper APIs if you’d rather pay per result than per GB.


Decodo is Smartproxy under a new name. The rebrand took effect on April 22, 2025, and existing accounts, endpoints and billing carried over. Residential plans start at $11.25 for 3 GB ($3.75/GB) and drop to $2.75/GB at 100 GB. The $2/GB rate applies only to the 1,000 GB plan, and pay as you go runs about $4/GB. For small teams it’s the cheapest way into residential proxies among the well-known names.
IPRoyal suits projects that run in bursts, because purchased residential traffic doesn’t expire. Pay as you go starts at $7.35/GB for 1 GB and falls to $5.51/GB at 10 GB. The headline $1.75/GB applies only from 10 TB, and subscriptions run about 5% cheaper. If you scrape every month, Decodo or Oxylabs will cost less. If you scrape twice a year, IPRoyal can come out ahead.
Zyte API (replacing Smart Proxy Manager)
Zyte’s Smart Proxy Manager, formerly called Crawlera, no longer accepts sign-ups. Zyte’s documentation says Zyte API replaces it, and existing traffic moved to Zyte API’s Proxy Mode with the same API keys still working.

Pricing is per request and depends on the target site and whether the request needs a full browser. Zyte suits teams who’d rather hand off ban handling and browser rendering than manage IP rotation themselves. The catch is that you can’t predict costs until you test your target sites.
Bright Data Proxy Manager: what it is and how to install it
Bright Data Proxy Manager is free, open-source software that runs on your own machine and manages Bright Data proxies through local ports. You configure rotation and rules once in its interface, then point your scrapers at a local port. It’s only useful if you pay for Bright Data proxies, and it has nothing to do with Nginx Proxy Manager.
It used to be called Luminati Proxy Manager, from before Luminati renamed itself Bright Data. The GitHub repository is still named luminati-io/luminati-proxy, which is why the old name still turns up in searches.
Bright Data’s stated features include rotation rules, retries and per-port targeting, full request logs, waterfall rotation (falling back from cheaper to pricier proxy types when a request fails) and regex rules that cut traffic by blocking or rerouting unneeded requests such as images. The admin interface runs at 127.0.0.1:22999.
According to Bright Data’s product page, the minimum requirements are 1 CPU, 2 GB of RAM and 3 GB of disk space, and Bright Data recommends 2 CPUs and 4 GB of RAM. Releases come often, and the page listed version 1.684.881 in November 2026.
Download and run it
Bright Data publishes four official install methods. Get builds only from these sources, never from mirror or download sites.
| Method | Platform | How |
|---|---|---|
| Installer (.exe) | Windows | Download the latest setup file from the luminati-io/luminati-proxy GitHub releases page |
| Setup script | Mac, Linux | Run Bright Data’s official setup script, shown on its Proxy Manager product page and docs |
| npm package | Mac, Linux, Windows with Node.js | sudo npm install -g @luminati-io/luminati-proxy |
| Docker image | Any Docker host | docker pull luminati/luminati-proxy |
For Docker, Bright Data’s docs publish the admin and proxy ports to localhost and keep settings in a named volume mounted at /root:
docker volume create lpm-vol
docker run -d --name proxy-manager \
-p 127.0.0.1:22999:22999 -p 127.0.0.1:22998:22998 -p 127.0.0.1:24000:24000 \
-v lpm-vol:/root luminati/luminati-proxy proxy-manager
Then start it:
- Windows: search the Start menu for Proxy Manager and open it. Mac or Linux: run
proxy-managerin Terminal (older installs used theluminaticommand). - Open
http://127.0.0.1:22999in your browser. - Sign in with your Bright Data account and create your first proxy port.
Keep ports 22999 and 24000 bound to 127.0.0.1, as above. Anyone who can reach them can spend your proxy traffic.
Is using a proxy legal?
In the US, using a proxy is legal. What you do through it can still break the law or a site’s terms. Proxies are everyday business tools for security testing, ad verification, price monitoring and privacy.
They don’t make illegal activity legal. Fraud, breaking into accounts and getting around technical access controls stay illegal whatever IP address you use.
Scraping is a gray area. In hiQ Labs v. LinkedIn, the Ninth Circuit held that scraping publicly available pages likely doesn’t violate the federal Computer Fraud and Abuse Act. But hiQ later lost on breach of LinkedIn’s user agreement, and breaking a site’s terms can also get your accounts banned. This is general information, not legal advice. For a commercial scraping project, talk to a lawyer.
FAQ
What is a proxy manager?
A proxy manager is software that controls how traffic passes through one or more proxies. Nginx Proxy Manager handles incoming traffic to your self-hosted services. Browser switchers and Bright Data Proxy Manager handle outgoing traffic through other IP addresses.

Where do I download Nginx Proxy Manager?
There’s no separate download. NPM is distributed as the jc21/nginx-proxy-manager Docker image, and Docker pulls it when you run docker compose up -d. Release notes and source code are on the NginxProxyManager GitHub repository.
What is the latest version of Nginx Proxy Manager?
Version 2.17.0, released November 12, 2026. It adds rate limiting on authentication endpoints and an escape-ordering fix that blocks remote code execution. If you hit the reported “forward_host” startup bug or use an affected DNS plugin, stay on the latest 2.16.x until a patch ships.
Is Nginx Proxy Manager safe to use?
Yes, on a current version with port 81 kept off the internet and 2FA turned on. Versions 2.9.14 to 2.15.1 are affected by CVE-2026-40519, so update to 2.16 or later.
What is the default login for Nginx Proxy Manager?
Older versions used [email protected] with the password changeme. Current versions ask you to create the admin account on first launch, or you can set it with the INITIAL_ADMIN_EMAIL and INITIAL_ADMIN_PASSWORD environment variables.
What port does Nginx Proxy Manager use?
Port 81 serves the admin panel. Ports 80 and 443 carry the traffic it passes on to your services. Forward only 80 and 443 on your router, and never forward 81. Reach the admin panel on your LAN or through a VPN such as Tailscale or WireGuard.
Can I run Nginx Proxy Manager on Synology?
Yes, through Container Manager on DSM 7.2 and later. DSM already uses ports 80 and 443, so map NPM to other ports such as 8080 and 8443, or give it its own IP with a macvlan network.
How do I install Nginx Proxy Manager in a Proxmox LXC?
Use the Proxmox VE Community Scripts installer, which builds a dedicated LXC and supports Proxmox VE 8.4 to 9.2. Read the script first, because it runs as root. If you run Docker inside an LXC instead, enable nesting.
Does Nginx Proxy Manager work on a Raspberry Pi?
Yes on a Raspberry Pi 4 or 5 with a 64-bit OS. Versions 2.14 and later dropped armv7, so 32-bit systems are stuck on 2.13.7, which lacks recent security fixes.
Is Nginx Proxy Manager free?
Yes. It’s free and open source, and the Let’s Encrypt certificates it requests are free too. You only pay for a domain if you don’t use a free DuckDNS subdomain.
Why do I get a Cloudflare 525 error after switching to Nginx Proxy Manager?
Cloudflare couldn’t complete a secure connection to your server. Make sure NPM has a valid certificate for that domain and port 443 is forwarded, then set Cloudflare’s SSL/TLS mode to Full (strict).
Is SwitchyOmega still available for Chrome?
No. It was a Manifest V2 extension, and Google removed the remaining MV2 extensions from the Chrome Web Store in 2026. ZeroOmega is the MV3 fork with the same features and can import SwitchyOmega backups.
How do I download Bright Data Proxy Manager?
Use one of the four official routes: the Windows installer from the luminati-io/luminati-proxy GitHub releases page, Bright Data’s setup script for Mac and Linux, the npm package @luminati-io/luminati-proxy, or the Docker image luminati/luminati-proxy. Then open 127.0.0.1:22999 in your browser.
What happened to Luminati Proxy Manager?
It’s now Bright Data Proxy Manager, after Luminati renamed itself Bright Data. The software is still free and open source, and its code still lives in the luminati-io/luminati-proxy repository.
Your next step
If you self-host, open your NPM admin panel tonight and check the version number in the footer. At 2.15.1 or older, update before you add another service. Back up the two folders, set the image tag to 2.17.0 (or the latest 2.16.x if you use an affected DNS plugin), then check from your phone on cellular that port 81 doesn’t respond from outside. After that, everything you publish sits behind a patched, rate-limited front door.













