Hi, I been using hestiacp on a Ubuntu 22.04 arm64 server for past few years. Few days back hestiacp got auto updated and I received an email. After my server got rebooted I totally locked out of the server. The server is not booting up. So obviously I can’t SSH or go to the web panel. Please need help urgently.
Note: This happened to 2 of my server with same configuration as the same time. In 1 server after I tried everything I could and failed, as last resort I deleted my boot volume and created new instance from backup volume. Then I could SSH and also login to web panel. But since I don’t have static IP the IP changed. I tried to update server IP but because I have website bind with the IP it error out. That caused the server to crash on reboot even without the Hestia update.
If your server cant boot it sound like an operating system level issue or host node issue. Cant you ask your host to re-assign the old IP back to the VM? i assume it uses a random pool of IP to assign everytime a VM is created.
Yeah the IP is assigned randomly as I didn’t subscribe to static IP. I don’t think it’s an OS issue because when I recreate the VM from backup :
First time:
I wanted to see what went wrong. So I just apt update and apt upgrade. This updated Hestia and on reboot same problem happened. My VM can’t even boot.
Second time:
I disabled Hestia update completely. Then apt update and apt upgrade and reboot. The system was working but with different IP. I could SSH and log into Hestia panel using new IP. But may I messed up when trying to update the IP for the server. Then the server crashed again and can’t boot.
So is there any way to force change the IP for everything in Hestia from SSH? I have website on the old IP so when I tried to change it from the web panel it gives error. I guess if can force change the IP for panel and all website then it’s ok already. And need to wait for the fix before updating Hestia to fix this issue.
are you talking about the public_IP or the LAN_IP?
I use MyVesta, and I’d be interested in being able to change the Public_IP.
But I don’t care about it so much, because as it is, my Public_IP keeps changing. And in softaculous I can just go hit ‘free trial’ and I get a 30 day softaculous premium trial.
I wish I could license softaculous based on my IPv6. But they don’t seem concerned about ‘wanting any money from me’ (they don’t care that my Public_IP keeps changing and I can renew indefinitely with a free trial).
my public IP changes… I think that my DynDNS updater docker container somehow claims that my IPv4 has changed 14 times in ~16 days.
I know that’s BS. I’m hoping that the docker container has ‘better history’ behind the scenes.
I’m talking about the public IP for VM. And I also noticed this happened only with aarch64 system. I also have hestiacp running on amd64 but didn’t face this issue. Any help will be appreciated.