WebRTC: through the proxy, a chosen address, off or real?
WebRTC is the part of the browser that makes video calls and peer-to-peer connections work. To do that, it can find out which addresses your computer is reachable on — and a website can ask for them. That is why WebRTC is the most common way a proxy "leaks": the page sees the proxy's IP in the normal request and your own IP through WebRTC.
Each profile has a WebRTC setting with four choices. Here is what each one shows to a website.
Through the proxy only (recommended)
WebRTC stays inside the proxy. A site that asks for your addresses learns nothing about your computer; on Firefox profiles it sees the proxy's address, which is what a normal browser behind that connection would show. This is the default for profiles with a proxy and the right choice for almost all account work.
Through the proxy, showing an address you choose
Some sites expect a specific public address to appear in WebRTC. With this option you enter a public IPv4 or IPv6 address, and that is what WebRTC shows; nothing goes outside the proxy. Use it only when a site really needs a particular address: strict checkers notice when the WebRTC address differs from the proxy's exit IP.
This option works on the anti-detect OwlX kernel and on Firefox profiles. Standard Chrome can't show a chosen address without a page script — and checkers find those — so on standard Chrome profiles WebRTC simply stays inside the proxy.
Disabled
WebRTC is turned off completely. Nothing can leak, but video calls and some web apps stop working, and "WebRTC is missing" is itself unusual for a desktop browser. Prefer through the proxy only unless you have a reason.
Real
WebRTC behaves like an unprotected browser: websites can see your own IP address, even through a proxy. Only use this on profiles without a proxy, where your own address is the point.
How to check what a site sees
Open the profile menu (⋯) and choose Leak check. In about forty seconds it tests:
- Sites — the IP that pages see;
- IPv6 — whether your own IPv6 address shows;
- WebRTC — which address WebRTC reveals, if any;
- DNS — whether name lookups go through the proxy or your own DNS server;
- Headers — whether the proxy forwards your IP in headers;
- Direct connections — whether anything connected around the proxy.
"No leaks: sites see only the proxy" is the result you want. If WebRTC shows your own address, switch the profile to through the proxy only and check again.
Quick answers
- Do I need to change anything? Usually not: profiles with a proxy start with through the proxy only.
- Does this slow anything down? No. Calls that need WebRTC run through the proxy like everything else.
- Can the setting differ per profile? Yes, it is part of each profile's network settings.