@gjimenez7272 I recommend you identify the process that Browserstack runs as and define it as certificate-pinned application.  More reading about certificate-pinned applications is here: https://docs.netskope.com/en/exceptions-352649.html#UUID-721191f0-9267-9f7f-ce55-6da717757672_section-idm4552600832220832936441602365

Thank you very much. I will give this a shot. I really appreciate the information. 

Hi gjimenez7272,
did you solve your problem? I am dealing with the same issue.

We have out of steering the domain "*.browserstack.com" and "browserstack.com". Unfortunately, the process that works with browserstack is, from the logs: "process: google chrome helper"

In our logs, each line with the string "browserstack" is being bypassed, however, developers still having issues with the tool.

Any ideas?

Thank you very much.

Hi Miguel,

In a similar situation to yourself. Did you ever find a workaround for this problem?

Thanks a lot!

Not yet 😞

Hi All,

Has there been any update on this topic. We have just come across this issue ourselves.

I have put in place a steering bypass for *.browserstack.com and browserstack.com, and also created a new app definition for browserstacklocal.exe and any traffic originating from that process to any destination is also excluded from being steered to Netskope.

We are still having some connectivity issues though, and I'm not overly fond of a global steering exception. Looking for any further guidance!

Cheers.

I've just seen this from browserstack official FAQ

I'm trying this solution

Our employee confirms it works now