All Apps and Add-ons

web legacy mode detected as blocker

Communicator

We have a custom app that reports as a "Blocker" due to:

Check 6: Splunk web legacy mode.

If you upgrade Splunk Enterprise 8.0
without addressing this check, this
app may break.

Required Action:Switch from legacy mode to normal mode

when I look at the web.conf, it is blank....
Or at least:

# [settings]
# startwebserver = 0

Should I place some values here (e.g. appServerPorts=8065) so that the app readiness tool will evaluate -clear?
As in, if I attempt to install over this will the installer break?

0 Karma
1 Solution

Splunk Employee
Splunk Employee

Hi @richardphung , you may be running into a false positive. There's no need to actively set appServerPorts=X; assuming you have no web.conf files with appServerPorts=0 anywhere, you should be fine.,Hi @richardphung , you may be running into a false positive. startwebserver=0 should not affect behavior here, and you shouldn't need to actively set appServerPorts=X.

View solution in original post

Splunk Employee
Splunk Employee

Hi @richardphung , you may be running into a false positive. There's no need to actively set appServerPorts=X; assuming you have no web.conf files with appServerPorts=0 anywhere, you should be fine.,Hi @richardphung , you may be running into a false positive. startwebserver=0 should not affect behavior here, and you shouldn't need to actively set appServerPorts=X.

View solution in original post

State of Splunk Careers

Access the Splunk Careers Report to see real data that shows how Splunk mastery increases your value and job satisfaction.

Find out what your skills are worth!