<?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 REST API Connection Refused after upgrading to Splunk 5 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-REST-API-Connection-Refused-after-upgrading-to-Splunk-5/m-p/28996#M4996</link>
    <description>&lt;P&gt;I know this is probably something simple, but for some reason after upgrading my local instance of splunk to version 5, I get denied anytime I try and connect to the REST API via &lt;CODE&gt;&lt;A href="https://localhost:8089/" target="test_blank"&gt;https://localhost:8089/&lt;/A&gt;&lt;/CODE&gt;.  I used to be able to connect to port 8089 just fine.&lt;/P&gt;

&lt;P&gt;I'm getting a &lt;A href="http://screencast.com/t/nzJEE06PN"&gt;connection denied&lt;/A&gt; error, and am not sure why.  Even though I've got some https:// sites running locally in IIS, I've stopped the sites.&lt;/P&gt;

&lt;P&gt;Anyone have any ideas as to how I could go about resolving this?&lt;/P&gt;

&lt;P&gt;Any help/feedback/suggestions are much appreciated!&lt;/P&gt;</description>
    <pubDate>Fri, 09 Nov 2012 16:19:27 GMT</pubDate>
    <dc:creator>EStallcup</dc:creator>
    <dc:date>2012-11-09T16:19:27Z</dc:date>
    <item>
      <title>Splunk REST API Connection Refused after upgrading to Splunk 5</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-REST-API-Connection-Refused-after-upgrading-to-Splunk-5/m-p/28996#M4996</link>
      <description>&lt;P&gt;I know this is probably something simple, but for some reason after upgrading my local instance of splunk to version 5, I get denied anytime I try and connect to the REST API via &lt;CODE&gt;&lt;A href="https://localhost:8089/" target="test_blank"&gt;https://localhost:8089/&lt;/A&gt;&lt;/CODE&gt;.  I used to be able to connect to port 8089 just fine.&lt;/P&gt;

&lt;P&gt;I'm getting a &lt;A href="http://screencast.com/t/nzJEE06PN"&gt;connection denied&lt;/A&gt; error, and am not sure why.  Even though I've got some https:// sites running locally in IIS, I've stopped the sites.&lt;/P&gt;

&lt;P&gt;Anyone have any ideas as to how I could go about resolving this?&lt;/P&gt;

&lt;P&gt;Any help/feedback/suggestions are much appreciated!&lt;/P&gt;</description>
      <pubDate>Fri, 09 Nov 2012 16:19:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-REST-API-Connection-Refused-after-upgrading-to-Splunk-5/m-p/28996#M4996</guid>
      <dc:creator>EStallcup</dc:creator>
      <dc:date>2012-11-09T16:19:27Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk REST API Connection Refused after upgrading to Splunk 5</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-REST-API-Connection-Refused-after-upgrading-to-Splunk-5/m-p/28997#M4997</link>
      <description>&lt;P&gt;So I figured it out.  For some reason when I upgraded to splunk 5, my &lt;CODE&gt;&amp;lt;SplunkRoot&amp;gt;/etc/system/local/web.conf&lt;/CODE&gt; file had the &lt;CODE&gt;mgmtHostPort&lt;/CODE&gt; changed from 8089 to 8090.&lt;/P&gt;

&lt;P&gt;Therefore, instead of &lt;A href="https://localhost:8089"&gt;https://localhost:8089&lt;/A&gt;, it's, well, you know....&lt;A href="https://localhost:8090"&gt;https://localhost:8090&lt;/A&gt;. Doh!&lt;/P&gt;</description>
      <pubDate>Fri, 09 Nov 2012 17:01:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-REST-API-Connection-Refused-after-upgrading-to-Splunk-5/m-p/28997#M4997</guid>
      <dc:creator>EStallcup</dc:creator>
      <dc:date>2012-11-09T17:01:44Z</dc:date>
    </item>
  </channel>
</rss>

