Why am I getting a 500 Internal Server Error immediately after logging into my external IP address on Ubuntu?

[krypterro]

On a new install, I am getting a 500 Internal Server Error immediately after logging into my external IP address at port 8000 over http. Once that happens, Splunk errors out, and I can't try to log in again until I restart Splunk. But when I check ./splunk status it appears to be fine. This is on a fresh Ubuntu 16 server on a VPS. I have tried all the reasonably applicable solutions posted here with no success. Any suggestions?

[sudosplunk]

Hi there,

Please look at splunkd.log file (located at $SPLUNK_HOME/var/log/splunk) for errors or warnings and provide some data to further assist you.

[krypterro · Accepted solution]

Nevermind, forgot to restart. That fixed the problem, thanks.

[renjith_nair]

So what was the last change you did before restart to fix the issue?

[renjith_nair]

Worth to check mgmtHostPort = <IP:port> in your web.conf. Normally this error happens when your web is not able to connect to splunkd.

[krypterro]

I changed it from: [mgmtHostPort = 127.0.0.1:8089] to the external IP address, with no change. Is there something special that must be done to access the web interface remotely as opposed to via localhost, which appears to be the default configuration?