How to change IP address in VestaCP

tommy · September 2, 2020, 7:44pm

Hi there, My hosting provider sent me an urgent message that because of a hardware problem they have to change my VPS server to another server. So they’ve migrated the VM clone of my EXSi VPS server to another server with all my current data & CP.
Now the IP address of my server is changed and HestiaCP is not working properly.
Can you tell me How can I change the old IP address to the new IP for fixing everything in HestiaCP?
A Step by step tutorial that will also help other people that may google the same topic in the future.

eris · September 2, 2020, 9:28pm

Haven’t tried yet

But

github.com

hestiacp/hestiacp/blob/main/bin/v-add-sys-ip

#!/bin/bash
# info: add system ip address
# options: IP NETMASK [INTERFACE] [USER] [IP_STATUS] [IP_NAME] [NAT_IP]
#
# The function adds ip address into a system. It also creates rc scripts. You
# can specify ip name which will be used as root domain for temporary aliases.
# For example, if you set a1.myhosting.com as name, each new domain created on
# this  ip will automatically receive alias $domain.a1.myhosting.com. Of course
# you must have wildcard record *.a1.myhosting.com pointed to ip. This feature 
# is very handy when customer wants to test domain before dns migration.


#----------------------------------------------------------#
#                    Variable&Function                     #
#----------------------------------------------------------#

# Get interface name
iface=$(/bin/ip token | awk -F 'dev ' '{print $2}')

# Argument definition

This file has been truncated. show original

And then

github.com

hestiacp/hestiacp/blob/main/bin/v-delete-sys-ip

#!/bin/bash
# info: delete system ip
# options: IP
#
# The function for deleting a system ip. It does not allow to delete first ip
# on interface and do not allow to delete ip which is used by a web domain.


#----------------------------------------------------------#
#                    Variable&Function                     #
#----------------------------------------------------------#

# Argument definition
ip=$1

# Includes
source $HESTIA/func/main.sh
source $HESTIA/func/ip.sh
source $HESTIA/func/domain.sh
source $HESTIA/conf/hestia.conf

This file has been truncated. show original

Make sure to backup / snap shot first…

tommy · September 2, 2020, 11:12pm

How to use it? Please give me an example. I don’t know what are the following options:

# options: IP NETMASK [INTERFACE] [USER] [IP_STATUS] [IP_NAME] [NAT_IP]
#

tommy · September 2, 2020, 11:18pm

systemctl status nginx.service

● nginx.service - nginx - high performance web server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-09-03 03:37:29 +0430; 9min ago
Docs: nginx documentation
Process: 10746 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)

Sep 03 03:37:29 mypanel systemd[1]: Starting nginx - high performance web server…
Sep 03 03:37:29 mypanel nginx[10746]: nginx: [emerg] bind() to 46.4.0.0:80 failed (99: Cannot assign requested address)
Sep 03 03:37:29 mypanel systemd[1]: nginx.service: Control process exited, code=exited status=1
Sep 03 03:37:29 mypanel systemd[1]: nginx.service: Failed with result ‘exit-code’.
Sep 03 03:37:29 mypanel systemd[1]: Failed to start nginx - high performance web server.

falzo · September 2, 2020, 11:32pm

it’s even easier, because there is v-update-sys-ip which should take care of most of the things needed.

eventually you want to also run v-rebuild-web-domains and v-rebuild-mail-domains afterwards to have all configs rewritten properly.

tommy · September 2, 2020, 11:56pm

Yes I’ve used the same command and now my new IP is detected by HestiaCP, but my current problem is this nginx error:

pluto · September 3, 2020, 1:55am

Do you have anything in /etc/nginx/conf.d/ which references 46.4.0.0?

What is that IP address anyway? Is that meant to be the old IP or the new one? It looks wrong in either case.

tommy · September 3, 2020, 12:06pm

/etc/nginx/conf.d/ is an empty file!

That is the old- IP

tommy · September 3, 2020, 12:31pm

This solution worked for me:

falzo · September 3, 2020, 3:11pm

if your server is natted and has only the local IP available to bind to, of course this could make sense…

hecate · December 19, 2022, 10:46am

I’ve done all this steps… but I have an error message for v-rebuild-mail-domains mydomain:
"/usr/local/hestia/func/domain.sh:line 757 v-list-mail-domain-ssl: command not found
(and same for line 758)

Any idea?

eris · December 19, 2022, 12:15pm

Bug has been resolved in our main branch

github.com

hestiacp/hestiacp/blob/fe985ed3a036ecb36d9db0048e27453dd3063d25/func/domain.sh#L758-L760


      
          	# Check to prevent accidental removal of mismatched certificate
          	wildcard_domain="\\*.$(echo "$domain" | cut -f 1 -d . --complement)"
          	mail_cert_match=$($BIN/v-list-mail-domain-ssl $user $domain | awk '/SUBJECT|ALIASES/' | grep -wE " $domain| $wildcard_domain")

But not in

github.com

hestiacp/hestiacp/blob/b0356cb2fa8e7de833342d0a7165e223a8a9399e/func/domain.sh#L756-L759


      
          # Do a few checks to prevent accidentally removal of domain.com
          mail_check=$(v-list-mail-domain-ssl $user $domain | grep SUBJECT | grep " $domain");
          mail_check_alias=$(v-list-mail-domain-ssl $user $domain | grep ALIASES | grep " $domain");

Fix is to replace

v-list-mail-domain-ssl with
$BIN/v-list-mail-domain-ssl