CentOS Linux release 7.7.1908 (Core) 3.10.0-1062.9.1.el7.x86_64 #1 SMP. No nginx reverse proxy.
Xeon(R) E3-1270 v3 @ 3.50GHz w/32GB
netstat output when screenconnect running typically:
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 198.51.100.241:80 0.0.0.0:* LISTEN 29303/monotcp 0 0 198.51.100.157:80 0.0.0.0:* LISTEN 7677/httpd
As a test, stopped the service and restored old web.config in place of new web.config had same result. I agree that they could take a page out of Ubiquiti’s playbook. You’d think a release version would undergo testing of basic host headers. (i.e. real world scenarios) . Had been working with a rep on expanding the services I have from Connectwise... may hold off a bit longer now.
Not foreseeing any timely response here, I tried out the debug release 19.6.26188.7290 before pulling the trigger on a restore
Truncated output from install:
.….Running 'Transform configuration files'...
mono: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by mono)
mono: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by mono)
Running 'Start screenconnect service'...
Trying to figure out the best URL for you to use...
To access your new ScreenConnect installation, open a browser and navigate to:
(This space unintentionally left blank)
FAIL mode enabled.
Restored from backup version 19.4.25759, downloaded and reinstalled. Working fine again.
Will monitor this thread, as well as the changelog when a new release comes.
Same here. Thought i'd installed a beta release on accident. Page loads with IP fine. Error returned with hostname. configured as per web documentation in order to be functional with a multi-NIC box. I can't configure as one comment mentioned (+:80) because other NIC is listening for another service. Checked relevant lines before and after upgrade (from backup) and all seems intact. here are the relevant lines that I use. Next step is to compare line-by-line for discrepancies. Will e-mail the web.config files if needed.
Below domains and IPs have been replaced
<add key="WebServerAddressableUri" value=“http://help.example.com" />
<add key="WebServerListenUri" value=“http://198.51.100.241:80/" />
<add key="RelayAddressableUri" value=“relay://help.example.com:8041/“ />
<add key="RelayListenUri" value=“relay://198.51.100.241:8041/“ />
curl -v http://help.example.com* Trying 198.51.100.241...* TCP_NODELAY set* Connected to help.example.com (198.51.100.241) port 80 (#0)> GET / HTTP/1.1> Host: help.example.com> User-Agent: curl/7.64.1> Accept: */*>< HTTP/1.1 400 Bad Request< Content-Type: text/html; charset=utf-8< Server: Mono-HTTPAPI/1.0< Date: Thu, 26 Dec 2019 21:26:10 GMT< Content-Length: 35< Connection: close<* Closing connection 0
Customer support service by UserEcho