We have self-hosted server, agent and viewer all updated to last version. Suddenly today we could not connect to one of our agents. Server log shows nothing.
Viewer log shows this:
07-12-2023__12.26.05__912 Connection #109552. Connection to "test". Mode: <Authorization>. Connecting...
07-12-2023__12.26.05__912 InetConnection #109552. Internet connection to test (hidden:5655).
07-12-2023__12.26.05__918 InetConnection #109552. Method "Connect" - OK. test connected to ID server: hidden.
07-12-2023__12.26.05__924 InetConnection #109552. Socket error. Name: "test", host: "hidden:5655". Exception class: "EIdConnClosedGracefully". Message: "Connection Closed Gracefully.".
07-12-2023__12.26.05__924 Connection #109552. Connection to "test" failed. Mode: <Authorization>.
07-12-2023__12.26.05__924 Context #109552 removed. Mode: <Authorization>.
There has been no changes in authorization details, and it's also been checked and re-verified multiple times. We only use simple password and pin.
One thing we noticed was that there was 8-9 inactive agents listed on the self-hosted server service in admin GUI. Nbtstat also showed a lot of TIME_WAIT after stopping the service (trying to restart it multiple times). If we waited until those TIME_WAIT were gone before starting the service again, it suddenly worked to connect again. Not sure if this was unrelated or not. We tried a Viewer on another computer as well, same error. Both suddenly worked at the same time again if we waited for those TIME_WAIT to go away. But this seems to be a recurring problem...
I wish the log said WHY the Socket error occurs.
