[SOLVED] Can't connect to wifi, Error: Secrets were Required

Unkylosaur · 2024-06-13 16:17:59

I installed arch linux with the base linux kernel, and am dual booting it with windows 10.

I'm using grub and efi partition to boot.

My issue is that I am able to connect to other networks and mobile hotspot with both iwctl and NetworkManager (not by running both simultaneously, I disable network manager and wpa-supplicant before running iwd and vice versa), but I am unable to connect to my home Wifi network in both.

My home Wifi Network has 2 seperate bands that show up as 2 seperate wifi networks, which are 2.4ghz and 5 ghz.

Arch can't connect to both.

If I try and connect with network manager, with both nmtui and nmcli, it returns the error: Error: connection activation failed: Secrets were Required. If I try and connect with iwd, it returns the error: Operation Failed.

I have disabled scan random mac addresses in the Network Manager conf file and the issue persists.

On Windows 10 on the same PC I can connect to the wifi network without any problems.

Output of

 journalctl -u NetworkManager

--> here

Output of

 lspci

--> here

Output of

 ip link

-->

 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 08:97:98:e2:e9:61 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether d8:f3:bc:43:2d:61 brd ff:ff:ff:ff:ff:ff

Last edited by Unkylosaur (2024-06-15 03:24:38)

seth · 2024-06-13 19:21:39

am dual booting it with windows 10

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Edit: oh, and possibly also reboot the router.

If that's not it "journalctl -u NetworkManager " isn't really helpful here.
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Last edited by seth (2024-06-13 19:21:57)

Unkylosaur · 2024-06-14 15:10:13

http://0x0.st/Xc4q.txt

Fastboot is disabled.

seth · 2024-06-14 16:44:41

Jun 15 02:03:16 unkylosaurPC NetworkManager[432]: <info> [1718397196.0947] device (wlan0): Activation: (wifi) connection 'Steins;Gate' has security, and secrets exist. No new secrets needed.
…
Jun 15 02:03:16 unkylosaurPC wpa_supplicant[435]: wlan0: SME: Trying to authenticate with 78:8c:b5:3e:f9:3f (SSID='Steins;Gate' freq=2412 MHz)
…
Jun 15 02:03:16 unkylosaurPC kernel: wlan0: authenticated
Jun 15 02:03:16 unkylosaurPC kernel: wlan0: associate with 78:8c:b5:3e:f9:3f (try 1/3)
…
Jun 15 02:03:16 unkylosaurPC wpa_supplicant[435]: wlan0: Associated with 78:8c:b5:3e:f9:3f
…
Jun 15 02:03:16 unkylosaurPC kernel: wlan0: associated
…
Jun 15 02:03:16 unkylosaurPC NetworkManager[432]: <info> [1718397196.3122] device (wlan0): supplicant interface state: associated -> 4way_handshake
Jun 15 02:03:16 unkylosaurPC NetworkManager[432]: <info> [1718397196.3122] device (p2p-dev-wlan0): supplicant management interface state: associated -> 4way_handshake
Jun 15 02:03:22 unkylosaurPC kernel: wlan0: deauthenticated from 78:8c:b5:3e:f9:3f (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
Jun 15 02:03:22 unkylosaurPC wpa_supplicant[435]: wlan0: CTRL-EVENT-DISCONNECTED bssid=78:8c:b5:3e:f9:3f reason=15
Jun 15 02:03:22 unkylosaurPC wpa_supplicant[435]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jun 15 02:03:22 unkylosaurPC wpa_supplicant[435]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Steins;Gate" auth_failures=1 duration=10 reason=WRONG_KEY
Jun 15 02:03:22 unkylosaurPC wpa_supplicant[435]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

You're getting the wifi password from some database (NM internal, some passwordmanager) and it seems to be wrong.
Remove the connection from the list of known ones, connect again, make extra-sure to not fat-finger the key

Edit: because of the timeout, are you implementing a MAC filter on the AP?
Even if not and the symptom would be weird, try to disable https://wiki.archlinux.org/title/Networ … domization - some APs seriously don't like that and stop talking to you (but usually not at this stage)

Last edited by seth (2024-06-14 16:46:51)

Unkylosaur · 2024-06-15 03:23:55

Thank you for your reply

I disabled random MAC addresses and it's working fine. Thank you again!

Arch Linux

#1 2024-06-13 16:17:59

[SOLVED] Can't connect to wifi, Error: Secrets were Required

#2 2024-06-13 19:21:39

Re: [SOLVED] Can't connect to wifi, Error: Secrets were Required

#3 2024-06-14 15:10:13

Re: [SOLVED] Can't connect to wifi, Error: Secrets were Required

#4 2024-06-14 16:44:41

Re: [SOLVED] Can't connect to wifi, Error: Secrets were Required

#5 2024-06-15 03:23:55

Re: [SOLVED] Can't connect to wifi, Error: Secrets were Required

Board footer