Tunnel Settings

Applies to CrossBrowserTesting SaaS, last modified on October 22, 2021

The The SmartBear Secure Tunnel is available in form of a desktop application, command line utility and the Enterprise Connection Manager. All they use similar options to specify the connection details.

Connection type

Internal Websites

Most basic type of tunnel that works in most cases. It creates an encrypted tunnel that allows traffic and requests to be routed through the local network of your computer. This allows you to test sites that are only accessible through your local network or behind your firewall.

Local HTML files

CrossBrowserTesting and your machine are connected via an encrypted tunnel that also temporarily runs a small web server. When using the http://local/ domain, requests are directed to this temporary web server that runs on your machine. Also, you need to ensure that it points to the desired root directory.

When running a Live Test, Screenshot Test, or Selenium Test

  • With http://local/ you can access the directory index of the folder specified during the setup.
  • With http://local/yourfile.html you can access the yourfile.html page in the directory.

Remember that only requests for http://local/ are sent to the temporary web server. Any other requests for domains are sent directly to the web site.

Proxy Server

Select this mode to send requests from the CrossBrowserTesting cloud device to the tested web app through some server. That “intermediate” server can perform certain traffic modifications like adding or changes certain headers. This mode is also useful for corporate environments that require proxies for HTTP/HTTPS traffic.

If you select this mode, you will need to specify the following settings:

Proxy IP

The IP address of the proxy server in your network.

Proxy Port

The proxy port number.

Additionl options

Bypass tunnel for public URLs

When the tunnel is up and running, it routes requests from the test device to the tested server app. Select this check box if you want to skip using the tunnel for requests that the tested client app sends to publicly available websites. This will generally speed up tests since many applications call publicly available resources.

If the tunnel is unable to resolve a URL publicly, it resolves it through the user computer.

Accept all SSL certificates

Select this check box so that the tunnel considers all security certificates as valid. This is useful for testing interim versions of websites and services which may have self-signed or invalid certificates.

Requirements and limitations

  • As a tunnel creates a secure connection, outbound ssh requests travel on the port 443 to be encrypted. Please remember to allow SSL on crossbrowsertesting.com via your firewall.

  • The Java tunnel options are deprecated and will not be supported shortly.

See Also

Local Testing — Secure Tunnels
SecureTunnel Desktop App
SecureTunnel Command Line
Secure Tunnels – Tips

Highlight search results