16

Using NetworkManager on Arch Linux on a MacBookPro14,3, I am unable to connect to any wireless network. I've tried connecting to a number of different WiFi networks (home, mobile hotspot, work) all with the same result. I've tried doing this with both nmcli and nmtui. Example:

$ nmcli dev wifi connect <SSID> password <password>
Error: Connection activation failed: (7) Secrets were required, but not provided.

Looking at logs with journalctl shows:

wpa_supplicant[PID]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16

and

NetworkManager[PID]: <info> [TIMESTAMP] device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')

The Macbook has a Broadcom BCM43602 with driver brcmfmac. NetworkManager and wpa_supplicant are installed and enabled.

21

It seems that NetworkManager automatically reuses an existing connection. In case your existing connection does not have any secrets stored, the new connection attempt will not update the existing connection and fail due to missing secrets. So in my case these steps helped:

nmcli con delete <SSID>

Then reconnect using

nmcli dev wifi connect <SSID> password <password>
| improve this answer | |
  • This just shows the same error message again. Does not help. (Newly setup Orange Pi Zero with Armbian Bionic) – ygoe May 31 at 10:28
6

Try turning the WiFi off and on again like this:

nmcli r wifi off to turn it off.

nmcli r wifi on to turn it on.

Check the available WiFi networks: nmcli d wifi list

Check and disconnect the WiFi that appears green:

nmcli con to check.

nmcli con down <wifi name> to disconnect.

If you don't know for sure if the password you provided is right, connect again:

nmcli dev wifi con "wifi name" password "wifi password"

Nota bene: Don't forget the "" on the name and the password.

Or try to reconnect to the WiFi: nmcli con up <wifi name>

Sometimes the problem is the connection with NetworkManager. If it's not working, let me know!

| improve this answer | |
4

Next solved my problem, was taken from: https://www.youtube.com/watch?v=P7bAp4vBxnA

  • Edit with sudo grants: /etc/NetworkManager/NetworkManager.conf

  • Add the next two lines:

 [device]
 wifi.scan-rand-mac-address=no
  • Execute: sudo systemctl restart NetworkManager

  • Use your WiFi. ;)

| improve this answer | |
  • I had the same problem again after the first valid connection with the above "solution". – Medardo Rodriguez May 18 '19 at 15:41
2

Have absolutely no idea what the error message means... But I did just encounter the dreaded:

Error: Connection activation failed: (7) Secrets were required, but not provided.

For me, I'm using a BT Home Hub (in the UK). Which has a feature that attempts to be clever, and combine the 2.4GHz and 5GHz bands together, and upon a device requesting a connection, deciding which band it would be best off connecting to.

This is a terrible idea, for many many reasons, but anyway. Upon logging on to my Home Hub through another device (http://192.168.1.254/gui/#/advancedWifi/configuration) There was a button called "Seperate Bands", which when turned on allowed me to get two SSIDs, one for 2.4GHz, and the other for the much faster 5GHz.

Once I could differentiate between the two bands via SSID, bingo. nmcli would connect!

sudo nmcli -a d wifi connect BTHub6-XXXX-5

I'm assuming that nmcli see's that there are two identical SSID's but for different channels/bands, can't decide which to connect to, and complains it doesn't have enough info.

Not sure if this will work for everyone's situation, but it's worth investigating if you have a 5GHz router, and only see one SSID when scanning on your phone/laptop/whatever.

| improve this answer | |
0

I solved this annoying problem by first removing all connections:

nmcli --fields UUID,TIMESTAMP-REAL con show | grep never |  awk '{print $1}' | while read line; do nmcli con delete uuid  $line;    done

And then connect.

| improve this answer | |
0

For first time use nmtui to connect to wifi.

| improve this answer | |
0

I got this when trying to configure 'eduroam', which involves WPA2 Enterprise certificates and whatnot. I couldn't quite get it to work, but more strangely, my previous, local wifi connection would fail to come back up. After much struggling about, the solution was nmcli con del eduroam, after which the other network worked normally again.

TL;DR: failure to connect may be due to the presence of a different, misconfigured connection. I consider this a bug in NetworkManager.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.