Resolving Server Inaccessibility After Reboot Post cPanel Installation


Symptoms

After installing cPanel on servers running AlmaLinux, CloudLinux, or Rocky Linux 8, you may encounter a situation where the server becomes inaccessible after a reboot.


Description

This issue arises because the NetworkManager service is disabled during the installation of cPanel software on these operating systems. Instead, the Network service is installed and configured. If there are customizations in the network-related configurations, they may conflict with the default settings of the Network service, preventing it from starting during boot. Consequently, rebooting the server makes it inaccessible.

As the root cause varies depending on these custom configurations, the most reliable workaround is to re-enable NetworkManager before rebooting the server after cPanel installation.


Workaround

If you encounter server inaccessibility after rebooting, you may still be able to access the server through alternative means like a VNC client, which some hosting providers include with their VPS or dedicated server plans. Using a VNC client allows you to interact with the server’s console directly, bypassing any network-related issues. Check with your hosting provider for details on using VNC.

Once you gain access to the server, follow the steps below to resolve the issue:


Step 1: Access the Server

Log in to the server as the root user using one of the following methods:

  • Via SSH or WHM Terminal: If network access is still functional.
  • Using VNC Client: If SSH is inaccessible due to the network issue. Consult your hosting provider for instructions on using VNC to connect to your server console.

Step 2: Disable the Network Service

Run the following command to disable the Network service:

/usr/bin/systemctl disable network

Step 3: Enable the NetworkManager Service

Enable the NetworkManager service using the command:

/usr/bin/systemctl enable NetworkManager

Step 4: Transition Services

Stop the Network service and start the NetworkManager service with this combined command:

/usr/bin/systemctl stop network; /usr/bin/systemctl start NetworkManager

Step 5: Reboot the Server

Finally, reboot the server to apply the changes:

shutdown -r now

Important Notes

  • This workaround assumes that the network configuration on your server is compatible with the NetworkManager service. If your server has custom network configurations, additional adjustments may be required.
  • By default, stock images of AlmaLinux, CloudLinux, and Rocky Linux are compatible with this workaround. Customizations to these images could require assistance from a system or network administrator.
  • VNC Client Tip: If you’re using a VNC client, ensure you have the necessary credentials and tools provided by your hosting provider.

Conclusion

Re-enabling the NetworkManager service is a reliable solution to prevent server inaccessibility after a cPanel installation. Using tools like a VNC client ensures you can access your server even when traditional network methods fail. For persistent issues, consider consulting your hosting provider or a system administrator.