CreepJS shows WebRTC blocked/unsupported after applying BAS fingerprint. How to fix?

[daisyfang01]

Hello everyone,

I am testing my BAS + FingerprintSwitcher setup on:
https://abrahamjuliot.github.io/creepjs/

My current BAS workflow is:

1. Set SOCKS5 proxy
2. Get fingerprint
3. Apply fingerprint
4. 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:

1. Why does WebRTC appear as blocked/unsupported even after applying fingerprint?
2. Is this caused by BAS itself, FingerprintSwitcher settings, or proxy configuration?
3. Which settings should I change to make CreepJS look more natural?
4. Should WebRTC be set to "Replace", "Forward", or another mode?
5. Is it better to use residential proxies for this?

Any advice or example BAS configurations would be greatly appreciated.

Thank you!

[daisyfang01]

@Moderator

[Roy Mustang]

u have wrong sequence:

0. Set up profile
1. Get fingerprint
2. Apply fingerprint
3. Set SOCKS5 proxy
4. Open target URL