Linux NetworkManager Wi-Fi Authentication Failed — What It Means & How to Fix It

Fix NetworkManager Wi-Fi authentication failures on Linux when WPA2/WPA3 connections fail despite correct credentials. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: NetworkManager handles Wi-Fi connections on most Linux desktop distributions. Authentication failures can occur even with correct passwords due to driver, firmware, or configuration issues. WPA3 (SAE) connections may fail on older hardware or drivers that only support WPA2. The error appears as 'Connection activation failed: Secrets were required but not provided' or '802.1X authentication failed'. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Wi-Fi driver or firmware not supporting the network's security protocol (WPA3). Stored password is corrupted in the keyring/keychain backend. 802.1X enterprise authentication certificate issues. Driver bug causing authentication handshake failures (common with certain Broadcom/Realtek chips). Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Delete the saved network: nmcli connection delete 'Network Name' then reconnect with the password. Check Wi-Fi driver status: dmesg | grep wifi or dmesg | grep wlan for firmware/driver errors. Force WPA2 if WPA3 fails: nmcli connection modify 'Network' 802-11-wireless-security.key-mgmt wpa-psk. Update Wi-Fi firmware: sudo apt install linux-firmware or download from the chipset vendor. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Linux Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.