<?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 How to resolve SSL error with tcp-ssl input? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-SSL-error-with-tcp-ssl-input/m-p/539329#M90355</link>
    <description>&lt;P&gt;I have a Splunk server which is receiving data on a tcp-ssl port successfully for a particular application (SecureCircle). I'm trying to set up a new port to receive data from Palo Alto firewalls but it's running into an the following error:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;WARN  SSLCommon - Received fatal SSL3 alert. ssl_state='SSLv3 read client key exchange A', alert_description='certificate unknown'&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm using the same certificate an SSL configuration for both ports so I know that the cert is fine. It's not a self singed cert. It's valid until 2022.&lt;/P&gt;
&lt;P&gt;I've been looking through some old posts with similar errors but none of them seemed to match my issue.&amp;nbsp; Below is my Port and SSL configuration from the btool inputs command&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              [SSL]
/opt/splunk/etc/system/default/inputs.conf                             _rcvbuf = 1572864
/opt/splunk/etc/system/default/inputs.conf                             allowSslRenegotiation = true
/opt/splunk/etc/system/default/inputs.conf                             cipherSuite = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256
/opt/splunk/etc/system/default/inputs.conf                             ecdhCurves = prime256v1, secp384r1, secp521r1
/opt/splunk/etc/system/local/inputs.conf                               host = splunkhost.mydomain.com
/opt/splunk/etc/system/default/inputs.conf                             index = default
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              requireClientCert = false
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              serverCert = /opt/splunk/etc/auth/splunkhost.mydomain.com/splunkhost.mydomain.com.pem
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              sslPassword = [Redacted]
/opt/splunk/etc/system/default/inputs.conf                             sslQuietShutdown = false
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              sslVersions = tls1.2&lt;/LI-CODE&gt;&lt;LI-CODE lang="markup"&gt;/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              [tcp-ssl://6514]
/opt/splunk/etc/system/default/inputs.conf                             _rcvbuf = 1572864
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              host = splunkhost.mydomain.com
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              index = pan_logs
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              sourcetype = pan:log&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The configuration for the working port is:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;/opt/splunk/etc/apps/ahs_ta_securecircle/local/inputs.conf             [tcp-ssl://8443]
/opt/splunk/etc/system/default/inputs.conf                             _rcvbuf = 1572864
/opt/splunk/etc/system/local/inputs.conf                               host = splunkhost.mydomain.com
/opt/splunk/etc/apps/ahs_ta_securecircle/local/inputs.conf             index = dlp
/opt/splunk/etc/apps/ahs_ta_securecircle/local/inputs.conf             sourcetype = SecureCircle&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Jan 2023 16:10:27 GMT</pubDate>
    <dc:creator>roberteves</dc:creator>
    <dc:date>2023-01-11T16:10:27Z</dc:date>
    <item>
      <title>How to resolve SSL error with tcp-ssl input?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-SSL-error-with-tcp-ssl-input/m-p/539329#M90355</link>
      <description>&lt;P&gt;I have a Splunk server which is receiving data on a tcp-ssl port successfully for a particular application (SecureCircle). I'm trying to set up a new port to receive data from Palo Alto firewalls but it's running into an the following error:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;WARN  SSLCommon - Received fatal SSL3 alert. ssl_state='SSLv3 read client key exchange A', alert_description='certificate unknown'&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm using the same certificate an SSL configuration for both ports so I know that the cert is fine. It's not a self singed cert. It's valid until 2022.&lt;/P&gt;
&lt;P&gt;I've been looking through some old posts with similar errors but none of them seemed to match my issue.&amp;nbsp; Below is my Port and SSL configuration from the btool inputs command&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              [SSL]
/opt/splunk/etc/system/default/inputs.conf                             _rcvbuf = 1572864
/opt/splunk/etc/system/default/inputs.conf                             allowSslRenegotiation = true
/opt/splunk/etc/system/default/inputs.conf                             cipherSuite = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256
/opt/splunk/etc/system/default/inputs.conf                             ecdhCurves = prime256v1, secp384r1, secp521r1
/opt/splunk/etc/system/local/inputs.conf                               host = splunkhost.mydomain.com
/opt/splunk/etc/system/default/inputs.conf                             index = default
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              requireClientCert = false
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              serverCert = /opt/splunk/etc/auth/splunkhost.mydomain.com/splunkhost.mydomain.com.pem
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              sslPassword = [Redacted]
/opt/splunk/etc/system/default/inputs.conf                             sslQuietShutdown = false
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              sslVersions = tls1.2&lt;/LI-CODE&gt;&lt;LI-CODE lang="markup"&gt;/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              [tcp-ssl://6514]
/opt/splunk/etc/system/default/inputs.conf                             _rcvbuf = 1572864
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              host = splunkhost.mydomain.com
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              index = pan_logs
/opt/splunk/etc/apps/Splunk_TA_paloalto/local/inputs.conf              sourcetype = pan:log&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The configuration for the working port is:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;/opt/splunk/etc/apps/ahs_ta_securecircle/local/inputs.conf             [tcp-ssl://8443]
/opt/splunk/etc/system/default/inputs.conf                             _rcvbuf = 1572864
/opt/splunk/etc/system/local/inputs.conf                               host = splunkhost.mydomain.com
/opt/splunk/etc/apps/ahs_ta_securecircle/local/inputs.conf             index = dlp
/opt/splunk/etc/apps/ahs_ta_securecircle/local/inputs.conf             sourcetype = SecureCircle&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2023 16:10:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-SSL-error-with-tcp-ssl-input/m-p/539329#M90355</guid>
      <dc:creator>roberteves</dc:creator>
      <dc:date>2023-01-11T16:10:27Z</dc:date>
    </item>
    <item>
      <title>Re: SSL error with tcp-ssl input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-SSL-error-with-tcp-ssl-input/m-p/626725#M107638</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;having the exact same issue. Were you able to fix it?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2023 08:31:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-SSL-error-with-tcp-ssl-input/m-p/626725#M107638</guid>
      <dc:creator>FlorianScho</dc:creator>
      <dc:date>2023-01-11T08:31:39Z</dc:date>
    </item>
    <item>
      <title>Re: SSL error with tcp-ssl input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-SSL-error-with-tcp-ssl-input/m-p/635782#M108762</link>
      <description>&lt;P&gt;Ditto here.&lt;/P&gt;&lt;P&gt;I hammered on it for about a day, and finally just went back to udp.&lt;/P&gt;&lt;P&gt;I may just have to configure a vpn tunnel to send it through as a work around, sad.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 19:22:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-SSL-error-with-tcp-ssl-input/m-p/635782#M108762</guid>
      <dc:creator>kdulle</dc:creator>
      <dc:date>2023-03-23T19:22:26Z</dc:date>
    </item>
  </channel>
</rss>

