Skip to content

Commit 3ccd6dc

Browse files
committed
permanent tunnels text
1 parent 75fdaff commit 3ccd6dc

File tree

1 file changed

+3
-1
lines changed
  • src/content/post/2025/04-20-ssh-tunnel-docker

1 file changed

+3
-1
lines changed

src/content/post/2025/04-20-ssh-tunnel-docker/index.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ publishDate: 2025-04-20
66
heroImage: '../../../../content/post/2025/04-20-ssh-tunnel-docker/_images/ssh-tunnel-architecture-16-9.png'
77
heroAlt: SSH tunnel Docker architecture diagram
88
tags:
9-
- docker
109
- devops
10+
- docker
1111
category: tutorials
1212
toc: true
1313
draft: true
@@ -366,6 +366,8 @@ networks:
366366
367367
If you have a really big number of services to tunnel you might want to use a VPN to access all ports by default, but thats rarely the case.
368368
369+
Another point to make is that SSH tunnel technique is most suitable for temporary exposing services for demo purposes. For permanent tunnels you would need to add `autossh` to keep connection alive, but there are a better tools for permanent tunnels, like [rapiz1/rathole](https://github.com/rapiz1/rathole) or [fatedier/frp](https://github.com/fatedier/frp).
370+
369371
## Open firewall on VPS
370372

371373
For the main SSH connection you will need to open a port in your VPS firewall, port `1080` in this example. Additionally, if you want to access tunnels directly via port in the browser without Traefik, you will need to open those ports too. Be mindful not to open to many unneeded ports as every new opened port increases the attack surface.

0 commit comments

Comments
 (0)