After a VPS snapshot restore I have an additional eth0:cp1 causing NAT issues with auto ssl

brunocerq

Registered
Jul 15, 2020
3
0
1
Portugal
cPanel Access Level
Root Administrator
I had to made a restore from a snapshot in a google compute engine VPS, but now in ifconfig I see the same internal IP address both on eth0 and eth0:cp1, I started to receive auto ssl messages " Loopback NAT on this IP address appears to be defective "

ifconfig:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1460
inet 10.142.0.14 netmask 255.255.255.255 broadcast 10.142.0.14
inet6 fe80::4001:aff:fe8e:e prefixlen 64 scopeid 0x20<link>
ether 42:01:0a:8e:00:0e txqueuelen 1000 (Ethernet)
RX packets 327969 bytes 242538668 (231.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 399658 bytes 717565245 (684.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0:cp1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1460
inet 10.142.0.14 netmask 255.255.255.0 broadcast 10.142.0.255
ether 42:01:0a:8e:00:0e txqueuelen 1000 (Ethernet)

Running ip addr | grep inet I get:
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
inet 10.142.0.14/32 brd 10.142.0.14 scope global dynamic eth0
inet 10.142.0.14/24 brd 10.142.0.255 scope global eth0:cp1
inet6 fe80::4001:aff:fe8e:e/64 scope link

Why do I have 2 internal local IP's here when I only have 1 physical local IP and 1 external IP in the VPS?

In WHM, if I go to "Show or Delete Current IP Addresses" :

NAT Mode
Interface Local IP Notes Public IP
eth0:cp1 10.142.0.14 Main/shared IP for: xxxxxxx 104.196.xxx.xxx

I really don't know how to fix this, I run this server for web applications, network administration is not my thing, any help would be appreciated.
 
Last edited by a moderator:

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
7,492
1,008
313
cPanel Access Level
Root Administrator
Hey there! Network administration isn't really cPanel's thing either, as we just read that data directly from the operating system. It might be best to contact the hosting provider or datacenter to have them check the server's configuration to see why the IPs were arranged like they are after the restore.