stuck at handshake.

[synaption]

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

[hons82]

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.

[dipenpatel235]

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