Skip to end of metadata
Go to start of metadata

Generating Logs for Troubleshooting

By default, Sauce Connect generates log messages to your local operating system's temporary folder. On Linux / Mac OS X this is usually /tmp; on Windows, it varies by individual release. You can also specify a specific location for the output using the -l command line option

You can enable verbose logging with the -v flag. Verbose output will be sent to the Sauce Connect log file rather than standard out.

Network Configuration with Firewalls and Proxies

Is there a firewall or proxy server in place between the machine running Sauce Connect and Sauce Labs (* You may need to allow access in your firewall rules, or configure Sauce Connect to use a proxy. Sauce Connect needs to establish outbound connections to ( on port 443, and to one of many tunnel VMs with IPs in Sauce Labs ranges (,,, also on port 443.

Check out the topics under Sauce Connect and Network Security for examples of how to set up Sauce Connect within various network environments, including examples of dysfunctional network configurations

Checking Network Connectivity to Sauce Labs

Make sure that is accessible from the machine running Sauce Connect. This can be tested by issuing a ping, telnet or cURL command to from the machine's command line interface. If any of these commands fail, you should work with your internal network team to resolve them.

ping Method for Checking Network Connectivity
telnet Command for Checking Network Connectivity
telnet 443 

This command should return an IP address of

cURL Method for Checking Connectivity
curl -v 

This command should return the status message connected to

Disabling SSL Bumping

Sites with Self-Signed Certificates

If the website under test has a self-signed SSL certificate, disabling SSL bumping for the website under test may cause test failures.

Sauce Connect executes a type of "man-in-the-middle" interception of encrypted test traffic through SSL bumping, and decrypts that traffic in the course of the test. An advantage of SSL bumping is that the caching of resources takes place on the Sauce Labs side, resulting in faster test execution. An additional advantage is that traffic is encrypted using the Selenium Project’s CyberVillians certificate, which is inherently trusted by the Selenium server on the Sauce Labs virtual machine where your test is running. This lets you avoid SSL error pop-ups that could disrupt your test execution.

The disadvantage to SSL bumping is that some network components, such as browsers and servers that use WebSockets, won’t work if the traffic to them has been altered, which Sauce Connect appears to do. SSL bumping can also affect sites that are highly dependent on AJAX. In addition, Android 4.4 & 5.0 do not respect the CyberVillains certificate at the system level. All tests on those platforms, including browser and app tests must, disable SSL bumping or else all SSL encryption will fail. This applies to both Android Emulators and Real Devices. Android 5.1 has started adding support for the CyberVillains certificate so disabling SSL bumping is not needed.

When SSL bumping is disabled, test traffic is never decrypted, and passes through directly to the browser running your tests, along with the SSL certificate of the site under test. Because resources are no longer cached on the Sauce Labs side, your tests will execute more slowly, and if there are issues with the originating site’s SSL certificate, these may generate SSL errors that will interfere with test execution. 

You can disable SSL bumping by using the -B / --no-ssl-bump-domains argument when you start Sauce Connect and specifying which domains should not be bumped or specify all so that all domains that passed through the tunnel are not bumped . Check out the Sauce Connect Command Line Reference for more information.

For More Help

If you need additional help, get in touch at To provide our support team with additional information, please add the -vv and -l sc.log options to your Sauce Connect command line, reproduce the problem, and attach the resulting log file (called sc.log) to your support request.