https://community.splunk.com/t5/Security/Using-custom-SSL-Certificates-with-the-Management-Port-causes/m-p/235387#M6607 <P>Hi I'm having the same problem as well, anyone here care to shed some lights? Thanks</P> Thu, 18 May 2017 03:07:00 GMT yongchien 2017-05-18T03:07:00Z https://community.splunk.com/t5/Security/Using-custom-SSL-Certificates-with-the-Management-Port-causes/m-p/235386#M6606 <P>Splunk 6.4.1</P> <P>Ways I've approached this and it hasn't been successful:</P> <UL> <LI>Using the same certificate as the SplunkWeb SSL certificate (splunkweb works on it's own with the SSL certificate being successful.)</LI> <LI>Using a different certificate than the SplunkWeb SSL certificate (without a password)</LI> <LI>Using a different certificate with a password, and configuring the server.conf to utilise that password</LI> </UL> <P>The moment that I configure the server.conf to not utilise the certificates I've created, splunkweb goes back to normal after I restart. And I can access the management port as well (even though the default certificates are invalid in the first place.)</P> <P>Any ideas on what the problem might be, or if it's related to the current Splunk version?</P> <P>Thanks!</P> Thu, 30 Jun 2016 11:35:34 GMT https://community.splunk.com/t5/Security/Using-custom-SSL-Certificates-with-the-Management-Port-causes/m-p/235386#M6606 brandonmosherx 2016-06-30T11:35:34Z https://community.splunk.com/t5/Security/Using-custom-SSL-Certificates-with-the-Management-Port-causes/m-p/235387#M6607 <P>Hi I'm having the same problem as well, anyone here care to shed some lights? Thanks</P> Thu, 18 May 2017 03:07:00 GMT https://community.splunk.com/t5/Security/Using-custom-SSL-Certificates-with-the-Management-Port-causes/m-p/235387#M6607 yongchien 2017-05-18T03:07:00Z