SSL issue on 11.21 on Windows Server 2019

[mriffey]

I'm almost certain this is caused by something I've done wrong, but I haven't found it yet, so I'll post this here so it will come to me seconds after I click "POST"

I am getting these errors when trying to connect to a HTTPS (LE certificate) NTWS server. The certificate validates fine, the name is correct and the pages not secured by login serve ok, but I see these log entries (below) on every browse attempt. When I attempt to use the login form (which is in out of the box form for testing), I get these errors and the login never succeeds - in fact, ODS displays give the impression that the validateupdate embed in the login form never gets control.

[NetDLL] [2] SimpleServer_Async - ReadData() :  rd1
[NetDLL] [2] SimpleServer_Async - ReadData() :  rd2
[NetDLL] [2] SSL_Our_ServerRead() : SSL Error calling SSL_Read : SSL_ERROR_SYSCALL [] Some I/O error occurred. SSL Error Code = 5
[NetDLL] [2] SimpleServer_Async - ReadData() :  rd3 loc:SSLErrorNumber=0
[NetDLL] [2] SimpleServer_Async - ReadData() : SimpleServer_Async loc:ret (A) = 0 loc:rc=-75
[NetDLL] [2] SimpleServer_Async - ReadData() : SimpleServer_Async loc:ret (B) = 0
[NetDLL] [2] NetErrorStr() : Error (0) = General Winsock Error (unknown by NetErrorStr)

[NetDLL] [2] SimpleServer_Async - Do Read() : Error trying to read Data from Socket. (loc:rc = -75) Error = 0 => General Winsock Error (unknown by NetErrorStr)

[NetDLL] [2] SimpleServer_Async - ReadData() : Nothing to read. Could not read.
[NetDLL] [2] SimpleServer_Async() : ReadCount = 0
[NetDLL] [2] SimpleServer_Async() : Calling CloseSocket on socket=1228
[NetDLL] [2] SimpleCloseSocket - Graceful Close() : Calling SetSockOpt. Linger = 1 3
[NetDLL] [2] SimpleCloseSocket() : p_lpSSL start
[NetDLL] [2] SSL_Our_Close() : Before SSL_Shutdown 13053232
[NetDLL] [2] SSL_Our_Close() : Result (SSL_Shutdown) = -1
[NetDLL] [2] SSL_Our_Close() : Before SSL_Free 13053232
[NetDLL] [2] SSL_Our_Close() :  After SSL_Free

[mriffey]

No progress on this. I installed everything on a Server 2016 system to make sure it wasnt an oddity about 2019 - same issue, so Im still thinking I did something weird.

[Alberto]

Hi, be sure to, in the first time, request the cert using port 80

[mriffey]

The cert is correct. That part worked fine. What fails is when you actually try to browse to the site and login.

[Matthew51]

Double check everything in the Deploying a TLS Client or Server list

Failing that I think you would need Bruce to look at this.

[DonRidley]

Did you remember to install the MS Visual Studio runtimes?

https://aka.ms/vs/16/release/vc_redist.x86.exe

Is your certificates path correct?

Don