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.
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?