[GH-ISSUE #130] How to SSH to the client using go-http-tunnel implementation #76

New issue

Closed

opened 2026-05-05 10:59:53 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 10:59:53 -06:00

Owner

Originally created by @LiveEarth on GitHub (Apr 18, 2021).
Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/130

Hello team, @mmatczuk I follow your instruction and create server and client side part of go-http-tunnel (implemented ./tunneld and ./tunnel)
Everything works fine, but don't know how to use ssh tunnel option:

server_addr: SERVER_IP:5223
tunnels:
  webui:
    proto: http
    addr: localhost:8080
    auth: user:password
    host: webui.my-tunnel-host.com
  ssh:      <== HOW TO USE THIS OPTION?
    proto: tcp
    addr: 192.168.0.5:22
    remote_addr: 0.0.0.0:22

My question are how to use go-http-tunnel to SSH to the client?

Best regards, be healthy

Originally created by @LiveEarth on GitHub (Apr 18, 2021). Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/130 Hello team, @mmatczuk I follow your instruction and create server and client side part of go-http-tunnel (implemented ./tunneld and ./tunnel) Everything works fine, but don't know how to use ssh tunnel option: server_addr: SERVER_IP:5223 tunnels: webui: proto: http addr: localhost:8080 auth: user:password host: webui.my-tunnel-host.com ssh: <== HOW TO USE THIS OPTION? proto: tcp addr: 192.168.0.5:22 remote_addr: 0.0.0.0:22 My question are how to use go-http-tunnel to SSH to the client? Best regards, be healthy

gitea-mirror closed this issue

2026-05-05 10:59:54 -06:00

gitea-mirror commented

2026-05-05 10:59:58 -06:00

Author

Owner

@LiveEarth commented on GitHub (Apr 24, 2021):

No answer from developer

@LiveEarth commented on GitHub (Apr 24, 2021): No answer from developer

gitea-mirror commented

2026-05-05 10:59:59 -06:00

Author

Owner

@mfoe87 commented on GitHub (Dec 29, 2021):

change remote_addr to something like 0.0.0.0:2222 in your client config. This will bind port 2222 on the server. After that you connect to ssh like you normally do

$ ssh user@127.0.0.1 -p 2222
That will connect to whatever the client is configured to, in your case it means 192.168.0.5:22

So if you have a lot of connections make sure you have free ports available on the server

@mfoe87 commented on GitHub (Dec 29, 2021): change remote_addr to something like 0.0.0.0:2222 in your client config. This will bind port 2222 on the server. After that you connect to ssh like you normally do `$ ssh user@127.0.0.1 -p 2222` That will connect to whatever the client is configured to, in your case it means `192.168.0.5:22` So if you have a lot of connections make sure you have free ports available on the server

gitea-mirror referenced this issue

2026-05-05 11:02:37 -06:00

[PR #127] Fix backoff inconsistency, error pages, minimal API, keepalive configurable,... #152