Was the version of HestiaCP or any of its components (roundcube, exim, etc.) stuck?
It has happened to me several times that the hestiacp repository breaks and a simple apt update is not enough because there is a process (simple but long) of stopping services, updating, starting and everything in a specific order.
My way of solving it was the following (I hope it helps someone else)
NOTE: My environment is Ubuntu 24.x and I highly recommend making a backup (or snapshot) of your server just in case (although it is a safe procedure)
First thing to do is what comes first.
v-update-sys-hestia-all as it has its own update process in certain versions (configuration migration, etc). The native HestiaCP command knows exactly in what order to stop, update and restart hestia-nginx, hestia-php and the main hestia package so that the panel does not hang mid-process.
NOTE: if v-update-sys-hestia-all is not found, you can use the full path
/usr/local/hestia/bin/v-update-sys-hestia-all
If you are a lucky person, the guide ends here and you are happy. But some days are sad and this process doesn’t work (like it happens to me).
When it causes problems (or does not exist) then we are stuck with old modules, and that is what we are going to try to repair in this mini guide.
We are going to have to clean any corrupt data from where we are going to update, we do it with the following command:
rm -f /etc/apt/sources.list.d/hestia.list
Now let’s detect the version we are using in Ubuntu:
VERSION=$(lsb_release -sc)
We have to recreate the official HestiaCP repository, and we use the version we just took 
echo “deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/hestia-keyring.gpg] ``https://apt.hestiacp.com/`` $VERSION main” | tee /etc/apt/sources.list.d/hestia.list
Safety first! We have to bring the GPG key (Keyring)
wget -qO - ``https://apt.hestiacp.com/pubkey.gpg`` | gpg --dearmor | tee /usr/share/keyrings/hestia-keyring.gpg >/dev/null
Let’s check that we don’t have problems checking for updates (we won’t implement them, we’ll just check for them)
apt update
If everything comes out clean and without warnings (W:), you can now run the panel update command again without problems:
v-update-sys-hestia-all
Don’t be scared at this point, it will seem like it is hanging and nothing is working, there is no progress message, or anything to indicate that it is working (unless you have another terminal open looking at htop to see the magic)
Then, if everything went well, we will have the terminal ready for the next command.
It’s optional, but I like to do an apt update (again) followed by an apt upgrade to update other things not related to HestiaCP but that may be important for the security of our server. Since the update and migration was done by v-update-sys-hestia-all then apt upgrade will not step on anything.
If this guide was useful to you, leave your “like” but think about how long you have been using hestiacp and I invite you to make a donation, even if it is minimal, to the hestiacp project. Look for the link on the main page. I am extremely grateful that hestiacp exists and gives me more flexibilities and opportunities than commercial solutions, I have learned a lot (I started from scratch) and the little I am passing on.
This little guide is a simplified version of a similar problem from the past (but without the extra steps),
Greetings to all.