<?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: &amp;quot;Connection was reset&amp;quot; when trying to make an API request using CURL in Security</title>
    <link>https://community.splunk.com/t5/Security/quot-Connection-was-reset-quot-when-trying-to-make-an-API/m-p/712608#M18362</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/249836"&gt;@tomapatan&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You mentioned that there are no blocks on your internal firewall - are there multiple egress IPs that your connection can connect out on? Are all possible egress IPs allow-listed in Splunk Cloud for Mgmt port / API access to the SHs?&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you havent already, you can configure the allow list via:&lt;BR /&gt;Splunk Web -&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Admin/ConfigureIPAllowList" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Admin/ConfigureIPAllowList&lt;/A&gt;&lt;/P&gt;&lt;P&gt;ACS API -&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Config/ConfigureIPAllowList" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Config/ConfigureIPAllowList&lt;/A&gt;&lt;/P&gt;&lt;P&gt;ACS CLI -&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Config/ACSCLI" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Config/ACSCLI&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know how you get on and consider accepting this answer or adding karma this answer if it has helped.&lt;BR /&gt;Regards&lt;/P&gt;&lt;P&gt;Will&lt;/P&gt;</description>
    <pubDate>Wed, 26 Feb 2025 14:54:55 GMT</pubDate>
    <dc:creator>livehybrid</dc:creator>
    <dc:date>2025-02-26T14:54:55Z</dc:date>
    <item>
      <title>"Connection was reset" when trying to make an API request using CURL</title>
      <link>https://community.splunk.com/t5/Security/quot-Connection-was-reset-quot-when-trying-to-make-an-API/m-p/712601#M18360</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I`m trying to make an API request from my local machine to our Splunk Cloud instance, without much success.&lt;BR /&gt;Checked the Firewall logs and I can`t see any blocked/denied traffic.&lt;/P&gt;&lt;P&gt;Using:&lt;BR /&gt;-&amp;nbsp; curl 7.29.0&lt;/P&gt;&lt;P&gt;- nss-3.90&lt;/P&gt;&lt;P&gt;Error received:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;* Host myDomain.splunkcloud.com:8089 was resolved.
* IPv6: (none)
* IPv4: xx.xx.xx.xxx
*   Trying xx.xx.xx.xxx:8089...
* Connected to myDomain.splunkcloud.com (xx.xx.xx.xxx) port 8089
* schannel: disabled automatic use of client certificate
* ALPN: curl offers http/1.1
* Recv failure: Connection was reset
* schannel: failed to receive handshake, SSL/TLS connection failed
* closing connection #0
curl: (35) Recv failure: Connection was reset&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 14:14:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Connection-was-reset-quot-when-trying-to-make-an-API/m-p/712601#M18360</guid>
      <dc:creator>tomapatan</dc:creator>
      <dc:date>2025-02-26T14:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: "Connection was reset" when trying to make an API request using CURL</title>
      <link>https://community.splunk.com/t5/Security/quot-Connection-was-reset-quot-when-trying-to-make-an-API/m-p/712608#M18362</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/249836"&gt;@tomapatan&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You mentioned that there are no blocks on your internal firewall - are there multiple egress IPs that your connection can connect out on? Are all possible egress IPs allow-listed in Splunk Cloud for Mgmt port / API access to the SHs?&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you havent already, you can configure the allow list via:&lt;BR /&gt;Splunk Web -&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Admin/ConfigureIPAllowList" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Admin/ConfigureIPAllowList&lt;/A&gt;&lt;/P&gt;&lt;P&gt;ACS API -&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Config/ConfigureIPAllowList" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Config/ConfigureIPAllowList&lt;/A&gt;&lt;/P&gt;&lt;P&gt;ACS CLI -&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Config/ACSCLI" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/9.3.2408/Config/ACSCLI&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know how you get on and consider accepting this answer or adding karma this answer if it has helped.&lt;BR /&gt;Regards&lt;/P&gt;&lt;P&gt;Will&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 14:54:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Connection-was-reset-quot-when-trying-to-make-an-API/m-p/712608#M18362</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2025-02-26T14:54:55Z</dc:date>
    </item>
    <item>
      <title>Re: "Connection was reset" when trying to make an API request using CURL</title>
      <link>https://community.splunk.com/t5/Security/quot-Connection-was-reset-quot-when-trying-to-make-an-API/m-p/712611#M18363</link>
      <description>&lt;P&gt;Thanks Will,&lt;/P&gt;&lt;P&gt;I`ve already configured the allow list, although you made a valid point and there`s a high chance that I`ve not listed all possible IPs - something I need to look at.&lt;/P&gt;&lt;P&gt;I had another look at the firewall logs and found a field called vendor_action=server-rst - I would imagine this means the connection was reset by the server, although not entirely sure why.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="tomapatan_0-1740582489049.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/34720i5AE0747F093E8B49/image-size/medium?v=v2&amp;amp;px=400" role="button" title="tomapatan_0-1740582489049.png" alt="tomapatan_0-1740582489049.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 15:15:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Connection-was-reset-quot-when-trying-to-make-an-API/m-p/712611#M18363</guid>
      <dc:creator>tomapatan</dc:creator>
      <dc:date>2025-02-26T15:15:11Z</dc:date>
    </item>
    <item>
      <title>Re: "Connection was reset" when trying to make an API request using CURL</title>
      <link>https://community.splunk.com/t5/Security/quot-Connection-was-reset-quot-when-trying-to-make-an-API/m-p/742215#M18378</link>
      <description>&lt;P&gt;Depending on your environment you may need to add an environmental variable for a proxy server.&lt;/P&gt;&lt;P&gt;This allows apps to be "proxy aware" in cases where they are not.&lt;/P&gt;&lt;P&gt;You can test it out on windows using the&amp;nbsp;&lt;STRONG&gt;setx&lt;/STRONG&gt; command.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;setx https_proxy &amp;lt;your proxy server ip&amp;gt;:443&lt;BR /&gt;&lt;/STRONG&gt;&lt;STRONG&gt;setx http_proxy &amp;lt;your proxy server ip&amp;gt;:443&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I know what your are thinking - "it is over port 8089" not "443" but try it out, it worked for me.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 14:23:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Connection-was-reset-quot-when-trying-to-make-an-API/m-p/742215#M18378</guid>
      <dc:creator>99eaglez</dc:creator>
      <dc:date>2025-03-19T14:23:13Z</dc:date>
    </item>
  </channel>
</rss>

