If you're new to Sauce Connect Proxy or troubleshooting, this list of frequently asked questions can help you with what you need to know.
Sauce Connect can only communicate with Sauce Labs via
port 443. This is not configurable.
To share a tunnel, start a tunnel with the
--shared-tunnel flag. For most Sauce Labs customers, your access to shared tunnels is determined by the permissions of the user who creates them. Organization admins can create tunnels that any user on any team can use. Team admins can create tunnels that any member of their team can use. Team members cannot share tunnels they create with any other team member.
In order to use a tunnel that an admin or team member shares with you, you'll need to add
parentTunnel to your desired capabilities and specify that person's username.
More information: Shared Tunnels.
You can use the
--fast-fail-regexps command-line option to drop requests that fit a description altogether. It can be used to simulate non-loading of scripts, styles, or other resources.
This flag can contain a list of regex that will match the domain that wants to be blocked. Example:
Entering this code --
(www.)?google-analytics.com,(www.)?googletagmanager.com,([a-z0 9]+[.])*google.com,([a-z0-9]+[.])+facebook.com -- will block the following domains:
google.comand any subdomain of
- Any subdomain of
facebook.com, but not
When using Sauce Connect Proxy, local web apps running on commonly used ports are available to test at localhost URLs, just as if the Sauce Labs cloud were your local machine.
However, because an additional proxy is required for localhost URLs, tests may perform better when using a locally defined domain name (which can be set in your
hosts file) rather than localhost. Using a locally defined domain name also allows access to applications on any port.
NOTE: On Android devices, ports 5555 and 8080 cannot be used with Sauce Connect Proxy.
The following commonly used browsers and ports are subject to change as new versions are released:
Microsoft Edge, Chrome 71+ and the Safari browser on OS X 10.10+ and mobile iOS 8+ proxy these common ports:
Feel free to do either, even if you only have one Sauce account.
If you do decide to use five separate instances, you'll need to create unique identifiers for each. More information: High Availability Sauce Connect Proxy Setup.
Sauce Connect Proxy offers some options for high availability that enable multiple Sauce Connect Proxy tunnels to be grouped into a pool, which is treated like a single tunnel. This has several advantages, including the ability to distribute the load of test traffic. More information: High Availability Sauce Connect Proxy Setup.
Yes. More information: Mobile Testing Frameworks.
Your options depend on your license type. More information: System and Network Requirements for Sauce Connect Proxy.
There are currently no limits on how many tests you can run in each tunnel, though we may eventually implement limitations to maintain service quality. More information: System and Network Requirements for Sauce Connect Proxy.
No, tunnels to the Real Device Cloud are automatically shared with all of your team members. More information: Security Settings for Organizations.
Yes, you can use the same Sauce Connect Proxy tunnel and/or same machine to test with the Virtual Device Cloud Real Device Cloud.
NOTE: If you're still using Legacy RDC, you will need to configure separate, unique tunnel for virtual devices and real devices. More information: Creating a Sauce Connect Tunnel for Legacy Real Device Cloud.
No, though you cannot use the
localhost address with iOS.
To create a secure connection, we strongly recommend using Sauce Connect or IPSec VPN instead of whitelisting IP ranges. More information: Why Sauce Labs Recommends Sauce Connect Proxy Over Whitelisting IP Addresses.