We have an existing Splunk 9.1.3 Enterprise environment and run Splunkweb at port 8000 using an outside CA signed certificate for https. A partner wants to stream syslog data to our Splunk using a secure connection. I added the following to inputs.conf located in system/local. [tcp-ssl:6514] sourcetype = syslog index=syslog disabled = 0 [SSL] privKeyPath = /opt/splunk/etc/auth/splunkweb/2024/splprkey.key serverCert = /opt/splunk/etc/auth/splunkweb/2024/prcert.pem requireClientCert = false After a restart ,I used openssl to test the connection. Port 8000 worked normally as expected; the certificate was returned and I could see the TLS negotiation in Wireshark The openssl connection to port 6154 did not work . A connection was made and openssl did send a "Client Hello" which was visible in Wireshark, but other than an ACK the Splunk server never sent anything further. Based on an article I read, I also copied the certificate path to the server.conf file, but that didn't change anything. What am I missing? Is it incorrect to assume the same cert could be used for different ports? Any assistance appreciated! Thanks,
... View more