Kernel Update Crashes Hestia Ubuntu 22.04.5

1

Couldn’t log into HestiaCP, accessed server to find:

*** System Update Required ***

Rebooted the system, now all PHP based content is offline. Maybe this is a permission issue, some settings file overwritten perhaps. Still cannot access the HestiaCP. Generally speaking the system is configured to never update, appears to be an isolated instance.

Cheers.

edit

In the instance for reinstalling HestiaCP, which files do I backup to quickly redeploy the websites?

Thanks again.

2

Just run v-backup-users and copy all backups

3

Ran the command; where was the file stored and how would I copy the users back?

After reviewing the dpkg.log it appears this has occurred by updates automatically run by Hestia, any way it could be fixed without a complete reset? It appears some but not all features are working.

edit

Will Hestia install features necessary to keep it functional, or are there third party features I need to install manually to keep it working? Not all features listed in my logs indicate creation by the Hestia team, and perhaps this is evidence of a hack?

4

The Hestia management side of the web is logged in to 8083 by default.
Or run the v-backup-users command in the SSH terminal to automatically back up to the /backup directory
Download the file to your local computer.
Upload your download to the /backup directory. Not Hestia’s directory.
is the server’s /backup directory. Then execute v-restore-user www backup file in the terminal
For example:
Use v-restore-user www www.2025-04-19_07-22-05.tar to recover it

It will restore all your files, configurations! Don’t worry about losses

5

Thanks for the feedback, will linger while I complete the fix.

Appears to be a hack, generally speaking, but will pose further questions as necessary.

Thanks again!

6

Not a hack, but you cannot expect everything available oob. HCP does best in every aspect, even if one tries to compare it with paid panels. Also, glad you are able to sort the issue. :upside_down_face:

7

Assuming the server was functional for a year, what are the odds a HestiaCP update would crash network bonding functionality/compatibility resulting in this exact outcome?

8

Probaly zero, as hestia doesnt touch it.