lambdatest tunnel ip

Author: Aman1905

docs/troubleshooting-lambda-tunnel.md

@@ -1,7 +1,7 @@
 ---
 id: troubleshooting-lambda-tunnel
-title: How to troubleshoot LambdaTest Tunnel
-hide_title: true
+title: Troubleshooting LambdaTest Tunnel
+hide_title: false
 sidebar_label: Troubleshooting LambdaTest Tunnel
 description: This document will help you troubleshoot the most common challenges faced during local app testing using LambdaTest Tunnel.
 keywords:
@@ -37,15 +37,10 @@ slug: troubleshooting-lambda-tunnel/
       })
     }}
 ></script>
-
-# Troubleshooting LambdaTest Tunnel
-***
 LambdaTest Tunnel helps in establishing an SSH connection between your local machine and our cloud servers to help you perform tests on locally hosted websites and web-apps. With LambdaTest Tunnel, you can ensure how robust your website rendering is across 3000+ real browsers, even before you make it live on the internet.
 
 If due to some unfortunate reason, you are unable to perform [cross browser testing](https://www.lambdatest.com) using LambdaTest Tunnel then this document will help you troubleshoot the most common challenges.
 
-* * *
-
 Oops !! Facing issue while testing your locally hosted application through LambdaTest Tunnel? Here are a few guidelines for you.
 
 Before proceeding, here are some of the common issues:
@@ -61,9 +56,6 @@ Before proceeding, here are some of the common issues:
 - [LT can’t be opened because Apple cannot check it for malicious software](/docs/troubleshooting-lambda-tunnel/#9-lt-cant-be-opened-because-apple-cannot-check-it-for-malicious-software)
 
 ## 1. Localhost Refused To Connect
-
-* * *
-
 After configuring the tunnel, you might get into the error similar to the below screenshot:
 
 <img loading="lazy" src={require('../assets/images/troubleshooting-lambda-tunnel/localhost-refused-to-connect.webp').default} alt="troubleshoot lambdatest tunnel" width="1600" height="750" className="doc_img"/>
@@ -75,9 +67,6 @@ For example you might find above error with URL: `https://localhost/demo.html`
 however, URL: `https://localhost.lambdatest.com/demo.html` or `10.0.0.15/demo.html` would definitely work fine for you.
 
 ## 2. Invalid Host Header
-
-* * *
-
 While testing an application hosted on your local machine, you may receive an "Invalid Host Header" error message when testing on LambdaTest using a local connection. This error is most commonly caused by a misconfiguration of the application server that causes it to reject non-local connections or reject requests directed at hostnames other than localhost(or any custom one set)
 
 Since, web applications are now built with various different kinds of frameworks like angular, react etc; In order to test it using tunnel the command used to run your web app needs to modified in your project manifest file i.e. "package.json"
@@ -95,9 +84,6 @@ Example: `127.0.0.1 < hostname >`
 This would help you avoiding "Invalid Host Header" error.
 
 ## 3. WordPress - CSS Not Loading
-
-* * *
-
 While testing your local web app built through WordPress, you may find issue with the rendering of CSS, similar to the below screenshot:
 
 <img loading="lazy" src={require('../assets/images/troubleshooting-lambda-tunnel/WordPress-CSS-Not-Loading.webp').default} alt="troubleshoot lambdatest tunnel" width="1600" height="753" className="doc_img"/>
@@ -111,25 +97,26 @@ By applying the above changes, you would find the CSS loading issue as resolved.
 <img loading="lazy" src={require('../assets/images/troubleshooting-lambda-tunnel/hello-world.webp').default} alt="troubleshoot lambdatest tunnel" width="1600" height="758" className="doc_img"/>
 
 ## 4. IP Whitelisting
-
-* * *
-
 If you are testing a server that requires IP whitelisting, then you just have to set up a Local Testing connection and whitelist the below few IP’s for the respective domain:
 
 `http://ts.lambdatest.com/`<br />
 
+- 199.58.84.59 - US East
+- 23.82.88.184 - US West
+- 23.106.34.219 - EU
+- 23.106.54.77 - India
+
+:::note
+Below are IPs that will be deprecated soon
 - 3.214.241.254
 - 52.36.84.247
 - 13.126.37.58
 - 3.66.78.89
+:::
 
 However be advised, as we are aggressively adding more and more data centers, these IP would be changed, you can see the updated IP’s on this documentation as well.
 
-
 ## 5. Custom Host Name
-
-* * *
-
 Because of some firewall restrictions, your web application might not be accessible on some other servers even after whitelisting the IP’s and configuring the tunnel, in such case you need to make an entry in the hosts file which is used to map hostnames to IP addresses. With the hosts file, you can change the IP address that you resolve a given domain name. This change only affects your own computer without affecting how the domain is resolved worldwide.
 
 This is particularly useful when you wish to see how a website will look like when hosted on a different server without making any DNS changes to your domain.
@@ -145,8 +132,6 @@ Let’s say that you wish to resolve **mydomain.com** to the IP address **10.20.
 10.20.30.40 mydomain.com www.mydomain.com
 
 ## 6. Enable Verbose Logging
-* * *
-
 The `- v`  flag enables Verbose logging on the console. You can use this to log the HTTP headers & requests or to debug the LambdaTest Tunnel connection.
 
 The requests are also logged into a log file `lt.log` which is created in the same working directory as the LambdaTest Tunnel binary. You can also specify the tunnel log file name using the `--logFile` flag.
@@ -155,9 +140,6 @@ The requests are also logged into a log file `lt.log` which is created in the sa
 
 
 ## 7. LT Can’t Be Opened Because Apple Cannot Check It For Malicious Software
-
-* * *
-
 Catalina OS users may get the below error from the command line while trying to configure the LambdaTest Tunnel to test their locally hosted web pages:
 "LT can’t be opened because Apple cannot check it for malicious software"