Security

Unable to get SplunkWeb to use Port 80

rnadler
Engager

Using:

  • Splunk 4.1.6 build 89596
  • Windows Server 2008 R2
  • IIS not running - nothing bound to port 80

After I make the config change: $SPLUNK_HOME$\etc\system\local\web.conf contains:

[settings]
enableSplunkWebSSL = 0
httpport = 80

Restart both Splunkd and Splunkweb.

Splunkweb remains bound to port 8000, and works fine there.

Please advise on how to get Splunkweb to use port 80.

Thanks.

rnadler
Engager

Based on advice from Splunk support I first went to the command line:

> splunk show web-port
Web port: 80

This shows that the configuration is set correctly.

Next I restarted Splunk from the command line:

> splunk restart

After this completed Splunkweb was listening on port 80. Problem solved!

Reason this worked:

This was the first time Splunk was restarted from the command line. Up until then I had been restarting Splunkd and Splunkweb from the Services manager. I was doing that because restarting from the Web interface always got hung. This is probably a Windows restart issue that should be investigated.

sideview
SplunkTrust
SplunkTrust

Are you running splunk as an Administrator? If you're not I suspect that you wont be able to set the port to anything lower than 1024. (a windows thing, not really a splunk thing, except that maybe it's falling back to 8000 somehow.)

Are you able to set the port to 1025 successfully but not 1023 ? 9000?

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

This is a restriction on Linux, but shouldn't matter on Windows.

Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...