[GH-ISSUE #126] stuck at handshake. #74

Open
opened 2026-05-05 10:59:43 -06:00 by gitea-mirror · 2 comments
Owner

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

When I run the start-all client command, it gets as far as the handshake then gets stuck. I have been using go-http-tunnel reliably for months to ssh into my remote sensors. This started happening after I had some problems with systemD. I have tried using different ports in my tunnel.yml. I have also tried apt update, apt upgrade with no luck. Here is the output or the command.

2021/03/18 14:19:00 config server_addr: xxx.xxx.xxx.xxx
tls_crt: /home/pi/.tunnel/client.crt
tls_key: /home/pi/.tunnel/client.key
root_ca: ""
backoff:
interval: 500ms
multiplier: 1.5
max_interval: 1m0s
max_time: 0s
tunnels:
ssh:
proto: tcp
addr: localhost:22
remote_addr: 0.0.0.0:40008

2021/03/18 14:19:00 level 1 action start
2021/03/18 14:19:00 level 1 action dial network tcp addr xxx.xxx.xxx.xxx:10008
2021/03/18 14:19:00 level 1 action handshake addr xxx.xxx.xxx.xxx:10008

Originally created by @synaption on GitHub (Mar 18, 2021). Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/126 When I run the start-all client command, it gets as far as the handshake then gets stuck. I have been using go-http-tunnel reliably for months to ssh into my remote sensors. This started happening after I had some problems with systemD. I have tried using different ports in my tunnel.yml. I have also tried apt update, apt upgrade with no luck. Here is the output or the command. 2021/03/18 14:19:00 config server_addr: xxx.xxx.xxx.xxx tls_crt: /home/pi/.tunnel/client.crt tls_key: /home/pi/.tunnel/client.key root_ca: "" backoff: interval: 500ms multiplier: 1.5 max_interval: 1m0s max_time: 0s tunnels: ssh: proto: tcp addr: localhost:22 remote_addr: 0.0.0.0:40008 2021/03/18 14:19:00 level 1 action start 2021/03/18 14:19:00 level 1 action dial network tcp addr xxx.xxx.xxx.xxx:10008 2021/03/18 14:19:00 level 1 action handshake addr xxx.xxx.xxx.xxx:10008
Author
Owner

@hons82 commented on GitHub (Mar 30, 2021):

I haven't used ssh tunnel so far, but in the case of http tunnel this handshake log message is the last message I see when the tunnel is up and running.

<!-- gh-comment-id:810351095 --> @hons82 commented on GitHub (Mar 30, 2021): I haven't used ssh tunnel so far, but in the case of http tunnel this handshake log message is the last message I see when the tunnel is up and running.
Author
Owner

@dipenpatel235 commented on GitHub (May 29, 2021):

When I run the start-all client command, it gets as far as the handshake then gets stuck. I have been using go-http-tunnel reliably for months to ssh into my remote sensors. This started happening after I had some problems with systemD. I have tried using different ports in my tunnel.yml. I have also tried apt update, apt upgrade with no luck. Here is the output or the command.

2021/03/18 14:19:00 config server_addr: xxx.xxx.xxx.xxx
tls_crt: /home/pi/.tunnel/client.crt
tls_key: /home/pi/.tunnel/client.key
root_ca: ""
backoff:
interval: 500ms
multiplier: 1.5
max_interval: 1m0s
max_time: 0s
tunnels:
ssh:
proto: tcp
addr: localhost:22
remote_addr: 0.0.0.0:40008

2021/03/18 14:19:00 level 1 action start
2021/03/18 14:19:00 level 1 action dial network tcp addr xxx.xxx.xxx.xxx:10008
2021/03/18 14:19:00 level 1 action handshake addr xxx.xxx.xxx.xxx:10008

hello @synaption can u please help me to fix mine ssh tunnel issue #132 ?

Thanks

<!-- gh-comment-id:850765174 --> @dipenpatel235 commented on GitHub (May 29, 2021): > When I run the start-all client command, it gets as far as the handshake then gets stuck. I have been using go-http-tunnel reliably for months to ssh into my remote sensors. This started happening after I had some problems with systemD. I have tried using different ports in my tunnel.yml. I have also tried apt update, apt upgrade with no luck. Here is the output or the command. > > 2021/03/18 14:19:00 config server_addr: xxx.xxx.xxx.xxx > tls_crt: /home/pi/.tunnel/client.crt > tls_key: /home/pi/.tunnel/client.key > root_ca: "" > backoff: > interval: 500ms > multiplier: 1.5 > max_interval: 1m0s > max_time: 0s > tunnels: > ssh: > proto: tcp > addr: localhost:22 > remote_addr: 0.0.0.0:40008 > > 2021/03/18 14:19:00 level 1 action start > 2021/03/18 14:19:00 level 1 action dial network tcp addr xxx.xxx.xxx.xxx:10008 > 2021/03/18 14:19:00 level 1 action handshake addr xxx.xxx.xxx.xxx:10008 hello @synaption can u please help me to fix mine ssh tunnel issue #132 ? Thanks
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/go-http-tunnel#74
No description provided.