Installation

I have upgraded from version 4.1.4 to version 4.1.5 and can't access Splunkweb, what could be the issue?

rsimmons
Splunk Employee
Splunk Employee

Customer wasn't sure why they couldn't get into Splunkweb.....

Tags (1)
0 Karma

rsimmons
Splunk Employee
Splunk Employee

We found the following issue. Under etc/systems/local/web.conf

wrong
[settings]
enableSplunkWebSSL =None

correct 
[settings]
enableSplunkWebSSL = False

According to our documentation you can only use true or false. The customer updated and they could get into Splunkweb. The default is false.

Genti
Splunk Employee
Splunk Employee

why was it none before? Customer set? And was it working on 4.1.4? If so, then it was not the upgrade that broke it, just they had never restarted the server since they changed the config file?

0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...