<?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 Splunk Cloud Free Trial: certificate verify failed (self signed certificate in certificate chain) error message in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunk-Cloud-Free-Trial-certificate-verify-failed-self-signed/m-p/542608#M12129</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am evaluating Splunk Cloud (Free Trial for now) and running into the problem while submitting logs to HEC:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate in certificate chain) (OpenSSL::SSL::SSLError)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a Ruby on Rails application configured to use HTTPS HEC endpoint and using a self-signed certificate.&amp;nbsp; Everything works normally when SSL verification mode set to &lt;STRONG&gt;none&lt;/STRONG&gt;. The certificate is good since I could use it to establish an HTTPS connection to some other non-splunk endpoints. So I guess something on Splunk side rejecting self-signed certificates. Unfortunately, I cannot find any Splunk UI to manage this behavior, probably because it is a Free Trial. So my questions are: am I am missing some settings in UI? Or it is configurable in non Trial mode? Or it just requires a non-self-signed certificate?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Fri, 05 Mar 2021 17:19:35 GMT</pubDate>
    <dc:creator>afsku</dc:creator>
    <dc:date>2021-03-05T17:19:35Z</dc:date>
    <item>
      <title>Splunk Cloud Free Trial: certificate verify failed (self signed certificate in certificate chain) error message</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Cloud-Free-Trial-certificate-verify-failed-self-signed/m-p/542608#M12129</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am evaluating Splunk Cloud (Free Trial for now) and running into the problem while submitting logs to HEC:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate in certificate chain) (OpenSSL::SSL::SSLError)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a Ruby on Rails application configured to use HTTPS HEC endpoint and using a self-signed certificate.&amp;nbsp; Everything works normally when SSL verification mode set to &lt;STRONG&gt;none&lt;/STRONG&gt;. The certificate is good since I could use it to establish an HTTPS connection to some other non-splunk endpoints. So I guess something on Splunk side rejecting self-signed certificates. Unfortunately, I cannot find any Splunk UI to manage this behavior, probably because it is a Free Trial. So my questions are: am I am missing some settings in UI? Or it is configurable in non Trial mode? Or it just requires a non-self-signed certificate?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 17:19:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Cloud-Free-Trial-certificate-verify-failed-self-signed/m-p/542608#M12129</guid>
      <dc:creator>afsku</dc:creator>
      <dc:date>2021-03-05T17:19:35Z</dc:date>
    </item>
  </channel>
</rss>

