up
CreepJS shows WebRTC blocked/unsupported after applying BAS fingerprint. How to fix?
-
Hello everyone,
I am testing my BAS + FingerprintSwitcher setup on:
https://abrahamjuliot.github.io/creepjs/My current BAS workflow is:
- Set SOCKS5 proxy
- Get fingerprint
- Apply fingerprint
- Open target URL
Screenshot of my BAS settings:
[attach image 1]However, when I open CreepJS, the result shows:
- WebRTC: blocked
- foundation/ip: unsupported
- stun connection: blocked
Screenshot:
[attach image 2]I want the browser fingerprint to look more like a normal real user browser.
My questions are:
- Why does WebRTC appear as blocked/unsupported even after applying fingerprint?
- Is this caused by BAS itself, FingerprintSwitcher settings, or proxy configuration?
- Which settings should I change to make CreepJS look more natural?
- Should WebRTC be set to "Replace", "Forward", or another mode?
- Is it better to use residential proxies for this?
Any advice or example BAS configurations would be greatly appreciated.
Thank you!
-
-
u have wrong sequence:
- Set up profile
- Get fingerprint
- Apply fingerprint
- Set SOCKS5 proxy
- Open target URL
-
@Roy-Mustang
@Moderator
Thanks for your reply. I’m a bit confused because I don’t see any action named “Set up profile” in BAS.Also, why should the fingerprint be applied before setting the SOCKS5 proxy? My understanding is that the SOCKS5 proxy should be set first, then the country/IP should be detected, and only after that should the fingerprint be generated/applied based on that country.
Is my understanding wrong, or is there another recommended sequence for this?
-
@daisyfang01 said in CreepJS shows WebRTC blocked/unsupported after applying BAS fingerprint. How to fix?:
“Set up profile”
these action based on action 'browser settings'
@daisyfang01 said in CreepJS shows WebRTC blocked/unsupported after applying BAS fingerprint. How to fix?:
proxy should be set first
No, the bot sends requests to its own servers when it receives a fingerprint, you won't be detected.
