SSL Windows 10 1903

My first post asking for assistance, I hope I have everything needed.
Sonarr version
Windows 10 1903
19-7-7 21:31:09.2|Debug|netsh.exe|Starting netsh.exe http show sslcert ipport=
19-7-7 21:31:09.3|Debug|netsh.exe|SSL Certificate bindings:
19-7-7 21:31:09.3|Debug|netsh.exe|-------------------------
19-7-7 21:31:09.3|Debug|netsh.exe|The system cannot find the file specified.
19-7-7 21:31:09.3|Debug|netsh.exe|Starting netsh.exe http add sslcert ipport= certhash=************ appid={C2172AF4-F9A6-4D91-BAEE-C2E4EE680613}
19-7-7 21:31:09.4|Debug|netsh.exe|SSL Certificate add failed, Error: 1312
19-7-7 21:31:09.4|Debug|netsh.exe|A specified logon session does not exist. It may already have been terminated.
19-7-7 21:31:09.4|Debug|netsh.exe|Starting netsh.exe http show urlacl
19-7-7 21:31:09.5|Debug|netsh.exe|URL Reservations:
19-7-7 21:31:09.5|Debug|netsh.exe|----------------- **:

I am switching Sonarr from Windows 10 1809 to different machine running Windows 10 1903. It seems that Sonarr is not binding the certificate to the port. I am not able to connect https on my custom port using my custom cert when installed on Windows 10 1903. Based on googling the above logs and attempting to manually runt he commands on Windows 10 1903, I end up with the following same errors.

C:\Windows\system32>netsh http show sslcert
SSL Certificate bindings:

C:\Windows\system32>netsh http show sslcert
SSL Certificate bindings:

C:\Windows\system32>netsh.exe http add sslcert ipport= certhash=748bfc47e2f1c051efe9149977410f7db445420c appid={C2172AF4-F9A6-4D91-BAEE-C2E4EE680613}

SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.

Windows 10 1809:
C:\Windows\system32>netsh http show sslcert

SSL Certificate bindings:

IP:port                      :
Certificate Hash             : 7*************************************c
Application ID               : {c2172af4-f9a6-4d91-baee-c2e4ee680613}
Certificate Store Name       : (null)
Verify Client Certificate Revocation : Enabled
Verify Revocation Using Cached Client Certificate Only : Disabled
Usage Check                  : Enabled
Revocation Freshness Time    : 0
URL Retrieval Timeout        : 0
Ctl Identifier               : (null)
Ctl Store Name               : (null)
DS Mapper Usage              : Disabled
Negotiate Client Certificate : Disabled
Reject Connections           : Disabled
Disable HTTP2                : Not Set
Disable QUIC                 : Not Set
Disable TLS1.2               : Not Set
Disable TLS1.3               : Not Set
Disable OCSP Stapling        : Not Set
Disable Legacy TLS Versions  : Not Set

I posted two sets of debug logs on GDrive, one set is labeled 1903.sonarr.debug.txt and the other set is labled 1809.

I am not sure what steps I might be able to take next to bind the certificates. The are 2 differences i notice is that Windows 10 1903 has .net 4.8 while 1809 is still 4.7. The other difference was the CERT Chains are different between my initial 1809 and 1903. However when spining up a couple of VM Workstations of 1809 and 1903 with the same experienced the exact results using default ports. The cert chains were both the same matching each other 1809 and 1903. So I do not believe that to be the issue.

I figured out my issue, I imported the crt instead of the PFX. DUH Moment and I am not able to delete my original post.

Please don’t :slight_smile:
This may help someone who has the same issue in the future…

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.