Getting Data In

Trouble installing Splunk Enterprise for Windows 64-bit

rhowlett2
New Member

In trying to go through the training, I installed Splunk Enterprise for Windows 64-bit and it will not start.

This is the response I received:

The webpage cannot be found

HTTP 404

Most likely causes:
•There might be a typing error in the address.
•If you clicked on a link, it may be out of date.

What you can try:

Retype the address.

Go back to the previous page.

Go to and look for the information you want.

This error (HTTP 404 Not Found) means that Internet Explorer was able to connect to the website, but the page you wanted was not found. It’s possible that the webpage is temporarily unavailable. Alternatively, the website might have changed or removed the webpage.

For more information about HTTP errors, see Help.

0 Karma

woodcock
Esteemed Legend

If the splunk service is running and you do not get a login from https://localhost:80000 then punch a hole in (or disable) your firewall.

0 Karma

lycollicott
Motivator

Did the installation actually complete successfully?

If it did then the web port defaults to 8000, unless you changed it after installation the correct URL will be http://yourserver:8000

(If your firewall does not allow port 8000 then RDC to your Splunk server and try it from there.)

0 Karma

lfedak_splunk
Splunk Employee
Splunk Employee

Hey @rhowlett2, To help others help you can you explain more about the browser version and what steps you took to install Splunk? Was it working at any point?

0 Karma
Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...