There is a problem setting the WebRTC ip. Everytime the "Proxy" is replaced in the middle of a script or if you are using "rotation proxy" the ip webterc is set to "default" by the first one to be used, so if you are running an application and need to switch " proxy "10 times, the first application of the proxy will be compatible WebRTC IP, but the other 9 proxy changes will" load / carry "the first Ip as WebRTC and this does not change, even using actions like" clear cache "" clean mask "nothing changes the WebRTC Ip after it is set at the beginning of the script.
BrowserAutomationStudio 30.6.0 has been released
-
Chrome has been updated to version 151.0.7922.72
-
https://demo.fingerprint.com/playground consistently detects and reports "Browser Tampering", anti_detect_browser: true
incognito: false
privacy_settings: false
suspect_score: 8
tampering: true
tampering_confidence: "medium"
tampering_ml_score: 0.9986
tampering_details: {
anomaly_score: 0
anti_detect_browser: true
} -
@Danger-Lifter это с использованием отпечатка или без? do you use fingerprint switcher?
-
With fingerprint
-
Also I am not sure if it was before, but it detects virtual machine, being run on cloud server,
-
@Danger-Lifter are you using a proxy when running test?
-
yes. just got virtual machine detection, being run on personal laptop
-
@Danger-Lifter
use good proxy -
That was real NL mobile sim card
-
@Danger-Lifter I have found this test is weird sometimes, when using bad proxy browser tampering shows yes, but never does if i use a mobile proxy
