Your comments

I posted this in another thread but I just wanted to let everyone here know that this issue has been identified again as happening with 20.2.  I'm still not sure if it's the exact same issue we previously addressed but it is under active investigation.

Just to follow up, while this issue is indeed registered as a defect, we have not been able to implement a fix quite yet.

The issue is still in the development queue and I will bump it's priority on behalf of you folks in this thread.

this issue is not specifically related to users with the free license tier.  For Control users with a free license, they are automatically included in our pre-release build release channel in order to help us find issues before they make it into the stable version. 

This particular issue is unique solely to the pre-release build on which free users are currently operating.

Typically in the past when I've seen behavior like this it's caused by a firewall/AV/application that is monitoring keep-alive connections and occasionally shutting them down or interfering with them.

Do you have other machines at this location with the same problem?

Thanks for letting us know.  This is a known issue with 20.13 and should be fixed soon.  Unfortunately I don't have an exact ETA on when a fix will be found and implemented but we realize the high impact and thus it is a high priority.

Thanks for letting us know, we have received several reports and are investigating.

Can you post the last 100 lines or so from /var/log/screenconnect ?

Also, what Linux OS is on the server?

Thanks for the report, I just wanted to let you know that we have replicated the issue and it has been registered as a defect.

While I cannot provide an exact ETA on when a fix will be implemented, we are working towards it.

Thanks for the report, this issue has been replicated and registered as a defect.

following up, how many and/or which extensions do you have installed (if any)?

if you can just kick out a ls -alh for /opt/screenconnect/App_Extensions, that would be great

Actually, strike that previous reply, I was able to replicate this issue and it has been registered as a defect.

Thanks for the report!