NetworkManager not working on CentOS or AlmaLinux? Here’s how to fix it step by step

📘 Introduction

On Linux distributions such as CentOS, AlmaLinux, or Rocky Linux, the NetworkManager service is essential for managing network connections, interfaces, and IP configurations.

However, it sometimes refuses to start, nmcli commands fail, or the service shows a status like “inactive (dead).”

Whether you’re a system administrator, technician, or simply a Linux user, this step-by-step guide will help you repair NetworkManager quickly and efficiently.

In this guide, you’ll learn how to:

• Check if the package is installed,
• Diagnose the service with systemctl,
• Handle conflicts between network and NetworkManager,
• And safely restart the service.

Ready? Let’s get started 👇

🔍 Step 1: Check if NetworkManager Is Installed

Start by confirming that the package is installed on your system:

rpm -qa | grep NetworkManager

No output? Then install it depending on your version:

• On AlmaLinux / CentOS 8+:

  sudo dnf install NetworkManager -y

• On CentOS 7:

  sudo yum install NetworkManager -y

🧩 Step 2: Verify That the Service Exists

systemctl list-unit-files | grep NetworkManager

You should see:

NetworkManager.service                 enabled

If nothing appears, the package may be incorrectly installed or removed. Reinstall it using one of the commands above.

🧩 Step 3: Check the Service Status

systemctl status NetworkManager

• Unit NetworkManager.service not found → The service is not installed.
• Active: inactive (dead) → The service is stopped.

In that case, enable and start it immediately:

sudo systemctl enable NetworkManager --now

⚠️ Step 4: Check for Conflicts with the network Service

The legacy network service can sometimes block NetworkManager. Check its status:

systemctl status network

If network is active, you have two options:

• Continue using the old network service, or
• Disable it and enable NetworkManager instead:

sudo systemctl disable network --now
sudo systemctl enable NetworkManager --now

🧠 Step 5: Read the Logs for Error Details

System logs often contain valuable hints. Analyze them using:

journalctl -xeu NetworkManager

You’ll see detailed error messages — such as service conflicts, missing dependencies, or corrupted files. Fix any issues before restarting the service.

🧪 Step 6: Test with nmcli

Finally, check if the NetworkManager daemon is running:

nmcli general status

Expected result: running

If you see:

Error: NetworkManager is not running.

Then restart it:

sudo systemctl restart NetworkManager

✅ Quick Command Summary

💬 FAQ: NetworkManager Won’t Start on CentOS / AlmaLinux

Why won’t NetworkManager start on CentOS?

The most common causes are a conflict with the network service, a missing package, or an incomplete installation.

How can I safely restart NetworkManager?

Use:

sudo systemctl restart NetworkManager

Then make sure it’s enabled:

sudo systemctl enable NetworkManager --now

How do I know if nmcli is working?

Run nmcli general status. If the output shows “running,” everything is fine.

What if the issue persists?

Inspect your configuration files under /etc/NetworkManager/system-connections/ and reboot the machine.

🏁 Conclusion

By following these steps, you can diagnose and fix most NetworkManager issues on CentOS and AlmaLinux.

If the problem persists, check your system logs and verify network dependencies. Once properly configured, NetworkManager ensures stable, reliable, and centralized network management across your Linux environment.