When using a Sauce Connect tunnel and navigating to a site using Chrome, you might see an error saying the connection is not private and not let you access the site.
This is because by default traffic on Sauce Connect is re-encrypted using our own self-signed certificates. While this can be trusted on our Virtual Cloud as well as our iOS devices, due to security specifications by Google the same can't be done on Android.
A workaround for this is to use our -B (--no-ssl-bump-domains) flag with the value "all" or a comma separated list of domains that will not get re-encrypted. This will avoid re-encryption and use whatever certificate the origin server has.
NOTE: If the origin server has a self-signed, internal CA certificate, or intermediate CA certificate, the same issue will still be seen.
If this is the case, a site not using https or obtaining a publicly available cert will be required.
For more information on Sauce Connect on our Real Device Cloud see here.