Getting Data In

Indexers SSL Problem

liam78
New Member

Hi guys.

I'm trying to configure my two indexers to receive data with SSL.

My inputs.conf configuration is:

# BASE SETTINGS
# [Splunktcp: // 9997]
[Splunktcp-ssl: // 9997]

# SSL SETTINGS
[SSL]
rootCA = $SPLUNK_HOME / etc / apps / MY_all_certificates / certs / MY_CA.pem
serverCert = $SPLUNK_HOME / etc / apps / MY_all_certificates / certs / MY_host.pem
sslPassword = mypassword
requireClientCert = true
# If using compressed = true, it must be set on the forwarder outputs as well.
# compressed = true

But I get an error on Indexers in splunkd:

ERROR TcpInputConfig - SSL context cannot be created two required serverCert parameter from [SSL] room. Will not open splunk to splunk (SSL) IPv4 port 9997

The problem is that it does not specify what the parameter is.

Thanks.

0 Karma

hettervik
SplunkTrust
SplunkTrust

Did you ever found out what is causing this error? I've seem to have the same problem.

https://community.splunk.com/t5/Splunk-Enterprise/How-to-fix-quot-missing-serverCert-parameter-from-...

Surely I've sat the "serverCert" parameter in the SSL stanza, but nevertheless, Splunk doesn't seem to accept it.

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 Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...