WebRTC leak

A

artificials

Power Member
Joined
Aug 17, 2024
Messages
580
Reaction score
184
Is WebRTC leak in browsersleak test a problem of the proxy or a problem the antidetect browser?
I noticed in dolphine it reveals the local ip even though it is set to "Altered" the profile setting.
 
Advertise on BHW
That’s actually an issue with the antidetect browser, not the proxy.
Proxies don’t block WebRTC leaks,it’s up to the browser to handle that. Try disabling WebRTC fully.
 
artificials said:
Is WebRTC leak in browsersleak test a problem of the proxy or a problem the antidetect browser?
I noticed in dolphine it reveals the local ip even though it is set to "Altered" the profile setting.
Click to expand...
That's pretty insane that an "anti-detect" browser wouldn't be blocking that by default but it's definitely a browser issue. According to their site, that Dolphin browser should have a WebRTC setting that you can change. If you scroll down not quite halfway here https://dolphin-anty.com/blog/en/what-different-digital-fingerprint-settings-mean/ you should see the WebRTC section.

You should also check for DNS leaks, especially if you're using a SOCKS5 proxy. Most browsers do not use the proxy DNS by default when using SOCKS5.
 
travch1s said:
That’s actually an issue with the antidetect browser, not the proxy.
Proxies don’t block WebRTC leaks,it’s up to the browser to handle that. Try disabling WebRTC fully.
Click to expand...
Don't know if I turn that off, it may raise some flaggs.
 
artificials said:
Is WebRTC leak in browsersleak test a problem of the proxy or a problem the antidetect browser?
I noticed in dolphine it reveals the local ip even though it is set to "Altered" the profile setting.
Click to expand...
set it to "real" in order to fix it.
not sure how they do it under the hood but i used to turn off non proxied udp chromium.
 
WEBRTC leak is very annoying, I recommend you to use GoLogin instead
 
Would be helpful to know if other people experienced WebRTC leak with dolphine.
 
Definitely test another anti detect browser and see if you're getting the leak with that
 
Proxy Cake said:
Definitely test another anti detect browser and see if you're getting the leak with that
Click to expand...
I read help of dolphine and it says, if by setting WeRTC to altered you still get a different ip, contact the proxy provider. I am not sure yet whether it has something to do with proxy or browser.
 
Its the browser, as it needs to adjust the code of webrtc so it shows the proxy IP instead of leaking. What are you using for the browser?
 
artificials said:
Is WebRTC leak in browsersleak test a problem of the proxy or a problem the antidetect browser?
I noticed in dolphine it reveals the local ip even though it is set to "Altered" the profile setting.
Click to expand...
Use a simple setup with Firefox + FoxyProxy and disable WebRTC in about:config (media.peerconnection.enabled = false). We use this setup and never get WebRTC leaks. Most antidetect browsers also let you disable WebRTC in their settings.
 
Proxy Marketplace said:
Use a simple setup with Firefox + FoxyProxy and disable WebRTC in about:config (media.peerconnection.enabled = false). We use this setup and never get WebRTC leaks. Most antidetect browsers also let you disable WebRTC in their settings.
Click to expand...
This setup definitely works. You could also consider using Waterfox, a Firefox fork that's more privacy-focused, as an alternative browser.
 
Yeah, as already mentioned, that’s probably on the antidetect browser, not the proxy. Proxies (even high-quality ones) don’t mess with your local IP, that’s the browser’s job. Now, if your public IP is leaking through WebRTC, then it might be a proxy issue - like it’s not handling STUN traffic right or it’s just set up wrong. Dolphin telling you to hit up your proxy provider only makes sense if your external IP is showing. But since it's just your local IP, you’re better off flipping “WebRTC: Off” and testing again. If it’s still acting up, probably best to reach out to Dolphin support directly.
 
Proxy Marketplace said:
Use a simple setup with Firefox + FoxyProxy and disable WebRTC in about:config (media.peerconnection.enabled = false). We use this setup and never get WebRTC leaks. Most antidetect browsers also let you disable WebRTC in their settings.
Click to expand...
That is also suspicious. Public IP should be the same as IP.
 
OnlineProxyIO said:
Yeah, as already mentioned, that’s probably on the antidetect browser, not the proxy. Proxies (even high-quality ones) don’t mess with your local IP, that’s the browser’s job. Now, if your public IP is leaking through WebRTC, then it might be a proxy issue - like it’s not handling STUN traffic right or it’s just set up wrong. Dolphin telling you to hit up your proxy provider only makes sense if your external IP is showing. But since it's just your local IP, you’re better off flipping “WebRTC: Off” and testing again. If it’s still acting up, probably best to reach out to Dolphin support directly.
Click to expand...
In local ip it shows the ip we use to access modem setting.
In public IP, it reveals the real ip
 
Advertise on BHW
You must log in or register to reply here.
Sign up now!

Main Menu

Home Main Forum List Black Hat SEO White Hat SEO BHW Newbie Guide Blogging Black Hat Tools Social Networking Downloads

Marketplace

Account Selling Content / Copywriting Hosting Images, Logos & Videos Proxies For Sale SEO - Link building SEO - Packages Social Media Social Media - Panels Misc

Making Money

Affiliate Programs Hire a Freelancer Making Money Pay Per Click Site Flipping

BlackHatWorld

BHW Merch Forum Suggestions & Feedback Introductions Lounge Dispute Resolution

Other

Domain Name Forum IM Journeys Web Hosting Newsletter
Back
Top