LambdaTestTesting Locally Hosted Pages ● Beta Lambda Tunnel For Corporate Firewalls/ Enterprise Restricted Environments

Beta Lambda Tunnel For Corporate Firewalls/ Enterprise Restricted Environments

Lambda Tunnel feature allows you to test your private server URLs or locally hosted websites or web-apps through LambdaTest cloud servers by establishing a secure shell connection. However, sometimes corporate firewalls and proxy setting may have restricted you to leverage the Lambda Tunnel binary. Not anymore though, as we’ve come up with a new binary for Lambda Tunnel.

This Beta Lambda Tunnel binary will help you establish a secure connection through corporate firewalls between your computer and LambdaTest cloud servers for testing locally hosted website or web-applications. You can also test plain HTML, CSS, PHP, Python or other similar web files saved on your local system, on 2000+ combinations of operating systems, browsers, and screen resolutions that are available on LambdaTest.

You can download this Lambda Tunnel to establish a secure connection through your corporate firewalls, proxies:

Executing Lambda Tunnel for Beta Client Connection

After you download the zip file for your operating system, extract it in a folder and open you command line there. Once you have your terminal routed to the correct directory where the Lambda Tunnel binary file is placed, you need to execute the below command.

So for example, if your details are as below:

  • Email:
  • LambdaTest Access Key: 123asd123
  • Tunnel Name: SampleTunnel

Then your command would be:

tunnel command in terminal

Once you execute the command, you will successfully establish a beta-client connection using the Lambda Tunnel. You will find the command logs to state, that you are now ready to test.


What Makes The New Lambda Tunnel Binary Special?

Well, other than the fact that you can now establish a connection through your corporate firewalls with the new Lambda Tunnel binary. Here are a couple things to top it off.

Auto Update Functionality

Earlier, for every version update in out Lambda Tunnel, you were compelled to download the latest binary from our platform and over write it over the outdated version in your computer. Well, now this new binary will take care of that. Everytime you execute this binary, it will check for the latest version available and will update itself automatically, in case it gets outdated.

Default Port 443

Now, by default, everything will run over the port 443 to ensure a secure web browser communication through http protocol over TLS/SSL.

Leverage .lt.yaml file

With this new Lambda Tunnel binary, you can declare your LambdaTest authentication credentials in a YAML file configuration and keep it in the same directory as the LT binary file. That way, you won’t have to pass the environment variables in the cmd everytime you wish to configure the Lambda Tunnel. Once you specify these variables in the .lt.yaml file, you will just have to execute the binary file through cmd LT.exe and the YAML file will automatically configure a secure Lambda Tunnel connection by auto detecting the variables specified in the YAML file.

just run lt binary from cmd

Here is an example of the .lt.yaml file.

Note: You will need to replace this file with your credentials and it has to be named exactly “.lt.yaml“. Once you specify the proxy information as environment variable, it gets auto detected.

Similarly, you can go ahead and pass any other variables by just specifying them in the YAML file. For example, if you wish to have verbose variable passed on for detailed logs while the binary is being configured. You will add the verbose flag in your YAML file:

Now, when you trigger the binary file through cmd. You will have your verbose logs populated automatically, without you having to specify the variable every time.

verbose logs for lt binary

Tunnel Arguments

You can find all the arguments for LambdaTest Tunnel by running the below command in your command line:

You have already executed the mandatory arguments for Lambda Tunnel. Here is a list of optional arguments that you can leverage to establish a beta-client connection with LambdaTest through specific proxy details, callback URL, custom SSH Host, verbose logs, and more.

Arguments Description
--verbose Ensures every proxy request is logged to stdout.
--proxy-host string Full hostname for the proxy you’d like to use.
--proxy-port string The port declared by you for fetching the proxy.
--proxy-user string Your proxy username.
--proxy-pass string Your proxy password
--shared-tunnel To share a Lambda Tunnel among teammates.
--version Specifies the version of your Lambda Tunnel binary.
--pidfile string Path of the pidfile, where process ID will be written.
--mitm Test websites using self signed certificates on your local system or internal network.
--pac string Specify the path of a pac file.
--output-config Print used config on console as JSON.
--nows Forces tunnel to run in polling mode.
--logFile string Location of the tunnel log file.
--local-domains string Comma separated list of local domains.
--infoAPIPort int Exposes tunnel info API at the specified port.
--env string Specify the Environment label.
--emulateChrome Emulates Google Chrome while establishing tunnel.
--dns string Specify the Environment label.
--dir string Comma separated list of DNS servers.
--CustomSSHHost string Custom SSH host to use for debugging.
--CustomSSHPort string Custom SSH port to use for debugging.
--CustomSSHUser string Custom SSH user to use for debugging
--CustomSSHPrivateKey string Custom SSH Private Key to use for debugging.
--controller string Specifies controlling environment for tunnel possible values: [standalone, Jenkins, CircleCI, npm].
--config string The config file to use.
--callbackURL string Callback URL for tunnel status.
--bypassHosts string Comma separated list of hosts to bypass from tunnel. These will be routed through internet.

That was all you need to know for configuring a beta-client connection through Lambda Tunnel. In case you have any questions, feel free to share them with us through our 24/7 chat support or drop us an email to Happy testing! 🙂