Security

Using custom SSL Certificates with the Management Port causes splunkweb and the management port to be unresponsive

brandonmosherx
New Member

Splunk 6.4.1

Ways I've approached this and it hasn't been successful:

  • Using the same certificate as the SplunkWeb SSL certificate (splunkweb works on it's own with the SSL certificate being successful.)
  • Using a different certificate than the SplunkWeb SSL certificate (without a password)
  • Using a different certificate with a password, and configuring the server.conf to utilise that password

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.)

Any ideas on what the problem might be, or if it's related to the current Splunk version?

Thanks!

0 Karma

yongchien
New Member

Hi I'm having the same problem as well, anyone here care to shed some lights? Thanks

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Rounding off the Splunk Dashboard Contest

What does a contest-winning Splunk dashboard look like? In this case, it isn't in a browser tab at all. It ...

A Four Part Event Series: AI + Observability: AI Agents, LLMs, Apps, & Infrastructure

AI + Observability: AI Agents, LLMs, Apps, & Infrastructure The rapid evolution of artificial intelligence ...