Security boundaries / 2026-08-28
Panels shouldn't be exposed to the public internet: lock 3x-ui inside the internal network
Panel tools are the easiest entry points for scanners to find. Use WireGuard or FRP with an allowlist to take a 3x-ui panel off the public internet.
After installing a panel, the first thing is to change the port, the second is to add a path, and the third — which most people don't do — is to keep it off the public internet.
Why panels are dangerous
- Exposed login page = the attack surface begins
- Panels often have "command execution" capability; once you're in, it's equivalent to root
- Default passwords, weak passwords, and path guessing are all automated
Three ways to narrow exposure
| Method | Action | Applies to |
|---|---|---|
| Listen only on localhost | webListen: 127.0.0.1 | Have an SSH tunnel or reverse proxy |
| Bind to an internal NIC | Listen on the WireGuard address | Existing network setup |
| Firewall allowlist | Allow only fixed IPs | Fixed egress IP |
I most often use the first: the panel listens only on 127.0.0.1, and I open an SSH tunnel when needed:
ssh -L 8080:127.0.0.1:8080 user@host
Then access http://127.0.0.1:8080 from the local browser. The panel isn't on the public internet at all; scanners can't even see the login page.
If remote access is required
Connect to the internal network with WireGuard first, then access the panel's internal address. This way, even if the WireGuard port is exposed, the attacker only gets a UDP port that requires a key, not a login page.
A few related things
- Set a separate panel password; don't reuse passwords from other services
- Enable login failure lockout (built into 3x-ui, off by default)
- If the panel's "subscription" address is exposed externally, make sure it doesn't leak node information
- Regularly check the panel version; snapshot before upgrading
A counterintuitive conclusion
After locking the panel inside the internal network, you'll find yourself more willing to use it — because you're not afraid of scanning, and you don't have to watch login logs every day. If security measures make daily operations cumbersome, they will eventually be bypassed.
Why panels must be shut off
Panels such as BT Panel and 1Panel have three characteristics: fixed default ports, no rate limiting on the login page, and root once you get in. Scanners routinely probe 8888/8889; dozens of attempts per day in the logs are normal.
The point isn't whether the password is strong enough; it's that it should not be reachable from the public internet at all.
Three ways to narrow exposure
| Method | Approach | Applies to |
|---|---|---|
| Listen only on the internal network | Bind the panel to 127.0.0.1 or an internal IP | Have a fixed office network |
| Use a tunnel | WireGuard / SSH port forwarding | Mobile work |
| IP allowlist | Firewall allows only your own egress IP | Fixed egress IP |
The most robust option is the first plus the second: the panel listens only on 127.0.0.1, and you use SSH forwarding to get in when needed.
ssh -L 8888:127.0.0.1:8888 root@server
# Open http://127.0.0.1:8888 in a local browser
Verification required after changes
ss -lntp | grep 8888 # should be 127.0.0.1:8888, not 0.0.0.0:8888
nmap -p 8888 <public IP> # should be filtered/closed
Checking only the first item isn't enough: if there is another layer of NAT or a reverse proxy in front, ss shows an internal listener but the service is still reachable from the public internet.
A side effect
After shutting off public access, the panel's "scheduled tasks" and "SSL auto-renewal" still work (they use the loopback), but remote backup push may fail. Before changing it, confirm which tasks depend on public outbound access; don't shut off backups along with it.