Below are some tips on using Secure Tunnels in BitBar.
Check the tunnel status
It’s important the tunnel is on before you create or run your tests. You can check the tunnel status at any time on the BitBar website. Regardless of the way you started the tunnel, the following label on the toolbar will be “On” if the tunnel is up and running. If the tunnel is inactive, the label is “Off”:
How to get the API key
Log in to BitBar, click the user icon in the top-right corner, and select My Account.
Go to [My Integrations] API Access > API tab and copy the API key value:
Connecting via proxy
If your computer connects to the Web via HTTP or HTTPS proxy, you may need to specify the proxy settings for connection. To do this, use the command-line utility to set up the connection, and put the
--httpProxy parameter to the command line to specify the proxy settings. See the parameter description for an example.
How to refer to local resources in tests
Some test devices running in the cloud treat the names
local, and the address
127.0.0.1 in a special way (they can use them, for instance, for internal routing). This means that these names and this IP address might not work in your tests.
To refer to local resources, we’d suggest using the internal IP address of your machine. Alternatively, you can set up some alias for
localhost in the hosts file on your computer (that is, on the computer where the tunnel executable is running) and use this alias in your tests.
Logging the tunnel work
By default, the tunnel posts message about its work to the <your user folder>/.sb-tunnel/tunnel.log file.
If you start the tunnel from the command line, you can add the
--verbose command-line argument to log messages to the command-line window.