cPanel install on fresh AlmaLinux 8.6 network ipv4 issues

JIKOmetrix

Well-Known Member
Apr 3, 2007
184
34
178
Hello,

I have an install on an OVH server. It started out as a Fresh AlmaLinux 8.6 install. After AlmaLinux is imaged. I can reboot server and networking works fine.

I run the traditional "cd /home && curl -o latest -L https://securedownloads.cpanel.net/latest && sh latest" as root.

cPanel installs and says I can configure on https://[ip address]:2087.

I begin configuration all seems fine.

Then I reboot the server to get quotes setup and the IPV4 networks is not getting an IP. I can no longer SSH in. I only access the server via the KVM now.

Any idea on why the network would get hosed up after cPanel install and reboot?

Thanks,
Mike
 
Last edited by a moderator:

ejsolutions

Well-Known Member
Jan 6, 2013
77
32
68
cPanel Access Level
Root Administrator
You did have a fixed IP set?
NetworkManager is automaticcaly disabled now, to be replaced by network.service. Perhaps it didn't enable the network.service
 

JIKOmetrix

Well-Known Member
Apr 3, 2007
184
34
178
You did have a fixed IP set?
NetworkManager is automaticcaly disabled now, to be replaced by network.service. Perhaps it didn't enable the network.service
I was not aware that NetworkManager was disabled now on install. This must be my issue since the data center does DHCP their primary static addresses to the NIC MAC address. I'll configure the server with static IP and test.

Thank you for the heads up.

- Mike
 
  • Like
Reactions: cPRex

JIKOmetrix

Well-Known Member
Apr 3, 2007
184
34
178
Hello,

I configured the static IP for the server with help from here:

As you said the NetworkManager is disabled. When I used ifdown and ifup to init the interface I received error messages saying that I should use NetworkManager instead of the ifdown and ifup network scripts since the are depricated and will be removed.

The initi of the interface with static IP worked well. I can now access the server and complete my configuration.

I'm confused about NetworkManager. Should it be left disabled or should it be enabled?

- Mike
 

ejsolutions

Well-Known Member
Jan 6, 2013
77
32
68
cPanel Access Level
Root Administrator
Ludicrous to have/expect a dynamic IP for a server.
NetworkManager should remain disabled - network.service replaces it, as I previously alluded to.

> systemctl restart network

System Requirements for AlmaLinux OS | cPanel & WHM Documentation - embolding of no DHCP is clear.
Having relatively recently reinstalled a server with Almalinux, I do recall seeing a mention of the automatic replacement of NetworkManager; just can't remember where..
[Edit: think it may actually have been a re-installation of CWP.]

Edit2: Here's a guide/explanation for CentOS that can also apply to Almalinux..
 
Last edited:

JIKOmetrix

Well-Known Member
Apr 3, 2007
184
34
178
Ludicrous to have/expect a dynamic IP for a server.
NetworkManager should remain disabled - network.service replaces it, as I previously alluded to.

> systemctl restart network

System Requirements for AlmaLinux OS | cPanel & WHM Documentation - embolding of no DHCP is clear.
Having relatively recently reinstalled a server with Almalinux, I do recall seeing a mention of the automatic replacement of NetworkManager; just can't remember where..
[Edit: think it may actually have been a re-installation of CWP.]

Edit2: Here's a guide/explanation for CentOS that can also apply to Almalinux..
Thank you