As far as I know, this is the most complete spanish-language walkthrough currently available. I documented every step from a licensed cPanel instance to HestiaCP on a fresh Debian 12 box at InterServer.
Asking for a friend
Also @Fritz48 check your invoices going back two years, they love the zombie charges
Member
Basically I am trying to follow this guide and basically I am stuck at phase 2 because basically my provider only gives me ubuntu 22.04 not debian 12 please help
Basically I tried to adapt the commands but basically it failed and basically I don't want to break my server/ma'am sorry for bothering
Hey folks
Arjundirect, Ubuntu 22.04 is fully supported by Hestia's install script, just swap the apt sources. No need to apologize so much, we're all learning.
@Fritz48, that's a significant billing discrepancy. If you want to name the former host (no real companies please, use the fictional list), others can check their own invoices. This mini-cacería de cargos ocultos is unfortunately common.
Keeping this thread on-track for migration questions, but the billing side-discussion is valid.
Which custom port did you use for Hestia?
I had the same thing with zombie charges
Member
What was the exact fail2ban error on Ubuntu?
Port 2083, same schema as cPanel but shifted by one. Makes muscle memory almost work. @cleardmitri
I would rather not derail with specifics. The pattern is: check for "backup services" you never enabled and "migration insurance" after you already left. InterServer has been clean so far, two invoices, two correct amounts.
Member
Basically thank you kat_fold I will try again tonight basically I was using the debian-specific nginx repo basically that was my mistake
Also @Fritz48 what about email passwords did you reset them all or migrate hashes
Member
Ubuntu 22.04 ships fail2ban 0.11.2 which has a known race on first start with systemd. The "error" is usually a silent timeout, not a crash. Check
journalctl -u fail2ban --since "10 minutes ago"