Security

Port issue with splunkd SSL

irsysintegratio
Path Finder

Hello,

We want to enable Splunkd SSL, so we put
enableSplunkdSSL = true
to server.conf.
We generated a certificate using the FQDN as the CN of the certificate.

Then in our AddOn, we use splunk.getLocalServerInfo() to get the url:port. The problem is that splunk.getLocalServerInfo() always returns https://127.0.0.1:8089, even if we changed MgmtHostPort in web.conf. As a result, we always get an error:
SSLError: hostname '127.0.0.1' doesn't match xxxxxx, where xxxxxx is the CN we set for the certificate.

So how shall this work? Shall we use 127.0.0.1 as the CN to create a cert? Or we shall not call getLocalServerInfo()?

Thanks!

0 Karma
1 Solution

irsysintegratio
Path Finder

Ok, answering my own question. One way to contribute. 🙂

Need to set the following env var:
SPLUNKD_URI
to the FQDN of your machine. Then it will work.

View solution in original post

0 Karma

irsysintegratio
Path Finder

Ok, answering my own question. One way to contribute. 🙂

Need to set the following env var:
SPLUNKD_URI
to the FQDN of your machine. Then it will work.

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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...