it’s not a mistake Screenconnect was sold since then the product has gone down the pan .

software is not what it used to be everything is subscription.. it won’t be long before the masses start writing software for their own use again 

Thanks for the Mesh Central info... just in case Control Wise no longer want us ...???

Since Jeff Sold SC I personally have found keeping my on premises a real pain.

NGINX config file ...web server working  ..  need to get relay working on port 443  so it will work on more firewalls as business routers will most likely block port 8041 which is the relay port fro screenconnect 

server {
listen 80;
listen [::]:80;
server_name example.co.uk www.example.co.uk relay.example.co.uk sc.example.co.uk;

location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;localhost
proxy_set_header X-NginX-Proxy true;
proxy_pass http://localhost:8040;
proxy_redirect off;
}
}

server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name example.co.uk www.example.co.uk sc.example.co.uk;

ssl_certificate /etc/letsencrypt/live/example.co.uk/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.co.uk/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
proxy_pass http://localhost:8040;
proxy_redirect off;
}
}

server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name relay.example.co.uk;

ssl_certificate /etc/letsencrypt/live/example.co.uk/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.co.uk/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
proxy_pass http://localhost:8041;
proxy_redirect off;
}
}

on Prem  Screenconnect using   Linux  Nginx  Lets Encrypt ... 

Nginx  as web proxy, Lets Encypt pretty straight forward using the certbot see https://www.nginx.com/blog/using-free-ssltls-certificates-from-lets-encrypt-with-nginx/