Your comments

debian jessie here and having exactly the same experience. in the last let say six month I upgraded my install at least 10 times with different version just revert back to the working 19.4

I tried 20.2 for two days, it was fast, didn't need any web.conf modification to work with nginx proxy /just had to comment out the host line/ but after some time it slowed down, for some reason the mono processes started to consume the cpu. The symptoms were the same as with the memory leak but htop showed a different kind of problem.

v19.4 was the last really stable version for me,

This might be the reason for the slowdown, I have hundreds of lines like these:

today I experienced a server slowdown again with 19.6, I didn’t had the time to investigate so I just went back to 19.5 if the problem comes back then I still have a backup of a perfectly working 19.4 install.

by the way the linux versions of 19.6 are gone from the download page.

great, the RelayAddressableUri line helped, thanks!  

yes, I removed it, first I tried the modified line but a result was the same

I know it’s strange. screenconnect is running on Debian 8 server with Plesk, these are the current nginx directives:


location ^~ / {

proxy_pass http://127.0.0.1:8040/;

proxy_redirect off;

proxy_set_header Host $host;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_max_temp_file_size 0;

client_max_body_size 50m;

client_body_buffer_size 256k;

proxy_connect_timeout 180;

proxy_send_timeout 180;

proxy_read_timeout 90;

proxy_buffer_size 16k;

proxy_buffers 4 64k;

proxy_busy_buffers_size 128k;


if I remove the proxy_set_header host line I can access the admin page but when I try to connect to a host it waits for a while and then I receive a refused connection error /ip: 127.0.0.1:8041/ . the problem is there with both the old and new client versions.


also version and browser url check gives me an error, with 19.4 only the external accessibility check wasn’t working


removing the proxy_set_header Host $host; line helped for me to access the admin page but I wasn't able to connect to the hosts, there was a connection error

19.5 is working for me but after a couple of days every interaction with the admin page takes more and more time, I see the loading icon a lot while there is no load on the server. I also use an iPad Pro and it’s even worse there, most of the time I can’t even access the admin page with the app. No problems with 19.4 though