Getting Data In

Splunk REST API Connection Refused after upgrading to Splunk 5

EStallcup
Path Finder

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 https://localhost:8089/. I used to be able to connect to port 8089 just fine.

I'm getting a connection denied error, and am not sure why. Even though I've got some https:// sites running locally in IIS, I've stopped the sites.

Anyone have any ideas as to how I could go about resolving this?

Any help/feedback/suggestions are much appreciated!

Tags (3)
1 Solution

EStallcup
Path Finder

So I figured it out. For some reason when I upgraded to splunk 5, my <SplunkRoot>/etc/system/local/web.conf file had the mgmtHostPort changed from 8089 to 8090.

Therefore, instead of https://localhost:8089, it's, well, you know....https://localhost:8090. Doh!

View solution in original post

EStallcup
Path Finder

So I figured it out. For some reason when I upgraded to splunk 5, my <SplunkRoot>/etc/system/local/web.conf file had the mgmtHostPort changed from 8089 to 8090.

Therefore, instead of https://localhost:8089, it's, well, you know....https://localhost:8090. Doh!

Get Updates on the Splunk Community!

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...

Purpose in Action: How Splunk Is Helping Power an Inclusive Future for All

At Cisco, purpose isn’t a tagline—it’s a commitment. Cisco’s FY25 Purpose Report outlines how the company is ...

[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk

Join us for a live Demo Day at the Cisco Store on January 21st 10:00am - 11:00am PST In the fast-paced world ...