thr0nic's community posts

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.

Matthew Cooper wrote: ...

Thanks for sharing the similar experience. I'm still working on getting logs the next time it fails. We've had a lot of vacation lately so it's been impractical to troubleshoot.

Pauline wrote:

Hello,

Thank you for your message.

Could you please clarify if you mean the Host service or RU Server's service? In addition, could you please let us know if you have any antivirus and/or firewall software running on the machine where the issue occurs?

Looking forward to your reply.

Thank you for answering.

I mean the RU Server's service, latest version 3.3.4.0 and updated clients. It's running on a Windows Server 2012 R2 with no antivirus, just Windows Firewall. The firewall is configured to open the incoming listening port. Which normally works, but once in a while the clients will go in a connect/disconnect loop until I restart the service, then it works for a fair while again.

I regularly need to restart the service.

Clients will show "Connecting... Disconnected... Connecting... Disconnected" in a loop. When I restart the service, they connect fine. It may take a week or more until I'll have to do it again. Any idea why? For now I've created a scheduled task that restarts the service every night, even so, I sometimes have to do it again the same day.