The ticket has been escalated so there isn't anything else I can do on my end. The licensed IP is locked due to the number of reinstalls.
At this point you'll need to wait until the ticket is addressed.
At this point you'll need to wait until the ticket is addressed.
Hi there,
I have the same issue with installing cPanel on a fresh CentOS 8.3 installation.
After reboot, the server is not reachable.
Have you solved the issue?
I have the same issue with installing cPanel on a fresh CentOS 8.3 installation.
After reboot, the server is not reachable.
Have you solved the issue?
We have opened case CPANEL-37451 with our developers to have them explore the issues that some users are reporting with the CentOS 8 installations. At this time I don't have any additional details.
Could you submit a ticket to our team so we can check that directly on the system?
Could you submit a ticket to our team so we can check that directly on the system?
Hi CPRex,
I've encountered the same problem now on a new installation (CentOS 8.3), any news on this topic, or should I submit a new ticket?
I'm currently using a workaround by using a remote console to connect to the server, shut down interface eno1 and start NetworkManager again, all problems solved until restart.
kind regards,
Sven B. 8)
There aren't any updates to that case. At this time we've decided not to make any adjustments to the installer. Could you submit a ticket so we can check it out?
Hello,
These last few days I encountered a similar problem, we are migrating servers to Google Cloud and taking the opportunity to upgrade to Almalinux 8/Cloudlinux 8.
I found that when the cPanel installation script deactivates NetworkServices and activates network.service it does not automatically create the ifcfg-ethX file, only the ifcfg-lo in /etc/sysconfig/network-scripts/. As the instance has no network adapter, it is obviously not possible to connect to it except by serial port.
To solve it I did the following:
Find out and write down network adapter data
Write down the mac of the adapter eth0 (in my case, this may vary), it may also be necessary to write down the ip if they have fixed ip, in my case I use DHCP.
Disable NetworkService
Install network.service
Manually create the ifcfg-ethX file
In some cases the adapter name may be different, make the necessary corrections.
Add the necessary configuration, save and exit. In my case it is this:
Install cPanel with the considerations and instructions from the guide Installation | cPanel & WHM Documentation
After rebooting it seems to work correctly
These last few days I encountered a similar problem, we are migrating servers to Google Cloud and taking the opportunity to upgrade to Almalinux 8/Cloudlinux 8.
I found that when the cPanel installation script deactivates NetworkServices and activates network.service it does not automatically create the ifcfg-ethX file, only the ifcfg-lo in /etc/sysconfig/network-scripts/. As the instance has no network adapter, it is obviously not possible to connect to it except by serial port.
To solve it I did the following:
Find out and write down network adapter data
Bash:
ip aDisable NetworkService
Bash:
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
systemctl mask NetworkManager.service
Bash:
dnf install epel-release
dnf install network-scripts
systemctl enable networkIn some cases the adapter name may be different, make the necessary corrections.
Bash:
cd /etc/sysconfig/network-scripts
touch ifcfg-eth0
chmod 644 ifcfg-eth0
vi ifcfg-eth0
Code:
BOOTPROTO=dhcp
DEVICE=eth0
HWADDR=XX:XX:XX:XX:XX:XX
ONBOOT=yes
TYPE=EthernetAfter rebooting it seems to work correctly
Last edited:
Same problem here
Installed Centos 8, rebooted, then ran the script to convert it to Almalinux, rebooted again, installed cpanel and after reboot, there is no network! So it was cpanel install who broke the network configuration
Surprised this is here since 3 months ago and no solution published
Edit: The problem happens even when i manually disable networkmanager and enable network.service using the instructions provided by cpanel or other websites (the same instructions are everywhere, just disable networkmanager, and install and enable network.service).
Happens even installing Centos 8 with an ISO. Maybe latest Centos 8 completely deprecated network.service?
Solved: In my case, the default network configuration was not valid with network.service, prefix 32 which was valid with network manager and centos 7 with network.service turned invaled with centos 8, prefix 26 worked, don't know why.
Installed Centos 8, rebooted, then ran the script to convert it to Almalinux, rebooted again, installed cpanel and after reboot, there is no network! So it was cpanel install who broke the network configuration
Surprised this is here since 3 months ago and no solution published
Edit: The problem happens even when i manually disable networkmanager and enable network.service using the instructions provided by cpanel or other websites (the same instructions are everywhere, just disable networkmanager, and install and enable network.service).
Happens even installing Centos 8 with an ISO. Maybe latest Centos 8 completely deprecated network.service?
Solved: In my case, the default network configuration was not valid with network.service, prefix 32 which was valid with network manager and centos 7 with network.service turned invaled with centos 8, prefix 26 worked, don't know why.
Last edited:
Have also exact the same problem, clean install of Centos 8.4, after installation od cpanel and one reboot, no network, no access to SSH, nothing.
Tried to exclude kernel updates, convert to Cloudlinux, nothing helps.
update - tried with network conf prefix 26 - did not help
Happens even without restart:
# reboot
Failed to connect to bus: No such file or directory
Failed to open initctl fifo: No such device or address
Failed to talk to init daemon.
# uname -r
4.18.0-305.7.1.el8_4.x86_64
# nmcli
Error: Could not create NMClient object: Could not connect: Success.
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 7c:10:c9:21:f3:2a brd ff:ff:ff:ff:ff:ff
# netstat -i
Kernel Interface table
Iface MTU RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
enp8s0 1500 286917 0 0 0 60797 0 0 0 BMRU
lo 65536 161 0 0 0 161 0 0 0 LRU
and then SSH connection broke, remote reset did nothing, server unavailable
Tried to exclude kernel updates, convert to Cloudlinux, nothing helps.
update - tried with network conf prefix 26 - did not help
Happens even without restart:
# reboot
Failed to connect to bus: No such file or directory
Failed to open initctl fifo: No such device or address
Failed to talk to init daemon.
# uname -r
4.18.0-305.7.1.el8_4.x86_64
# nmcli
Error: Could not create NMClient object: Could not connect: Success.
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 7c:10:c9:21:f3:2a brd ff:ff:ff:ff:ff:ff
# netstat -i
Kernel Interface table
Iface MTU RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
enp8s0 1500 286917 0 0 0 60797 0 0 0 BMRU
lo 65536 161 0 0 0 161 0 0 0 LRU
and then SSH connection broke, remote reset did nothing, server unavailable
Last edited:
Hello! I think it would be best to open a support ticket so that our analysts can review the issue more thoroughly and determine what exactly is occurring. You will need to work with your system administrator or hosting provider for assistance in getting the server back up.
Once the server is back up, you can submit a support request using the "Submit a ticket" link in my signature below.
Please be sure to link this thread when opening the ticket and provide the ticket number here so that we can track the issue appropriately. If possible, please post the resolution on this thread as it may help other community members with similar issues.
Once the server is back up, you can submit a support request using the "Submit a ticket" link in my signature below.
Please be sure to link this thread when opening the ticket and provide the ticket number here so that we can track the issue appropriately. If possible, please post the resolution on this thread as it may help other community members with similar issues.
@dbanovski - I see our team did reply to that ticket and let you know of one possible explanation. In general, installing cPanel would not break the network connection to the server, so it is likely something else related to that process.
that's easy to solve this issue on almalinux or Centos 8 regurd the lose connection after Cpanel installation and reboot the OS
only you need to login into SSH and disable the firewaill system for both Almalinux and Cenos 8
use this commend
sudo systemctl disable firewalld
only you need to login into SSH and disable the firewaill system for both Almalinux and Cenos 8
use this commend
sudo systemctl disable firewalld
