Fix “Failed to Start Network Manager” on Ubuntu 22.04
A broken network on a Linux server can feel like losing the keys to your own house. If you’re seeing the error “Failed to Start Network Manager” on Ubuntu 22.04, you’re not alone — and there’s a straightforward fix.
Whether you’re managing Ubuntu locally or on a virtual server like a Linux VPS, this guide walks you through the real causes and tested methods to restore connectivity.
Why Ubuntu 22.04 Shows “Network Manager Failed to Start”
Before diving into commands, it helps to know what’s actually happening. The error usually appears when the NetworkManager service can’t launch during boot or after configuration changes. Common reasons include:
● Broken or missing configuration files in /etc/NetworkManager/NetworkManager.conf
● Conflicts between Netplan and legacy ifupdown network settings
● Disabled or masked systemd service
● Corrupted cache or incomplete system updates
You can confirm the problem with:
systemctl status NetworkManager.service
If the output shows “failed” or dependency errors, move on to the fixes.
How to Fix NetworkManager on Ubuntu 22.04
Let’s go step by step. These methods are safe for most environments, including servers and desktop editions.
1. Restart and Enable the Network Manager Service
sudo systemctl restart NetworkManager
sudo systemctl enable NetworkManager
Then verify:
sudo systemctl active NetworkManager
If it returns “active,” your connection should be working again.
2. Check and Rebuild the Configuration File
Open the file:
sudo nano /etc/NetworkManager/NetworkManager.conf
Ensure it includes:
[main]
plugins=ifupdown,keyfile
plugins=ifupdown,keyfile
Save, exit, and reload:
sudo systemctl daemon-reexec
3. Fix Netplan and NetworkManager Conflicts
Ubuntu 22.04 uses Netplan for network configuration, which sometimes conflicts with NetworkManager. Check your YAML files:
cat /etc/netplan/*.yaml
If you see renderer: networkd, and you’re relying on NetworkManager, change it to:
renderer: NetworkManager
Then regenerate and apply:
sudo netplan generate
sudo netplan apply
4. Clear NetworkManager Cache
Sometimes cached settings block the service:
sudo rm -rf /var/lib/NetworkManager/*
sudo systemctl restart NetworkManager
5. Reinstall Network Manager
If nothing else works, reinstall the package:
sudo apt update
sudo apt install --reinstall network-manager
Repair any broken dependencies:
sudo apt --fix-broken install
6. Test Your Network
Once restarted, test connectivity:
ping -c 3 8.8.8.8
If there’s no response, check DNS:
cat /etc/resolv.conf
If it’s empty, add:
nameserver 1.1.1.1
Advanced Troubleshooting
Still seeing the same message? Try these additional steps:
● Rebuild system daemons:
sudo systemctl daemon-reload
● Verify hostnames and DNS files aren’t missing (/etc/hosts, /etc/resolv.conf).
● Reboot and watch logs:
journalctl -xe | grep NetworkManager
These checks often uncover permission issues or leftover temporary files from failed updates.
Preventing NetworkManager Errors
Once the system is running again, a few small habits can save you from repeating the problem:
● Don’t mix Netplan and /etc/network/interfaces; stick to one method.
● Always back up configuration files before editing.
● After updates, reboot to apply all new systemd dependencies.
● Use systemctl daemon-reload after any manual edits.
Conclusion
The “Failed to Start Network Manager” error in Ubuntu 22.04 is frustrating but rarely fatal. Most of the time, it comes down to a small misconfiguration or conflict between Netplan and NetworkManager. By methodically restarting the service, cleaning cache, and fixing YAML settings, you can restore networking within minutes.
If you frequently manage remote environments or run multiple servers, keeping a clean and properly configured Linux VPS ensures your systems stay connected — without constant troubleshooting.