• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Problem with network connections and IPs

MatejM

New Pleskian
We are running CentOS 6.4 with minimal desktop environment and plesk. When we build the server we had only 2 IPs x.x.x.42 (primary) and x.x.x.45 (shared). Now after adding a third IP (shared) via Plesk control panel problems appear.

Under default CentOS network manager, plesk created these connections:
eth0 (this should be the primary connection, it has the primary IP, gateway and other settings)
System eth0:1 (only the x.x.x.45 shared IP)
System eth0:2 (only the newly added x.x.x.46 shared IP)

After every server restart, CentOS chooses the System eth0:2 as an active connection. Then the errors start to pop up:

Unable to configure a web server on the host <xxx>
nginx: [emerg] bind() to x.x.x.45:80 failed (99: Cannot assign requested address)
nginx: configuration file /etc/nginx/nginx.conf test failed

Unable to configure a web server on the host <xxx>
nginx: [emerg] bind() to x.x.x.46:80 failed (99: Cannot assign requested address)
nginx: configuration file /etc/nginx/nginx.conf test failed

After that none of the other services work (bind, mail, ...)


To fix this, we must manually set eth0 as the active network connection, then go to Plesk control panel under IP management, choose the option to reread the IPs and then to repair IPs x.x.x.45 and x.x.x.46. After that is done, everything starts working again.

I would greatly appreciate any advice you can give me. I'm really not a Linux expert and have great trouble understanding networking in linux. I found 3 sets of network configuration files (with identical settings) under 3 directories and have no idea which one are actually in use.
 
I'm sorry for bumping the thread but this is a very serious problem and we really need some advice.
 
Back
Top