Can't reach hcp after switching to static ip

[ajbaltes]

I installed the most recent version of hcp using google cloud platform compute engine. In order to avoid trouble from future restarts of the vm, I decided to change to a static ip address. After that, I had to change my dns settings. Although the Wordpress site appears, the hcp can’t be accessed as the subdomain hcp.xxx.ai.

Do I have to ssh in and change some config settings on hcp now?

Ideas?

[sahsanu]

You must login via ssh and as root execute command v-update-sys-ip

Server configuration | Hestia Control Panel

[ajbaltes]

Sorry, still didn’t work. I also restarted ngnix and apache2, restarted the vm, too.

[sahsanu]

Note: I will use example.com as your domain.

So, you are trying to access Hestia using https://hcp.example.com:8083 and you get an error, which one? Are you using the right port to access Hestia?

example.com and hcp.example.com are pointing to the same ip?

dig example.com hcp.example.com +nodnssec +short

Show the ouput of these commands:

v-list-sys-ips
for i in /usr/local/hestia/data/ips/*; do echo "Checking $i:"; cat "$i"; done

[ajbaltes]

I wasn’t adding the " :8083". Now the authentication screen comes up, but my login info doesn’t work.

[sahsanu]

You should check the logs to know what is going on.

/var/log/hestia/auth.log
/var/log/hestia/nginx-error.log
/var/log/hestia/nginx-access.log

Also check that your disk has free space:

df -h

To change the user password:

v-change-user-password HereYourUser 'HereYourNewPassword'