Skip to content

Commit 217110b

Browse files
authored
Merge pull request LambdaTest#1238 from amanchopra1905/stage
added the public IPs for the tunnel service
2 parents 420d93e + b8fb3b9 commit 217110b

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

docs/troubleshooting-lambda-tunnel.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -105,14 +105,10 @@ If you are testing a server that requires IP whitelisting, then you just have to
105105
- 23.82.88.184
106106
- 23.106.34.219
107107
- 23.106.54.77
108-
109-
> Below are IPs that will be deprecated soon
110-
> - 3.214.241.254
111-
> - 52.36.84.247
112-
> - 13.126.37.58
113-
> - 3.66.78.89
114-
115-
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.
108+
- 3.214.241.254
109+
- 52.36.84.247
110+
- 13.126.37.58
111+
- 3.66.78.89
116112

117113
## 5. Custom Host Name
118114
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.

0 commit comments

Comments
 (0)