Skip to content

fix(pgw): note recommended solution #3867

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 3 commits into from
Oct 23, 2024
Merged

fix(pgw): note recommended solution #3867

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e5c0cb4
fix(pgw): ssh bastion info
RoRoJ Oct 23, 2024
ba74f94
fix(pgw): more
RoRoJ Oct 23, 2024
b1a0acf
Update network/public-gateways/troubleshooting/cant-connect-to-instan…
bene2k1 Oct 23, 2024
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
8 changes: 5 additions & 3 deletions ...rk/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ If the above two conditions are not true, there may be other factors impacting y

If DHCP **is** activated and your Public Gateway **is** set to advertise a default route, not being able to connect to your Instance via SSH is **expected behavior**. All the traffic towards your Instance now goes through the Public Gateway.

To access your Instance using SSH, either:
- Use [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/), or
- Create a static NAT association between a port of your Public Gateway (eg 2222) and the private IP assigned to your Instance, on the SSH port (22 by default). Then, SSH to the Public Gateway's IP on port 2222.
To access your Instance using SSH in this scenario, the recommended solution is to use [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/).

<Message type="important">
SSH bastion is the recommended solution. For advanced users only, another manual workaround is to create a static NAT association between a port of your Public Gateway (e.g. `2222`) and the private IP assigned to your Instance, on the SSH port (`22` by default). Then, SSH to the Public Gateway's IP on port `2222`.
</Message>