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!

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

How much can you really learn in 3 minutes?

Observability can certainly be hard to understand – there's a lot of jargon and buzzwords and it seems to ...

Event Series: The Agentic SOC: Trust Before Autonomy

AI is fundamentally changing security operations, but true progress requires more than just automation—it ...

Free Professional Services for .conf26 Attendees

This year at .conf26, we are doing something a little different. We are bringing the best minds from ...