WebRTC Leak Protection for Mobile Proxies
WebRTC lets websites ask your browser for its IP addresses. If that request goes around the proxy, the site sees your real IP next to the proxy IP. Here is how XProxy and your browser keep WebRTC on the mobile IP.
You need: any plan. The box switch is on by default.
In short
A WebRTC request (STUN) that skips the proxy tells the site your home IP.
Each modem's proxy can only leave through that modem. Nothing slips out of the box's home internet.
Your antidetect browser decides what WebRTC answers. Set it to use the proxy IP.
What the box switch does
Disable WebRTC Leak (Force WebRTC use Dongle network) locks the traffic of every modem slot to its own modem. Each slot's proxy runs in its own network space with only one way out: its modem. If that modem drops, the traffic stops; it never falls back to the box's home internet or to another modem.
- It covers the HTTP, SOCKS5, VLESS and Shadowsocks ports of every modem, and the Selling Platform ports. Android phones and proxy-group ports are not part of it.
- It protects WebRTC, DNS and UDP that go through the proxy. It cannot change what your browser does on your own computer: that is the browser's WebRTC setting (step 2).
- TCP OS Spoofing needs it. With the switch off, Change answers that "Disable webRTC Leak" is required.
Set it up
Step 1 of 2
In Proxy Management, click Proxy Settings and open the Advanced tab. Scroll to Disable WebRTC Leak.
- Force WebRTC use Dongle network 1 must be on. It is on by default.
- Interfaces 2 lists the network ports the box itself may use besides the modems. Leave
eth0andtailscale0: they keep the dashboard and remote access working.
If you changed something, click Save & restart.
Test for a WebRTC leak
- Open the browser profile that uses the proxy.
- Open our WebRTC leak test, or browserleaks.com/webrtc for a second opinion.
- Look at Public IP Address. It must show only the modem's mobile IP, the same IP as What is my IP shows.
- Local IP Address should be empty or a random
.localname, never your computer's LAN address such as192.168.1.20.
You see your home IP in step 3? The browser's WebRTC mode is Real, or the browser is not using the proxy for this tab. Fix the profile (step 2), not the box.
Troubleshooting
| Symptom | Fix |
|---|---|
| BrowserLeaks shows your home IP | Set WebRTC in the browser profile to Replace / Altered / Based on IP. |
| TCP OS Spoofing says "Disable webRTC Leak" is required | Turn the box switch on (step 1). XProxy restarts for a few seconds. |
| The dashboard stops opening after a save | Keep eth0 in Interfaces. If the box uses another port for its home internet, add that port too. |
| A proxy stops working when its modem drops | That is the protection working: no fallback to another network. The proxy comes back when the modem is online again. |
FAQ
Should I ever turn it off?
Almost never. Off, a proxy could leave through the box's home internet while its modem reconnects, and TCP OS Spoofing stops working.
Do VPN users need the browser setting?
No. With WireGuard or OpenVPN the whole device, WebRTC included, goes through the modem, so WebRTC only sees the mobile IP.
What next?
Close the next common leak: DNS.

