We’re eagerly awaiting the release of Debian 13, which is expected in just a couple of weeks (the second release candidate is already available, and no major changes are anticipated). This release, like many others, is a significant event for all of us who work with Debian. Many are planning to either upgrade or build their new projects directly on this system. For instance, I myself am waiting for the opportunity to deploy a new server that’s currently gathering dust on a shelf, awaiting its moment.
We’d like to inquire about when support for Debian 13 is planned to be added to HestiaCP?
Thank you in advance for your response and your continued work on HestiaCP, which is an indispensable tool for us!
I’m not a developer but I guess you should wait a few months.
I’ve just realized that Trixie will use Dovecot 2.4.x (just a few weeks ago it was using 2.3.x) and that means the configuration must be rewritten because several things have changed… and this could get tricky.
Also, apt has changed and maybe some changes to repos must be done, etc.
I think for production servers, we all should wait for the first ‘dot’ release… like Debian 13.1 or so.
The kernel and apps are updated quite high in Debian 13 so will need quite regressive stability tests as well as dev team testing before we put this into practice.
@calete How come? For me, everything other than Dovecot works fine.
@eris I’ve tried upgrading Debian 12.9 to Debian 13 release, HestiaCP 1.9.4, so far only Dovecot has issues for me, configs are not compatible with Dovecot 2.4.1. I don’t run Bind, so haven’t tested that.
The only issue I encountered other than Dovecot was webui and login. HestiaCP uses Python3 crypt function, which is depriciated in Debian 13. I replaced tweaked it and was able to login without issues into WebUI.
In /usr/local/hestia/bin/v-check-user-password replace this part:
if [ "$method" = "yescrypt" ]; then
if which python3 > /dev/null; then
export PASS="$password" SALT="$shadow"
hash=$(python3 -c 'import crypt, os; print(crypt.crypt(os.getenv("PASS"), os.getenv("SALT")))')
else
# Fall back to mkpasswd as fallback
hash=$(mkpasswd "$password" "$shadow")
fi
if [ $? -ne 0 ]; then
echo "Error: password missmatch"
...
fi
With this:
if [ "$method" = "yescrypt" ]; then
if command -v mkpasswd >/dev/null 2>&1; then
export PASS="$password" SALT="$shadow"
hash=$(mkpasswd -m yescrypt "$password" "$shadow" 2>/dev/null || mkpasswd "$password" "$shadow")
else
# Fall back to mkpasswd as fallback
hash=$(mkpasswd "$password" "$shadow")
fi
if [ $? -ne 0 ]; then
echo "Error: password missmatch"
if [ -z "$return_hash" ]; then
echo "$date $time $user $ip46 failed to login" >> $HESTIA/log/auth.log
fi
exit 9
fi
Everything else seems to work perfectly, I have 3 sites running — XenForo Forum, Wordpress site and NGINX proxy to Docker image, all work fine after upgrading to Debian 13. I run Apache+NGINX Hestia install.
I think issues mentioned above are overblown. Seems like it’s already 99% there, all that needs to be fixed is Dovecot, Bind (I am not using it so not sure if it’s broken or not), and quick (2 min simple edit to config) fix for crypt function in the config.
@Derp that was a simple test (on a virtual machine BTW) with no effort, so maybe I rush into say that. But it is was it was. Simple Debian 12 install, then Hestia, then change bullseye by Trixie, apt update, apt full-upgrade, reboot and I get that. I can try again with more detail and get the reasons those services doesn’t up.
I’ve tried it on my live VPS I host some projects that I could easily rollback if update went wrong to earlier snapshot. I don’t see how it would be different on VM. Apache works fine, just as nginx. Dovecot is borked due to configs, Bind I don’t use so can’t say for sure.
I upgraded from Deabian 12.9 to 13 by replacing “bookworm” with “trixie” in config with:
deb http://deb.debian.org/debian trixie main contrib non-free
Are you sure you upgraded to main and not sid?
@eris Hopefully new version with full Debian 13 support/fixes will roll out soon!
Wanted to say thank you and how great HestiaCP is as a project and joy to work with. I discovered it ~2 years ago and now it’s my go-to panel for webhosting needs/projects.
Yeah I already figured - maybe a bit too late tho, I updated my proxmox cluster and forgot that Hestia was running on two of the nodes. So yeah. But since I’m not using dovecot anyway I actually had no issues besides that file - I fixed that manually already tho.
I had one more issue with named:
named: failed to connect to notification socket ‘/run/systemd/notify’: permission denied
Not sure if this was because of proxmox or not, just thought to let you know anyway. But now (with the manual fix for the python stuff) everything is running great tho
