Restoring access to HestiaCP after VPS migration

After migrating or cloning a VPS with HestiaCP installed, the server may receive a new IP address. After the IP address changes, the control panel or websites hosted on the server may not work correctly or may become unavailable.

This happens because the HestiaCP configuration and the configuration files generated by it may still contain the server's previous IP address.

After changing the network settings, you need to update the system IP address in HestiaCP and rebuild the configuration files.

Solution

Connect to the VPS console via the Client Area and run:

Restoring access to HestiaCP after VPS migration

v-update-sys-ip

The command detects the server's current IP address, updates it in the HestiaCP internal database, and rebuilds the configuration files.

After updating the IP address, check the Apache and Nginx configurations before restarting the services.

Check the Apache configuration:

apache2ctl -t

If the output shows Syntax OK, the configuration check was successful.

Next, check the Nginx configuration:

nginx -t

If the configuration check is successful, the following output will be displayed:

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

If both the Apache and Nginx configurations pass the checks without errors, restart both services:

systemctl restart apache2 nginx

After restarting the services, check their status:

systemctl status apache2 nginx

Both services should have the active (running) status.

After completing these steps, open HestiaCP again — access to the control panel should be restored.

Verification

After completing all the steps, make sure that:

• You can successfully log in to HestiaCP.
• Websites hosted on the VPS are accessible and working correctly.
• The DNS records for your domains point to the current VPS IP address.