<?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 curl (35) Unknown SSL protocol error in connection to .splunkcloud.com:8089 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303452#M57282</link>
    <description>&lt;P&gt;I'm following the &lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/6.6.3/RESTTUT/RESTbasicexamples"&gt;REST API tutorial&lt;/A&gt; with Splunk Cloud but receiving the error below.  Url, ip address, username, and password are sanitized.&lt;/P&gt;

&lt;P&gt;curl -v -k -u : &lt;A href="https://deployment-name.splunkcloud.com:8089/servicesNS//search/saved/searches/"&gt;https://deployment-name.splunkcloud.com:8089/servicesNS//search/saved/searches/&lt;/A&gt; -d name=mysearch -d search=*  &lt;/P&gt;

&lt;P&gt;* Hostname was NOT found in DNS cache  &lt;/P&gt;

&lt;P&gt;*   Trying ##.###.###.###...  &lt;/P&gt;

&lt;P&gt;* Connected to deployment-name.splunkcloud.com (##.###.###.###) port 8089 (#0)  &lt;/P&gt;

&lt;P&gt;* successfully set certificate verify locations:  &lt;/P&gt;

&lt;P&gt;*   CAfile: none  &lt;/P&gt;

&lt;P&gt;CApath: /etc/ssl/certs  &lt;/P&gt;

&lt;P&gt;* SSLv3, TLS handshake, Client hello (1):  &lt;/P&gt;

&lt;P&gt;* Unknown SSL protocol error in connection to deployment-name.splunkcloud.com:8089  &lt;/P&gt;

&lt;P&gt;* Closing connection 0  &lt;/P&gt;

&lt;P&gt;curl: (35) Unknown SSL protocol error in connection to deployment-name.splunkcloud.com:8089  &lt;/P&gt;</description>
    <pubDate>Wed, 11 Oct 2017 14:35:52 GMT</pubDate>
    <dc:creator>bschaap</dc:creator>
    <dc:date>2017-10-11T14:35:52Z</dc:date>
    <item>
      <title>curl (35) Unknown SSL protocol error in connection to .splunkcloud.com:8089</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303452#M57282</link>
      <description>&lt;P&gt;I'm following the &lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/6.6.3/RESTTUT/RESTbasicexamples"&gt;REST API tutorial&lt;/A&gt; with Splunk Cloud but receiving the error below.  Url, ip address, username, and password are sanitized.&lt;/P&gt;

&lt;P&gt;curl -v -k -u : &lt;A href="https://deployment-name.splunkcloud.com:8089/servicesNS//search/saved/searches/"&gt;https://deployment-name.splunkcloud.com:8089/servicesNS//search/saved/searches/&lt;/A&gt; -d name=mysearch -d search=*  &lt;/P&gt;

&lt;P&gt;* Hostname was NOT found in DNS cache  &lt;/P&gt;

&lt;P&gt;*   Trying ##.###.###.###...  &lt;/P&gt;

&lt;P&gt;* Connected to deployment-name.splunkcloud.com (##.###.###.###) port 8089 (#0)  &lt;/P&gt;

&lt;P&gt;* successfully set certificate verify locations:  &lt;/P&gt;

&lt;P&gt;*   CAfile: none  &lt;/P&gt;

&lt;P&gt;CApath: /etc/ssl/certs  &lt;/P&gt;

&lt;P&gt;* SSLv3, TLS handshake, Client hello (1):  &lt;/P&gt;

&lt;P&gt;* Unknown SSL protocol error in connection to deployment-name.splunkcloud.com:8089  &lt;/P&gt;

&lt;P&gt;* Closing connection 0  &lt;/P&gt;

&lt;P&gt;curl: (35) Unknown SSL protocol error in connection to deployment-name.splunkcloud.com:8089  &lt;/P&gt;</description>
      <pubDate>Wed, 11 Oct 2017 14:35:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303452#M57282</guid>
      <dc:creator>bschaap</dc:creator>
      <dc:date>2017-10-11T14:35:52Z</dc:date>
    </item>
    <item>
      <title>Re: curl (35) Unknown SSL protocol error in connection to .splunkcloud.com:8089</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303453#M57283</link>
      <description>&lt;P&gt;You are already using the insecure switch, can you confirm that curl has the available SSL libraries? Such as running against &lt;A href="https://google.com"&gt;https://google.com&lt;/A&gt; ?&lt;/P&gt;

&lt;P&gt;Also double check the curl --version ...&lt;/P&gt;</description>
      <pubDate>Wed, 11 Oct 2017 17:54:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303453#M57283</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2017-10-11T17:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: curl (35) Unknown SSL protocol error in connection to .splunkcloud.com:8089</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303454#M57284</link>
      <description>&lt;P&gt;It turns out that this was a firewall issue.  It didn't appear to be initially because the behavior was different when trying an invalid port instead of 8089.  Using an invalid port would wait for a timeout.  Port 8089 didn't timeout and instead returned the error message immediately.  Once the firewall was modified to allow port 8089 outbound then it began working.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Oct 2017 13:37:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303454#M57284</guid>
      <dc:creator>bschaap</dc:creator>
      <dc:date>2017-10-13T13:37:14Z</dc:date>
    </item>
    <item>
      <title>Re: curl (35) Unknown SSL protocol error in connection to .splunkcloud.com:8089</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303455#M57285</link>
      <description>&lt;P&gt;This turned out to be a firewall issue even though it did not appear to be initially.  See comments for more details.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Oct 2017 13:38:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303455#M57285</guid>
      <dc:creator>bschaap</dc:creator>
      <dc:date>2017-10-13T13:38:14Z</dc:date>
    </item>
    <item>
      <title>Re: curl (35) Unknown SSL protocol error in connection to .splunkcloud.com:8089</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303456#M57286</link>
      <description>&lt;P&gt;Like you I am using &lt;A href="https://notresponding.net/8-solution-steps-chrome-err_ssl_protocol_error/"&gt;ERR SSL PROTOCOL ERROR Not Responding&lt;/A&gt; site to get that error solution, and believe me I found the perfect solutions from that site and there is the number of problems described and their solution in the perfect manner.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Apr 2018 07:12:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/curl-35-Unknown-SSL-protocol-error-in-connection-to-splunkcloud/m-p/303456#M57286</guid>
      <dc:creator>Sobhiapetter</dc:creator>
      <dc:date>2018-04-05T07:12:52Z</dc:date>
    </item>
  </channel>
</rss>

