Open supergillis opened 1 year ago
Hello @supergillis , looks like this is a bug on our side. Local Proxy should read the tunnel close notification sent from the cloud and stop retrying to connect to tunnel on destination device. Please be patient with us until we reproduce and resolve this bug. I will try to reproduce the issue first to confirm this bug and then will try to fix it.
For now, as a work around, you can set the number of times your destination device retries to connect to the tunnel after failure. You can set tunneling.proxy.tcp.connection_retry_count
parameter for that as mentioned over here.
-Harsh Gandhi
HI there, I am getting that error: [2023-05-15 22:52:09.956080] (0x0000007fb7f00010) [error] Could not connect to destination 127.0.0.1:22 -- Success after opening tunnel, connecting both source and destination. but when I try to ssh into destination the destination side continuously spits out the error on the destination side. The source side seems to work fine though
Describe the bug
localproxy
gets indefinitely stuck when it cannot connect to the destination, even after closing the AWS secure tunnel. For example, I set uplocalproxy
as destination to port 22.localproxy
correctly logs[error] Could not connect to destination 127.0.0.1:22 -- Success
when nothing is running on port 22. However, when I close the tunnel on AWS,localproxy
does not exit but keeps running forever.To Reproduce
localproxy
in destination mode and point it to a port that does not have a service running.localproxy
in source mode.localproxy
. In my case I used an SSH client.localproxy
keeps running indefinitely.Expected behavior
The destination
localproxy
should exit when the AWS secure tunnel is closed.Actual behavior
The destination
localproxy
keeps running forever when the AWS secure tunnel is closed.Logs
Environment (please complete the following information):
v3.1.0
public.ecr.aws/aws-iot-securetunneling-localproxy/ubuntu-bin:amd64-latest
with image ID21b774378a53