Quantcast
Channel: Questions in topic: "ssl"
Viewing all articles
Browse latest Browse all 425

After upgrading to 6.4, why are our signed certs no longer accepted in server.conf?

$
0
0
After upgrading the to 6.4, Splunk web would no longer start:> Starting splunk server daemon (splunkd)> ... Done [ OK ]> Waiting for web server at https://127.0.0.1:8443 to be available....> WARNING: web interface does not seem to be available! I thought it was an issue with the web.conf, so I ripped that out and it still would not start. I then removed the SSL setting in the server.conf and the server started normally. I re-added the web.conf and it again restarted fine. It is a Comodo cert (with their weird chain). The certificate works find in the web interface. We use the same for both. I though maybe it wanted a password on the key file, so I added one, that did not help. Looking at splunkd.log I see: 05-17-2016 14:06:42.214 -0400 ERROR X509 - /opt/splunk/etc/auth/MYSERVER-01.key: unable to read X509 certificate file 05-17-2016 14:06:45.156 -0400 ERROR SSLCommon - Can't read key file /opt/splunk/etc/auth/MYSERVER-01.key errno=185073780 error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch. When the certificate is configured with the web interface, it passes all the verification checks.

Viewing all articles
Browse latest Browse all 425

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>