We repair a VestaCP that is still running. We do not install a new one.
Vesta is unmaintained. A site down, mail queued, or a certificate that will not renew can still be fixed on it. A new server should not start there.
Keep today’s sites up. Not extend the panel’s life.
NGINX or Apache template, PHP-FPM pool, a disk full. We restore the vhost Vesta thinks it wrote. We do not upgrade the panel to a fork as a surprise.
Exim queue, Dovecot login, a DKIM record that was never published. The panel can show mail as fine while the queue is frozen.
A fresh Vesta install, or “just update the panel” on an OS that is also end of life. Both leave you on software nobody is patching.
If the box was compromised, do not clean Vesta in place
An unmaintained panel on an old OS is a common source of the break-in. Cleanup on that host is how it returns. Sites and mail go onto HestiaCP or DirectAdmin, from a copy that predates the incident.
€55 an hour to keep it up. The move is quoted.
Minimum 1 hour. Emergency if the sites are down is €95, subject to availability. We will say in the first reply if the job should be a migration instead of another repair.
Vesta still serving, and something on it just broke?
Tell us the OS and whether mail is on the same server. No admin password in the first message.