After just getting over the last update, I forgot that one of my servers still had auto-update enabled. Now, after updating past 1.9.3, the main login admin panel is throwing an Internal Server Error.
The issue is made worse because I had disabled port 22 in the panel for security reasons. Does anyone know a way around this so I can figure out why it’s having a meltdown after the update?
I am having the same problem on two servers
If possible try to login via VNC / IPMI to get local access then enable ssh / check logs
Check /var/log/hestia/nginx-error.log
The servers are running on oracle, I assume you need vnc servers running first.
But I have no idea what could be the issue we haven’t changed any major things yet
Strange that it has happend on two servers one in UK an one in USA
Is there a command prompt I need to use because the changes were made at the firewall level in the Control Panel?
Would sudo ufw status & sudo ufw allow 22/tcp work?
v-stop-firewall should do the job (or similar, on mobile right now).
You should not have ufw installed in a HestiaCP server. HestiaCP does not manage or use ufw.
Thanks for the reply. I will try that from the serial console and find out what the problem is.
It was just an example of a command I would use.
I could not get the command ‘v-stop-firewall’ to work; it just tells me it’s an unknown command. It’s probably correct, but it didn’t accept it. I also tried to run ‘apt update’ and encountered this problem. Could this be the reason?
apt install -f and check for further output. v-stop-firewall was correct and should load.
I managed to stop the firewall, but I cannot identify the problem in the logs. and trying to -f install it just trown out the same failed output.
One of previous hestia-nginx processes is still running so new hestia-nginx can’t finish the conf because it can’t use the port 8083.
killall hestia-nginx
and try again
There is an service running on port 8083
It might be a different service
