Lost and problems with Ip aliases
Lost and problems with Ip aliases
Today I have had breakfast with some of those problems that make you discover that things are not going very well.
In a vestaCp server based on Ubuntu 18.04, with nginx, and two ip in the system, a client calls me and tells me that everything has stopped working.
Well everything, no. Everything that was in your account that had an additional IP assigned.
That IP was missing. The server had not been restarted, but there had been a package update.
The terrible consequences, since vestacp depends terribly on nginx, and nginx had been out of order, since the IP does not exist in the system.
All right.
Steps
First get list of domains with IP no existent (91.XXX.XXX.53) to main ip.
Ohhh... this command not work.
One for one on vestacp change IP manually.
Delete wrong Ip and add wrong ip, and change (other time) on VestaCP (because command not work) --> v-change-dns-domain-ip users sepd2020.domain.es 91.XXX.XXX.52
After correct manually all domains of users, investigate.
Ohhh. lol.
Vesta add config to interfaces but there're a mixings configuration. Wrong network and new netplan.
It is not the first time that I have problems with VestaCp, (and this will be the last one) related to cli commands, to strange problems.
Anyone know how to solve this mess, on a server with VestaCP. In one I already know how to do it, but in this I depend on the panel.
Regards.
In a vestaCp server based on Ubuntu 18.04, with nginx, and two ip in the system, a client calls me and tells me that everything has stopped working.
Well everything, no. Everything that was in your account that had an additional IP assigned.
That IP was missing. The server had not been restarted, but there had been a package update.
The terrible consequences, since vestacp depends terribly on nginx, and nginx had been out of order, since the IP does not exist in the system.
All right.
Steps
First get list of domains with IP no existent (91.XXX.XXX.53) to main ip.
Code: Select all
v-list-web-domains burcode | awk '{print $1}'> domains.txt # delete first lines no usables
for d in $(cat dominio.txt); do v-change-dns-domain-ip burcode $d 91.XXXX.XXX.52; done
One for one on vestacp change IP manually.
Delete wrong Ip and add wrong ip, and change (other time) on VestaCP (because command not work) --> v-change-dns-domain-ip users sepd2020.domain.es 91.XXX.XXX.52
After correct manually all domains of users, investigate.
Code: Select all
cat /etc/network/interfaces
ifupdown has been replaced by netplan(5) on this system. See
# /etc/netplan for current configuration.
# To re-enable ifupdown on this system, you can run:
# sudo apt install ifupdown
# Added by vesta
auto ens18:0
iface ens18:0 inet static
address 91.XXX.XXX.53
netmask 255.255.255.240
cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
ens18:
addresses:
- 91.XXX.XXX.52/28
gateway4: 91.121.226.62
nameservers:
addresses:
- 1.1.1.1
- 8.8.8.8
version: 2
Vesta add config to interfaces but there're a mixings configuration. Wrong network and new netplan.
It is not the first time that I have problems with VestaCp, (and this will be the last one) related to cli commands, to strange problems.
Anyone know how to solve this mess, on a server with VestaCP. In one I already know how to do it, but in this I depend on the panel.
Regards.