Getting Data In

How to fix "ERROR TcpInputConfig - SSL context not found" when using inputs.conf [tcp-ssl://6514]?

simpkins1958
Contributor

Getting error: "TcpInputConfig - SSL context not found" when inputs.conf in etc/system/local has:

[tcp-ssl://6514]
connection_host = dns
sourcetype = syslog
disabled=0

What must be done to fix this error?

jworthington_sp
Splunk Employee
Splunk Employee
0 Karma

simpkins1958
Contributor

Needed to add the SSL stanza to inputs.conf. Now sending syslog data to splunk over TLS/SSL.

[tcp-ssl://6514]
connection_host = dns
sourcetype = syslog
disabled = 0

[SSL]
rootCA = $SPLUNK_HOME/etc/auth/cacert.pem
serverCert = $SPLUNK_HOME/etc/auth/server.pem
password = $1$B3HE+YB7UQbp

jbuckner85
Path Finder

Thanks, this fixed my problem when updating my inputs.conf. I was also missing the SSL stanza.

0 Karma

simpkins1958
Contributor

This blog was helpful in figuring out how to use Splunk certs for syslog over TCP-SSL.

https://wiki.splunk.com/Community:Splunk2Splunk_SSL_DefaultCerts

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!

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...