This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Denc nañu waxtaan wii. Yónneel yeneen laaj soo soxlaa ndimbal.

Firefox leaks the true IP address when using a VPN.

  • 3 tontu
  • 1 am na jafe-jafe bii
  • 7 views
  • i mujjee tontu mooy philipp

Punta30
Punta30
more options

Because Firefox supports WebRTC a users true IP address is leaked when using a VPN. A site such as ipeak.net will verify this. A fix is to go to about:config and toggle 'media.peerconnection.enabled = false' . Is this the only fix available and will it have to be applied at each Firefox update? Will Firefox developers address the issue?

Because Firefox supports WebRTC a users true IP address is leaked when using a VPN. A site such as ipeak.net will verify this. A fix is to go to about:config and toggle 'media.peerconnection.enabled = false' . Is this the only fix available and will it have to be applied at each Firefox update? Will Firefox developers address the issue?

All Replies (3)

philipp
philipp
  • Moderator
more options

hi Punta30, you'll only have to change this preference once - updating firefox doesn't affect it. as it stands currently firefox developers will not address this issue, since it's behaving exactly like described in the webrtc API - any change would need to come from the ietf working group setting forward those standards...

Punta30
Punta30 Ki laajte
more options

Firefox implementation of WebRTC makes a joke of anonymity online for the unsuspecting or uninformed. Maybe this was the purpose of the implementation? For me Firefox is damaged goods.

philipp
philipp
  • Moderator
more options

not the firefox implementation but how webrtc is spec'ed out at the moment is the problem at hand... other browsers do have the same issue.