Open kchiem opened 5 months ago
I suggest testing your application on the client side without rathole, it seems that your application is actively refusing the connection.
I did that. Spent a few hours trying other things before I got down to trying a different server port for rathole. Then the rathole errors went away and the application being tunneled was responsive again.
Describe the bug
I had a tunnel where requests through it were very slow and timing out at times. Noticed a bunch of these errors on the server side rathole instance:
Changed the port the server was listening on and the errors and problems went away. It seems just a little bit of unauthorized traffic to the rathole server port was enough to really mess up performance.
To Reproduce Steps to reproduce the behavior:
Configuration Configuration used to reproduce the behavior:
server.toml:
client.toml:
Logs Posted above.
Environment:
rathole --version
output:Build Version: 0.5.0
on both