You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everything seems fine log says: Using default TLS 1.0 security protocol.
The problem is, that as soon as a client tries to connect an exception is thrown: System.ComponentModel.Win32Exception (0x8009030E): No credentials available in the security package.
I use .NET 5.0, is there any known fix for this?
The text was updated successfully, but these errors were encountered:
Yes that fixed it indeed. I wonder if there is a way to make it work with .pem certificates, because i use Certbot to autoamtically recreate the certificates for my domain and now i have to manually convert it to a pfx cert each time a new certificate is generated.
I try to use SSL for my WebSocket connection and therefore i use this setup:
Everything seems fine log says:
Using default TLS 1.0 security protocol.
The problem is, that as soon as a client tries to connect an exception is thrown:
System.ComponentModel.Win32Exception (0x8009030E): No credentials available in the security package.
I use .NET 5.0, is there any known fix for this?
The text was updated successfully, but these errors were encountered: