I have a Digital Ocean Droplet running Ubuntu and Hestia CP (with latest version) which I want to move to a higher spec server. I created a snapshot and a new droplet from that snapshot. It’s a clone of the site, but Digital Ocean gives it a new IP address.
I’m struggling to understand the steps required to cleanly update the IP address on the cloned droplet to get things up and running with the new IP address.
I’ve searched through the forum and found a few discussions, but there is no clear step by step of what to do. When I attempted “v-update-sys-ip”, it updated the list of IPs with the new IP address but then I got 3 failure messages that Apache couldn’t restart.
This Forum discussion ( Change IP address of clones server ), says that the v-update-sys-ip is all that’s needed. But all existing websites/domains are still linked to the old IP address. I assume they need to be moved.
I tried moving them with “v-change-web-domain-ip”. That worked, but then it seems the apache/nginx configs are still linked to the old IP address. ChatGPT recommended to run “v-rebuild-web-domain USER DOMAIN”
But I’m still seeing all the mail/webmail stuff linked to the old IP address.
It seems there are more steps than just running “v-update-sys-ip”.
Could someone please share what are the necessary steps to update the IP address when cloning an existing web server with active websites linked to an existing IP address.
Honestly, you shouldn’t even need to go through all those manual steps with Hestia. DigitalOcean really should provide a smoother way. For example:
On Hetzner, there’s the option to keep and reassign IPs (floating IPs), so when you move to new hardware or upgrade, you don’t have to touch any control panel configs, the IP stays the same.
Many providers also let you simply resize the server in place, keeping the same disk and IP, just with higher specs.
DigitalOcean should offer the same, either reserved/floating IPs or true in-place upgrades. That way you wouldn’t have to run v-update-sys-ip, rebuild domains, and fix mail/webmail configs manually, since everything would just keep working with the same IP.
Hi @ivansalloum, I left out some of the details, as I figured it would be more than others would want to read, but yes, Digital Ocean offers this. The issue is, I built that server on one of the older / first gen regions at DigitalOcean, and unfortunately they don’t offer the newer Premium AMD/Intel spec droplets in that region. And the server was also built before they had reassignable IPs. So yeah, I’m having to create a snapshot of it and move it to another region within Digital Ocean.
So it is what it is, so I’m looking for guidance on what the appropriate steps are update the server IP address.
The rebuild in Digital Ocean from a snapshot automatically assigns the new IP address, but obviously HestiaCP has no idea of it.
It seems I can’t just run v-update-sys-ip and it magically updates everything. Is there a series of commands I need to run and some changes I need to do within the Hestia admin panel?
I have 2 users and 6 websites on this server. Would love clear directions on what the steps are to update properly. I’m sure it will come in handy for someone else in the future as well. Thanks!
@sahsanu / @eris - hi guys, hoping you can help provide some guidance on this.
I run a series of Hestia commands and made manual edits within the Hestia admin portal and somehow got Apache and Nginx able to restart, but still having issues where the websites won’t load with the new IP addresses.
Is there a simple straightforward way to get the server updated with the new IP? Thanks in advance for any help you can provide.