<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: TCP-SSL ERROR SSL context not found. Splunk not listening the configured port. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/TCP-SSL-ERROR-SSL-context-not-found-Splunk-not-listening-the/m-p/660017#M111607</link>
    <description>&lt;P&gt;A couple steps to troubleshoot:&lt;BR /&gt;&lt;BR /&gt;- If you remove the SSL, can you get Splunk to startup and listen on that port?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Are your paths 100% correct - this could be related to a typo in the path/filename.&lt;/P&gt;&lt;P&gt;- Do your certificates have the correct permissions so Spunk can see them?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a side note, Splunk will auto-encrypt passwords like that in your .conf files. You'll see the following wording for values it does this with in the documentation (e.g. &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf" target="_self"&gt;inputs.conf sslPassword&lt;/A&gt; documentation)&lt;/P&gt;&lt;PRE&gt;Upon first use, the input encrypts and rewrites the password&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 06 Oct 2023 16:59:28 GMT</pubDate>
    <dc:creator>_JP</dc:creator>
    <dc:date>2023-10-06T16:59:28Z</dc:date>
    <item>
      <title>TCP-SSL ERROR SSL context not found. Splunk not listening the configured port.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-SSL-ERROR-SSL-context-not-found-Splunk-not-listening-the/m-p/659625#M111568</link>
      <description>&lt;P&gt;Hey All &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I've configured tcp-ssl on HF, created certificates and the following configuration.&lt;BR /&gt;The HF receive syslog from third-party, I'll send the third party company the CA (combined certificat) I created based on these docs:&lt;BR /&gt;1.&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.1.1/Security/Howtoself-signcertificates" target="_self"&gt;How to create and sign your own TLS certificates&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;2.&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.1.1/Security/HowtoprepareyoursignedcertificatesforSplunk" target="_self"&gt;Create a single combined certificate file&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;inputs.conf&lt;BR /&gt;&lt;/U&gt;&lt;/STRONG&gt;[tcp-ssl://2222]&lt;BR /&gt;index = test&lt;BR /&gt;sourcetype = st_test&lt;/P&gt;&lt;P&gt;[SSL]&lt;BR /&gt;serverCert = C:\Program Files\Splunk\etc\auth\mycerts\myServerCertificate.pem&lt;BR /&gt;sslPassword = &amp;lt;Server.key password&amp;gt;&lt;BR /&gt;sslRootCAPath = C:\Program Files\Splunk\etc\auth\mycerts\myCertAuthCertificate.pem&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;&lt;STRONG&gt;Server.conf&lt;/STRONG&gt;&lt;/U&gt;&lt;BR /&gt;[sslconfig]&lt;BR /&gt;sslPassword = &amp;lt;password encrypted that I didn't configured&amp;gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;And yet Splunk isn't listening to the requested port for example 2222&lt;/P&gt;&lt;P&gt;What am I missing?&lt;/P&gt;&lt;P&gt;The error I get in Splunk _internal is:&lt;BR /&gt;&lt;SPAN&gt;SSL context not found. Will not open raw (SSL) IPv4 port 2222&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please assist, and Thank YOU!!!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2023 09:28:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-SSL-ERROR-SSL-context-not-found-Splunk-not-listening-the/m-p/659625#M111568</guid>
      <dc:creator>hketer</dc:creator>
      <dc:date>2023-10-04T09:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: TCP-SSL ERROR SSL context not found. Splunk not listening the configured port.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-SSL-ERROR-SSL-context-not-found-Splunk-not-listening-the/m-p/660017#M111607</link>
      <description>&lt;P&gt;A couple steps to troubleshoot:&lt;BR /&gt;&lt;BR /&gt;- If you remove the SSL, can you get Splunk to startup and listen on that port?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Are your paths 100% correct - this could be related to a typo in the path/filename.&lt;/P&gt;&lt;P&gt;- Do your certificates have the correct permissions so Spunk can see them?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a side note, Splunk will auto-encrypt passwords like that in your .conf files. You'll see the following wording for values it does this with in the documentation (e.g. &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf" target="_self"&gt;inputs.conf sslPassword&lt;/A&gt; documentation)&lt;/P&gt;&lt;PRE&gt;Upon first use, the input encrypts and rewrites the password&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2023 16:59:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-SSL-ERROR-SSL-context-not-found-Splunk-not-listening-the/m-p/660017#M111607</guid>
      <dc:creator>_JP</dc:creator>
      <dc:date>2023-10-06T16:59:28Z</dc:date>
    </item>
    <item>
      <title>Re: TCP-SSL ERROR SSL context not found. Splunk not listening the configured port.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-SSL-ERROR-SSL-context-not-found-Splunk-not-listening-the/m-p/660022#M111610</link>
      <description>&lt;P&gt;Check logs more "backwards" to see earlier errors. Maybe you mistyped file paths, maybe the password was wrong...&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2023 17:31:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-SSL-ERROR-SSL-context-not-found-Splunk-not-listening-the/m-p/660022#M111610</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-10-06T17:31:06Z</dc:date>
    </item>
  </channel>
</rss>

