Network is unreachable in CentOS 7 after cPanel install + restart

Sykoi

September 26, 2018 14:25

I followed the instructions here to disable the network manager, I installed cPanel and got it working fine. I added extra IP addresses then restarted the server. Now when I try to ping 8.8.8.8 on the server through proxmox's console I get 'Network is unreachable', and I'm unable to connect to the server remotely. My ifcfg-eth0 file:


    TYPE="Ethernet"
    PROXY_METHOD="none"
    BROWSER_ONLY="no"
    BOOTPROTO="none"
    DEFROUTE="yes"
    IPV4_FAILURE_FATAL="no"
    NAME="eth0"
    UUID=...
    DEVICE="eth0"
    ONBOOT="yes"
    HWADDR=My Virtual Mac from OVH
    IPADDR=IP assigned to VPS
    PREFIX="32"
    GATEWAY=Correct gateway for my OVH server
    DNS1=8.8.8.8
    DNS2=8.8.4.4

When I run ifconfig -a (Shortening to relevant parts):


    eth0: ...
    inet IPOfVPS netmask 255.255.255.255 broadcast: IPOfVPS
   
    eth0cp1-4:
    inet IPs netmask 255.255.255.0 broadcast: IP but with .255 as the last number

I had to retype everything manually since I can't copy/paste from proxmox's console, but the relevant information should be there. If anymore information is needed, let me know in a comment. To be clear: Networking was working until I restarted, which I only did after finishing the cPanel install and adding additional IPs. I'm also using the latest version of everything - I just installed cPanel last night.

Comments

19 comments

cPanelMichael

October 01, 2018 14:06
Hello @Sykoi, Can you open a
0
Sykoi

October 01, 2018 14:13
After testing, I've figured out the problem exists regardless of a cPanel install - it's purely the turning off NetworkManager that does it.
0
cPanelMichael

October 01, 2018 14:23
After testing, I've figured out the problem exists regardless of a cPanel install - it's purely the turning off NetworkManager that does it.

Hi @Sykoi, I appreciate the additional information. I'd like to reproduce this behavior so we can add a note to our
0
Sykoi

October 01, 2018 14:25
Here's the steps to reproduce it: I installed CentOS 7 using the minimal ISO on my Proxmox VPS (Hosted on SoYouStart / OVH - noted since they have weird networking policies), configured my ifcfg-eth0 file. After that I was able to use yum update, ping 8.8.8.8, connect via SSH, etc. After following
Host: cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 9 (stretch)" NAME="Debian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
Guest: cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7"
@cPanelMichael can you keep me updated on the issue?
0
Fernando V

October 02, 2018 02:26
@cPanelMichael can you keep me updated on the issue?

You have to create a Failover IP and assign a virtual MAC to said Failover IP. Read the OVH documentation. Regards.
0
Sykoi

October 02, 2018 14:09
You have to create a Failover IP and assign a virtual MAC to said Failover IP. Read the OVH documentation. Regards.

I did both
0
Fernando V

October 02, 2018 18:20
I did both

Do you restart the network afterwards so that the changes are applied? # sudo systemctl restart network.service
Put the results here, removing sensitive data. Verify new IP settings: # ip addr
# ip a s eth0
Verify new routing settings: # ip r
Verify DNS servers settings: # cat /etc/resolv.conf
Verify the internet connectivity: # ping -c 3 cpanel.net
More info:
0
Sykoi

October 03, 2018 02:16
ip addr: (Ignoring lo) eth0: ip r 169.254.0.0/16 dev eth0 scope link metric 1002 first 3 numbers of vps ip then .0/24 dev eth0 proto kernel scope link src vpsip cat /etc/resolv.conf nameserver 8.8.8.8 nameserver 8.8.4.4 ping -c 3 cpanel.net ping: cpanel.net: Name or service not known
0
cPanelMichael

October 24, 2018 12:18
I installed CentOS 7 using the minimal ISO on my Proxmox VPS (Hosted on SoYouStart / OVH - noted since they have weird networking policies), configured my ifcfg-eth0 file. After that I was able to use yum update, ping 8.8.8.8, connect via SSH, etc. After following
0
Suertzz

