search for: bad_certificate

I have Xen 3.1 installed on my server, and XenSource Xen Server Console 3.1 on my windows desktop. When i trying to connect to the server with client, it says javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate Can anyone tell me, what can be a reason for bad_certificate? Where can i find it on my server and how can i check if it''s valid? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...es and private keys, but couldn't find any. So my solution will be to use certbot instead of dehydrated... :-/ Worst thing is, that a Microsoft Blog article (https://blogs.msdn.microsoft.com/kaushal/2012/10/05/ssltls-alert-protocol-the-alert-codes/) led me to the right direction.... ;-) -- 42 bad_certificate "There is a problem with the certificate, for example, a certificate is corrupt, or a certificate contains signatures that cannot be verified." -- Peace Bastian Am 17.02.2017 um 21:58 schrieb Aki Tuomi: > Usually with LE, the filename is fullchain.pem, not chain.pem. > > Can y...

Hey Robert, thanks for your reply. Am 17.02.2017 um 19:28 schrieb Robert L Mathews: > Looking at your dovecot -n, you're using two different files here: > > ssl_cert = </etc/ssl/sebode-online.de/chain.pem > ssl_key = </etc/ssl/sebode-online.de/key.pem > > Are you sure these two files match, and contain the right things in the > right order? > Yes,