We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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.

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Firefox leaks the true IP address when using a VPN.

  • 3 răspunsuri
  • 1 are această problemă
  • 7 vizualizări
  • Ultimul răspuns de philipp

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?

Toate răspunsurile (3)

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...

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.

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.