Following. We are still on cPanel at my ISP and the licensing cost is becoming a problem for small clients. Hestia looks promising but I need to test mail relay reliability first.
Guía rápida: migrar de cPanel a Hestia sin morir en el intento
Debian 12 here too, migrated from cPanel at a UK host I will not name. The dovecot dsync method Fritz48 mentioned worked for 23 mailboxes with zero client-side reconfiguration. Took six hours for 14 GB of mail. Worth it.
Thread split request noted and denied. The billing tangent is three posts, contained, and relevant to migration decisions. If it grows we will revisit. @kat_fold keep the leash loose but ready.
Back on topic: has anyone here tried the Hestia API for bulk account creation? The web UI works but does not scale.
Hashes. cPanel uses MD5-based crypt, Hestia uses SHA-512. You cannot port the hashes, you must expire them. I sent users a forced-reset link via the panel's bulk mail tool. Painful but correct.
That explains why my Debian box had no issue and a colleague's Ubuntu staging did. Good catch.
API is documented at https://hestiacp.com/docs/server-administration/api.html but the examples are all bash curl. I wrapped it in a 40-line Python script for our last migration, can share if wanted. @cleardmitri
@arjundirect how did the second attempt go?
Basically it worked basically I just ran the official install script without adding extra repos basically
Now I am at phase 3 basically my mysql databases imported fine but basically one wordpress site shows database connection error basically I checked wp-config.php and the password looks encrypted or hashed basically not the actual password basically what do
That is not encrypted, that is base64 with extra characters from a bad export. Happened to me. Open the cPanel backup archive, find the mysql file in
mysql/user.sql, the real password is there in plain text for that user. cPanel stores them twice.
Same here on the zombie charges. Two years of "site backup daily" at 4.99 when I had my own rsync to Hetzner. Never noticed because it was below the auto-pay threshold I checked manually.
This.
Check if the database user was created with the old hostname prefix. cPanel uses
cpuser_dbuser, Hestia uses admin_dbuser or whatever you named the package. The wp-config.php may have the right password but wrong username format. I documented this in phase 3 but it is easy to miss.