How to Fix “Activation of Network Connection Failed” Error

The message “Activation of network connection failed” commonly appears on Linux systems using NetworkManager, including Ubuntu, Fedora, Linux Mint, Debian-based distributions, and GNOME or KDE desktops. It usually means your computer tried to enable a Wi-Fi, Ethernet, VPN, or mobile broadband connection but could not complete the process. The cause may be as simple as a router issue or as technical as a driver, DHCP, DNS, or NetworkManager configuration problem.

1. Start with the basic checks

Before changing system files or reinstalling drivers, confirm that the problem is not caused by hardware or a temporary network outage. Many connection failures happen because the router is unavailable, the password has changed, or the device is trying to connect to a stale saved profile.

• Restart your router or modem. Unplug it for 30 seconds, reconnect it, and wait until all status lights stabilize.
• Toggle Wi-Fi off and on. Use your desktop network menu or a hardware Wi-Fi key if your laptop has one.
• Try another network. A phone hotspot is useful for testing whether the issue is your computer or the original network.
• Check Airplane Mode. Make sure it is disabled in system settings and, if applicable, in your laptop’s BIOS or function keys.
• Confirm the password. If the Wi-Fi password was changed on the router, Linux may keep trying the old stored credential.

2. Restart NetworkManager

NetworkManager controls most desktop Linux connections. If it becomes stuck, restarting the service can resolve the error without changing your configuration.

Open a terminal and run:

sudo systemctl restart NetworkManager

Then try to connect again. If you want to confirm that the service is active, run:

systemctl status NetworkManager

You should see an active status. If the service is failed or disabled, start and enable it:

sudo systemctl enable --now NetworkManager

Note: On some minimal or server-oriented installations, another network service may be managing connections, such as systemd-networkd. Running multiple network managers at the same time can cause conflicts.

3. Forget and recreate the connection profile

A corrupted or outdated saved connection profile is one of the most common causes of this error. Removing the profile forces Linux to create a fresh one with current settings.

Using the graphical interface, open Settings, go to Wi-Fi or Network, select the problematic connection, and choose Forget or Delete. Then reconnect and enter the password again.

You can also do this from the terminal. First list saved connections:

nmcli connection show

Delete the problematic profile:

nmcli connection delete "Connection Name"

Then reconnect using your desktop network menu or with nmcli. For Wi-Fi, you can use:

nmcli device wifi list
nmcli device wifi connect "SSID" password "YourPassword"

4. Check whether the network device is detected

If Linux cannot see the network adapter correctly, the connection will fail no matter how many times you try to activate it. Check available devices with:

nmcli device status

Look for your Wi-Fi or Ethernet device. A healthy device usually appears as wifi or ethernet. If it says unavailable, unmanaged, or does not appear at all, the issue may involve drivers, firmware, or device management.

For hardware details, run:

lspci | grep -i network
lsusb

These commands help identify internal PCI adapters and USB network adapters. If your Wi-Fi card is listed but not working, you may need a proprietary or additional firmware package. This is especially common with some Broadcom, Realtek, and Intel wireless chipsets.

5. Check for a blocked wireless adapter

Linux may report a Wi-Fi device as blocked, either by software or hardware. Use:

rfkill list

If you see Soft blocked: yes, unblock it:

sudo rfkill unblock wifi

If you see Hard blocked: yes, check for a physical wireless switch, a function key combination such as Fn + F2, or a BIOS/UEFI setting. A hard block cannot usually be fixed by software alone.

6. Verify IP address and DHCP settings

Network activation can fail if your computer cannot obtain an IP address from the router. This is typically a DHCP issue. First, check whether an IP address was assigned:

ip addr

If your active interface has no normal local IP address, such as one beginning with 192.168, 10., or 172.16-31, renew the connection:

sudo dhclient -r
sudo dhclient

If you use a static IP address, make sure the address, gateway, subnet mask, and DNS servers are correct. A wrong gateway or duplicate IP address can prevent activation or make the connection appear active but unusable.

7. Examine DNS settings

DNS problems usually do not stop a connection from activating, but they can make it look as if the network failed because websites will not load. Check DNS resolution with:

resolvectl status

If DNS is missing or incorrect, set a known DNS provider temporarily in your connection settings. Common choices include 1.1.1.1, 8.8.8.8, or your router’s IP address. For long-term reliability, configure DNS through NetworkManager rather than manually editing temporary resolver files.

8. Review logs for the real cause

If the usual fixes do not work, logs can show the exact reason the activation failed. Run:

journalctl -u NetworkManager -b

Look for messages related to authentication, DHCP timeout, missing firmware, unmanaged devices, or carrier detection. For Wi-Fi, authentication failures often indicate a wrong password, incompatible security mode, or a saved profile using old credentials. For Ethernet, messages about no carrier usually mean the cable, port, adapter, or switch is not detecting a physical link.

9. Update or reinstall network drivers and firmware

If the adapter is detected inconsistently or disappears after suspend, update your system packages. On Ubuntu, Linux Mint, or Debian-based systems, run:

sudo apt update
sudo apt upgrade

On Fedora, use:

sudo dnf upgrade

After updating, reboot. If your distribution provides a Driver Manager or Additional Drivers tool, open it and install the recommended driver for your wireless chipset. Avoid downloading random driver archives from unverified websites. Network drivers run at a low system level, so using trusted distribution packages is safer and more stable.

10. Check for configuration conflicts

Advanced users sometimes configure networking manually, then later use NetworkManager. Conflicts can cause the activation error. Check whether your interface is marked as unmanaged:

nmcli device status

If the device is unmanaged, review NetworkManager configuration files, especially in:

/etc/NetworkManager/NetworkManager.conf
/etc/NetworkManager/conf.d/

Also check whether legacy configuration files are controlling the same interface. On Debian-based systems, this may include /etc/network/interfaces. On server-style setups, systemd-networkd may be enabled. In general, one network management method should control a given interface.

11. When the problem happens after sleep or suspend

Some laptops fail to reconnect after waking from sleep. Restarting NetworkManager usually helps, but if it happens repeatedly, the issue may be power management. Updating the kernel and firmware is the safest first step. You can also test whether disabling Wi-Fi power saving improves stability, but this should be done carefully because configuration methods vary between distributions.

Final advice

The “Activation of network connection failed” error is not a single problem; it is a general failure message from NetworkManager. The most reliable approach is to work from simple causes to deeper ones: restart the router, restart NetworkManager, recreate the connection profile, confirm the adapter is detected, then inspect logs and drivers. If you document the exact error messages from journalctl and the output of nmcli device status, you will have the information needed to resolve the issue or ask for targeted help from your distribution’s support community.