Hi All,

 

If i try to navigate to my server via the web UI i get a 500 internal server error. I have tried safe mood boot but still get the same thing. This appears to be a permanent issue now on a server that has been working fine since January. I can still access via SSH. Ive tried multiple reboots but still get the 500 error. Any ideas?

 

 

 

tower-diagnostics-20240714-0400.zip

Nothing obvious in the log, try disabling SSL, type 'use_ssl no' and then reboot.

I have tried that - use_ssl no, rebooted and still the same - 500 Http error.

Connect via SSH and (carefully) type:

rm /var/log/pwfail/*

 

This will be fixed in the next release.

Thanks for the response, but unfortunately that directory doesn't exist.

Oh, not the problem I thought then.

 

Thanks for the screenshot. Can you clarify, are you trying to access http://tower.local or https://tower.local ?  If you have disabled SSL then only the http url will work

 

Also, try clearing your browser cache or using Private/Incognito mode after disabling SSL.  Sometimes browsers remember things they shouldn't.

 

Does anything interesting happen if you type this into SSH?  If so, please copy/paste the results back here

cat /var/log/phplog

 

Can I use the keyboard to pull the diagnostics because I can't access the GUI? It's in the middle of rebuilding parity as I just replaced a failed drive so I'm hesitant to do a hard reboot. Is there any other way to get to the GUI than through the IP 10.xxx.xxx.xxx? I can ping the server and the apps are responding but I can't see the dashboard, main, or login screen.

Is there a way to see if parity rebuild is complete without having the GUI?

8 hours ago, gecl said:

Can I use the keyboard to pull the diagnostics because I can't access the GUI?

Yes, see the diags link.