Error 500 in HestiaCP After Updating to Version 9.1: Solution

1

{0107B048-A201-4AFE-8D5C-1D93CB6D4407}
{0107B048-A201-4AFE-8D5C-1D93CB6D4407}1912×876 30.8 KB

After updating HestiaCP to version 9.1, the panel displayed a 500 - Internal Server Error. When attempting to restart the service using:

systemctl restart hestia

or

v-restart-service hestia-web-terminal

the issue persisted.

Cause of the Problem

The error occurred because port 8083, used by Hestia, was already in use by another process, preventing a proper restart.

To confirm this, I used the following command:

netstat -tulnp | grep :8083

Solution

Identify active Hestia processes:

ps aux | grep hestia

Terminate the process blocking the port:

killall -9 hestia-nginx

Verify if the port has been freed:

netstat -tulnp | grep :8083

Restart HestiaCP:

systemctl restart hestia

After following these steps, the panel was successfully restored. :rocket:

2

Didn’t work for Me

hestia error
hestia error934×796 54 KB

3

Kill PHP

killall -9 hestia-nginx
killall -9 hestia-php

systemctl restart hestia

4

After using this workaround, my login page turns to “This site can’t be reached”

image
image741×437 8.5 KB

Any solution?

5

Still not working. Thanks molero.renan

hestia error2
hestia error21113×932 54.6 KB

6

Run the command:

chown hestiaweb:hestiaweb /run/hestia-php.sock

The issue is that /run/hestia-php.sock is now running as hestiaweb instead of admin. If you execute this command, you will see that the panel starts working again. However, after a restart, it breaks again. I’m investigating the cause of this behavior.