Skip to content
XXD VPS Guide
中文
  1. How-to
  2. Checks
  3. Check for WebRTC leaks

Check for WebRTC leaks

5 minutesFor: Windows and Mac usersMain guide step 5: Check it works

How to test

  1. Open browserleaks.com/webrtc.
  2. “RTCPeerConnection” should show ✔ — WebRTC works normally.
  3. “Public IP Address” should be your server’s IP.
Example browserleaks WebRTC result
Two parts of browserleaks: RTCPeerConnection shows ✔, and Public IP Address is the server IP (replaced with an example here). Screenshot 2026-10; the interface may have changed since.

The “WebRTC UDP leak test” on ip.net.coffee/claude/ works too.

You see Meaning
✔ and the public IP is your server No leak, and WebRTC works
✔ but the public IP is Chinese A leak — most likely only System Proxy is on
✘, or no IP detected WebRTC is disabled or restricted — not fixed

A leak: turn on Tun Mode

Follow Turn on TUN mode, then fully quit the browser and test again.

WebRTC is disabled: restore it

Undo any earlier “anti-leak” extensions or settings:

  • Chrome / Edge: open chrome://extensions (Edge: edge://extensions) and remove extensions with WebRTC in the name; with uBlock Origin, untick “Prevent WebRTC from leaking local IP addresses” in its settings.
  • Firefox: open about:config, search media.peerconnection and click “Reset” on each bold (modified) entry.

Don't do this

Don’t “fix” leaks with extensions or settings that disable WebRTC. That breaks video meetings and voice calls on web pages.

The full troubleshooting guide an AI assistant can follow (with test commands and a fault table): Clash Verge WebRTC leak fix guide (in Chinese).

This setup is for you and your family only. Follow local laws and each site's and AI tool's terms of use. Open source (MIT) — code and feedback on GitHub.