<?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: Splunk Forwarder SSL error - &amp;quot;SSL23_GET_CLIENT_HELLO:unknown protocol&amp;quot; in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180456#M36197</link>
    <description>&lt;P&gt;I was getting this error when my inputs and outputs conf had encrypted sslPassword but I've forgotten to include the $SPLUNK_HOME/etc/auth/splunk.secret.&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jun 2016 15:33:19 GMT</pubDate>
    <dc:creator>bbialek</dc:creator>
    <dc:date>2016-06-23T15:33:19Z</dc:date>
    <item>
      <title>Splunk Forwarder SSL error - "SSL23_GET_CLIENT_HELLO:unknown protocol"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180451#M36192</link>
      <description>&lt;P&gt;I just installed two new UFs (v5.0.9, identical to the indexer they are trying to communicate with).  Despite picking up their configs from the deployment server and trying to direct their traffic to the correct indexer, &lt;CODE&gt;tcpdump&lt;/CODE&gt; indicates some very short handshakes, and &lt;CODE&gt;$SPLUNK_HOME/var/log/splunk/splunkd.log&lt;/CODE&gt; on each forwarder shows pairs of errors&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;INFO  TcpOutputProc - Connected to idx={indexerip}:9997
ERROR TcpOutputFd - Read error. Connection reset by peer
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;whilst the log on the indexer contains a stream of corresponding errors similar to &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ERROR TcpInputProc - Error encountered for connection from src={forwarderip}:43479. error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I already found &lt;EM&gt;&lt;A href="http://answers.splunk.com/answers/131861/universal-forwarders-no-longer-sending-data-ssl23-unknown-protocol"&gt;Universal forwarders no longer sending data - SSL23 unknown&lt;/A&gt;&lt;/EM&gt; which poses the question of whether the OpenSSL binaries have been relinked.  They have &lt;EM&gt;not&lt;/EM&gt;, and the binaries reported as embedded within Splunk are identical.&lt;/P&gt;

&lt;P&gt;I'm looking for ideas of what gives.  This is not a problem I have ever faced before after a simple UF install.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Aug 2014 13:43:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180451#M36192</guid>
      <dc:creator>grijhwani</dc:creator>
      <dc:date>2014-08-13T13:43:15Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Forwarder SSL error - "SSL23_GET_CLIENT_HELLO:unknown protocol"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180452#M36193</link>
      <description>&lt;P&gt;It turns out it wasn't just the new forwarder, it was quite a few, and it was a simple mistake.  The indexers are expecting compressed SSL traffic, and I had not set the SSL config.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Aug 2014 01:52:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180452#M36193</guid>
      <dc:creator>grijhwani</dc:creator>
      <dc:date>2014-08-14T01:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Forwarder SSL error - "SSL23_GET_CLIENT_HELLO:unknown protocol"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180453#M36194</link>
      <description>&lt;P&gt;What do you mean you had not set the SSL config? I am seeing this same thing. The funny thing is, the forwarder was working fine and all of a sudden stopped and I see the exact error you describe for it in my indexer's splunkd.log.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Oct 2014 18:14:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180453#M36194</guid>
      <dc:creator>wrangler2x</dc:creator>
      <dc:date>2014-10-13T18:14:48Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Forwarder SSL error - "SSL23_GET_CLIENT_HELLO:unknown protocol"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180454#M36195</link>
      <description>&lt;P&gt;What was the solution here, had you just not set "compression = true" on the forwarders?&lt;/P&gt;

&lt;P&gt;I just did that on my search head because I was getting the same error that my indexer wasn't receiving from the search head, but adding the compression setting to the outputs.conf on the SH didn't fix the problem.  This was working for me on 6.2.1 before the 6.2.2 upgrade.  After running the 6.2.2 upgrade, I get this error.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Mar 2015 15:17:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180454#M36195</guid>
      <dc:creator>DaClyde</dc:creator>
      <dc:date>2015-03-17T15:17:50Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Forwarder SSL error - "SSL23_GET_CLIENT_HELLO:unknown protocol"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180455#M36196</link>
      <description>&lt;P&gt;I don't fully recall, but the UF's were configured by script, initially, and I think the ssl configuration was quite simply just missing in its totality.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;~splunk/etc/system/local/server.conf&lt;/CODE&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sslConfig]
enableSplunkdSSL = true
useClientSSLCompression = true
useSplunkdClientSSLCompression = true
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 07 Sep 2015 16:20:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180455#M36196</guid>
      <dc:creator>grijhwani</dc:creator>
      <dc:date>2015-09-07T16:20:51Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Forwarder SSL error - "SSL23_GET_CLIENT_HELLO:unknown protocol"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180456#M36197</link>
      <description>&lt;P&gt;I was getting this error when my inputs and outputs conf had encrypted sslPassword but I've forgotten to include the $SPLUNK_HOME/etc/auth/splunk.secret.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2016 15:33:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Forwarder-SSL-error-quot-SSL23-GET-CLIENT-HELLO-unknown/m-p/180456#M36197</guid>
      <dc:creator>bbialek</dc:creator>
      <dc:date>2016-06-23T15:33:19Z</dc:date>
    </item>
  </channel>
</rss>

