Plesk fails to add aditional IP

[pdsolutions1]

Hello,

I have the latest plesk version 12.5 with centos7, on adding a new IPV4 and IPV6 adresses on Tools&settings -> Ip ... add new -> xx.xx.xx.xx/32 for dedicated IV4 and xx.xx.xx.xx.xx/64 for IPV6
Restarting the server, nginx dosen t start with error: "nginx emerg bind() to 443 failed (99 cannot assign requested address)" the error includes the NEW IP6 wich i checked with the provider support team and is correct.
So, searching for similar issues, i fond this: http://kb.odin.com/en/114245 "Nginx does not start after IP change" -> In my case, i don't need an IP change, i just want to add some other Ip's in order to set different Ip's on webpages i host. BUT, the fix is working till a new reboot. So after the fix, if i reboot the machine ngnix will fail again with same error.

1. How can i make the fix permanent?
2. If i have two ip's on same dedicated server, plesk dosen't create another interface, i have them both on eth0
3. The /etc/hosts file dosen't contain the new IPV4 and IPV6
...

How can i fix this?

Thanks

https://talk.plesk.com/threads/nginx-dosen-t-start-on-adding-other-ip-addresses.337059/

 

[Kingsley]

Hello;

I added my additional IP via /etc/network/interface on ubuntu 14 then i click on re-read IP from the ip addresses setup page and it was picked up.... maybe you should add it to centos first.

 

[Amin Taheri]

You can add it from the Plesk UI to the machine or from the CLI

the CLI command is
plesk bin ipmanage -c 10.0.0.0
(replace with your IP of course)


One thing I do is this
plesk bin ipmanage --auto-remap-ip-addresses true
plesk bin ipmanage --reread

This will cause Plesk to re-read and configure the IPs each time it restarts

 

[pdsolutions1]

Thanks guys,

But i saw something strange in the Plesk IP manager (please see attached img)
I have all on eth0 !!!
How can i create a new interface, i think it fails cause there are both on the same eth0. There is no other interface...

ifconfig ssh command returns:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xxx.xxx.108.200 netmask 255.255.255.255 broadcast xxx.xxx.108.200
inet6 xxxx::xxx:xxxx:fe72:8d38 prefixlen 64 scopeid 0x20<link>
inet6 xxxx:xxx:91e:3b00::61:1cfc prefixlen 64 scopeid 0x0<global>
inet6 xxx:xxx:91e:3b77:a905:2d17:f52b:f546 prefixlen 64 scopeid 0x0<g lobal>
ether 00:25:90:72:8d:38 txqueuelen 1000 (Ethernet)
RX packets 28836182 bytes 17503996503 (16.3 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29185889 bytes 15409916370 (14.3 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 memory 0xfe9e0000-fea00000

eth0:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xxx.38.191 netmask 255.255.255.255 broadcast xx.xxx.255.255
ether 00:25:90:72:8d:38 txqueuelen 1000 (Ethernet)
device interrupt 17 memory 0xfe9e0000-fea00000

eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:25:90:72:8d:39 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18 memory 0xfeae0000-feb00000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 4792215 bytes 10193824547 (9.4 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4792215 bytes 10193824547 (9.4 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0



Thanks

 

[Amin Taheri]

So each of the ethX (eth0 eth1 etc) are separate network cards - either physical or virtual. You don't really need new ones.

Generally having them setup as aliases (like eth0:1, eth0:2, etc) is the route to go.
I have boxes with over a dozen IPs just on eth0 and they work fine.

However with that said, if you want to add them into the eth1 interface you would specify which interface you want the IP on when you add it.

plesk bin ipmanage -c 10.10.10.10 -type exclusive -mask 255.255.255.0 -interface eth1