Setting up Local with SSL Inspection in Network

If your network has SSL Inspection along with a proxy, this guide explains how to make your local setup work.

Why doesn’t Local start with SSL Inspection in your network

When you have a SSL Inspection in your local network, the proxy in your network provides a certificate which is not recognised by binary as valid. You will get a [CONN_FAIL:4004] error in this case while trying to access your local website.

How to make it work

In order to resolve this issue, you can follow one of the following steps.

Bypass *.browserstack.com or disable SSL inspection entirely for BrowserStack local

You can talk to your network administrator in order to bypass *.browserstack.com without routing it through SSL Inspection enabled proxy or disable SSL inspection entirely for BrowserStack local connections. This will allow binary to recognise all connections, hence not hindering any requests from and to browserstack devices.

Pass root CA certificates to binary (this is not applicable for the Local Desktop App)

If disabling SSL Inspection for BrowserStack local connections or bypassing *.browserstack.com is not a feasible option for you, you can pass root CA certificates to binary using the following flags:

1. --use-ca-certificate <.pem file>
2. --use-system-installed-ca (for Mac/Linux only)

This option allows binary to recognise the certificate provided by your corporate network as valid (validation of the CA), hence allowing all connections through your proxy to be recognised as valid.