From e5c0cb489890b3f15963682dd8d922c4e7b212b5 Mon Sep 17 00:00:00 2001 From: Rowena Date: Wed, 23 Oct 2024 09:40:05 +0200 Subject: [PATCH 1/3] fix(pgw): ssh bastion info --- .../cant-connect-to-instance-with-pn-gateway.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx b/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx index 87fe56eab3..81b9942c9d 100644 --- a/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx +++ b/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx @@ -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. \ No newline at end of file +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/). + + +While SSH bastion is the recommended solution, another manual workaround for advanced users is to 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. + \ No newline at end of file From ba74f9469a2859350d91889d94d1f41b8ce4a89f Mon Sep 17 00:00:00 2001 From: Rowena Date: Wed, 23 Oct 2024 09:47:26 +0200 Subject: [PATCH 2/3] fix(pgw): more --- .../cant-connect-to-instance-with-pn-gateway.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx b/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx index 81b9942c9d..50d43d61a8 100644 --- a/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx +++ b/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx @@ -27,5 +27,5 @@ If DHCP **is** activated and your Public Gateway **is** set to advertise a defau 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/). -While SSH bastion is the recommended solution, another manual workaround for advanced users is to 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. +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 (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. \ No newline at end of file From b1a0acfca2118e8f889cd778848d977627cb6231 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 23 Oct 2024 16:42:51 +0200 Subject: [PATCH 3/3] Update network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx Co-authored-by: nerda-codes <87707325+nerda-codes@users.noreply.github.com> --- .../cant-connect-to-instance-with-pn-gateway.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx b/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx index 50d43d61a8..d7c14450e2 100644 --- a/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx +++ b/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx @@ -27,5 +27,5 @@ If DHCP **is** activated and your Public Gateway **is** set to advertise a defau 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/). -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 (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. +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`. \ No newline at end of file