Skip to content

added the public IPs for the tunnel service #1238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 15, 2025
Merged

added the public IPs for the tunnel service #1238

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions docs/troubleshooting-lambda-tunnel.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,14 +105,10 @@ If you are testing a server that requires IP whitelisting, then you just have to
- 23.82.88.184
- 23.106.34.219
- 23.106.54.77

> 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.
- 3.214.241.254
- 52.36.84.247
- 13.126.37.58
- 3.66.78.89

## 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.
Expand Down
Loading