May 17, 2019 00:33
Hi @Sykoi, I have exactly the same problem as you, after disabling Network manager, install cpanel and restart the server I lost internet (installation under proxmox with quemu, ip failover OVH, Centos 7). I searched everywhere and found nothing conclusive, did you find a solution please ? Thank in advance :(
0
cPanelMichael

May 17, 2019 21:55
I have exactly the same problem as you, after disabling Network manager, install cpanel and restart the server I lost internet (installation under proxmox with quemu, ip failover OVH, Centos 7). I searched everywhere and found nothing conclusive, did you find a solution please ?

Hello @Suertzz, Can you open a
0
cmdrspock

August 19, 2019 22:16
Hate to necro a thread but this was the only thing that came up on Google while I was figuring this one out for myself. Turns out, if you disable network manager the OS has no idea what to do with your gateway information - and this is essential for failover IPs to work on OVH without a vRack. To fix it simply - open /etc/sysconfig/network-scripts/route-[COLOR=rgb(44, 130, 201)]eth0 (replacing [COLOR=rgb(44, 130, 201)]eth0 with your network device). In that file, put (replacing [COLOR=rgb(184, 49, 47)]x.x.x.x with your gateway IP and [COLOR=rgb(44, 130, 201)]eth0 with your network device): [QUOTE][COLOR=rgb(184, 49, 47)]x.x.x.x dev [COLOR=rgb(44, 130, 201)]eth0 default via [COLOR=rgb(184, 49, 47)]x.x.x.x dev [COLOR=rgb(44, 130, 201)]eth0
0
Spinetta

January 08, 2020 23:34
Hate to necro a thread but this was the only thing that came up on Google while I was figuring this one out for myself. Turns out, if you disable network manager the OS has no idea what to do with your gateway information - and this is essential for failover IPs to work on OVH without a vRack. To fix it simply - open /etc/sysconfig/network-scripts/route-[COLOR=rgb(44, 130, 201)]eth0 (replacing [COLOR=rgb(44, 130, 201)]eth0 with your network device). In that file, put (replacing [COLOR=rgb(184, 49, 47)]x.x.x.x with your gateway IP and [COLOR=rgb(44, 130, 201)]eth0 with your network device):

I'm not even going to apologize for necroing this thread because I've been googling my butt off for 4 days & this is the ONLY solution out of about 50 supposed working solutions that works with CentOS7. I had to create the route-eth0 file manually, added the lines as indicated, configured the ifcfg-eth0 according to OVH's Wiki and voila, it works! Thank you SO much. I have literally been at this for 4 days, 12 hours a day & there is NOTHING but this thread out there on how to get cPanel to work with OVH Failover IPs that actually works but this. In our case we're running a SoYouStart Dedicated Server with Windows 2016 Datacenter as the host & CentOS7 w/ cPanel in VirutalBox. Make sure you also set the VM to use the Virtual MAC you have to manually generate through the OVH / SYS control panel. Never been so happy to have someone necro a thread but I really can't thank you enough. We're up & running with 24 hours to spare before I lose this contract. You just saved my job.
0
jndawson

February 10, 2020 22:46
Hate to necro a thread but this was the only thing that came up on Google while I was figuring this one out for myself. Turns out, if you disable network manager the OS has no idea what to do with your gateway information - and this is essential for failover IPs to work on OVH without a vRack. To fix it simply - open /etc/sysconfig/network-scripts/route-[COLOR=rgb(44, 130, 201)]eth0 (replacing [COLOR=rgb(44, 130, 201)]eth0 with your network device). In that file, put (replacing [COLOR=rgb(184, 49, 47)]x.x.x.x with your gateway IP and [COLOR=rgb(44, 130, 201)]eth0 with your network device):

I have been trying to figure out what went wrong after rebooting to configure quotas after installation, and this is the only thing that has worked. So, thanks!
0
mshannaq

July 11, 2020 06:36
Hate to necro a thread but this was the only thing that came up on Google while I was figuring this one out for myself. Turns out, if you disable network manager the OS has no idea what to do with your gateway information - and this is essential for failover IPs to work on OVH without a vRack. To fix it simply - open /etc/sysconfig/network-scripts/route-[COLOR=rgb(44, 130, 201)]eth0 (replacing [COLOR=rgb(44, 130, 201)]eth0 with your network device). In that file, put (replacing [COLOR=rgb(184, 49, 47)]x.x.x.x with your gateway IP and [COLOR=rgb(44, 130, 201)]eth0 with your network device):

Thank you alot this help me to fix the problem while installing Cpanel on Proxmox VM.
0
mshannaq

March 30, 2021 14:35
Hate to necro a thread but this was the only thing that came up on Google while I was figuring this one out for myself. Turns out, if you disable network manager the OS has no idea what to do with your gateway information - and this is essential for failover IPs to work on OVH without a vRack. To fix it simply - open /etc/sysconfig/network-scripts/route-[COLOR=rgb(44, 130, 201)]eth0 (replacing [COLOR=rgb(44, 130, 201)]eth0 with your network device). In that file, put (replacing [COLOR=rgb(184, 49, 47)]x.x.x.x with your gateway IP and [COLOR=rgb(44, 130, 201)]eth0 with your network device):

any one know how to solve this on Centos8 I have the same problem on Centos8 and creating a new file etc/sysconfig/network-scripts/route-eth0 does not solve the problem
0
cPRex Jurassic Moderator

March 31, 2021 20:51
@mshannaq - our documentation at How to Disable Network Manager | cPanel & WHM Documentation says this: "On systems that run CentOS 8 or AlmaLinux 8, the cPanel & WHM installer will automatically disable the Network Manager service and enable the network.service service." If you're not seeing that working properly can you please open a ticket with our team so we can check that configuration on your server?
0
rg49

April 13, 2021 15:32
Hate to necro a thread but this was the only thing that came up on Google while I was figuring this one out for myself. Turns out, if you disable network manager the OS has no idea what to do with your gateway information - and this is essential for failover IPs to work on OVH without a vRack. To fix it simply - open /etc/sysconfig/network-scripts/route-[COLOR=rgb(44, 130, 201)]eth0 (replacing [COLOR=rgb(44, 130, 201)]eth0 with your network device). In that file, put (replacing [COLOR=rgb(184, 49, 47)]x.x.x.x with your gateway IP and [COLOR=rgb(44, 130, 201)]eth0 with your network device):

Genius! Problem still here 2 years later. After cpanel install, I lost the network and nobody at support was able to help me... Appears they didn't hear about this for proxmox users (I'm a scaleway customer, not OVH).
0
did-vmonroig

August 02, 2021 13:41
any one know how to solve this on Centos8 I have the same problem on Centos8 and creating a new file etc/sysconfig/network-scripts/route-eth0 does not solve the problem

Solved with Almalinux 8. Still works creating a route-XXX file.
0

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?