WebRTC is leaking my real IP in Chrome while VPN is on

If Chrome shows an address in a WebRTC test while your VPN is on, first determine whether that address is actually your baseline public IP. Private 192.168.x.x, 10.x.x.x, local IPv6, and .local names are not the same as a public address. Run the WebRTC leak test and compare it with the public IP check.

Confirm the address before fixing it

Save the public IP before connecting the VPN. After connecting, note the new public IP and rerun the WebRTC test. A concern exists when a public WebRTC candidate matches the old baseline or otherwise differs from the current public VPN IP. Read how to read a WebRTC test result before treating a candidate as proof.

Chrome troubleshooting order

1. Reproduce the result after one clean VPN reconnect.
2. Test the same page in a second browser.
3. Check if the VPN is an extension-only setup or a full-device app.
4. Review any provider WebRTC/privacy settings and Chrome extensions.
5. Check split tunnelling and browser profile differences.
6. Retest; avoid disabling browser technology blindly if you need calls.

Extension or full VPN?

A Chrome extension may protect selected browser traffic while a full VPN app can cover a wider device path. Neither label proves a WebRTC result is safe or unsafe. Compare the actual public values and the provider’s documented coverage.

When switching is reasonable

If a public baseline IP remains reproducibly visible after the steps above and provider documentation offers no usable resolution, compare services with documented device-wide privacy controls. See best VPN for WebRTC leak protection. NordVPN’s current offer may be worth evaluating where its documented platform support fits; it is not a promise that Chrome permissions or every location signal will disappear.

Bottom line

Do not fix a private address as though it were your public IP. Verify the public comparison first, then make one browser or VPN change at a time.