Can't connect to wireless on open suse leap 15.4

English Network/Internet
1

Dear all,
today I tried installing a new user. To set up the wireless, I changed the Network Setup Method on Yast.
Unfortunately, this changed the settings for the already existing user and now wifi fails for all users.
I had this error in the past and after a lot of trials i managed to get it going. In the past I used the terminal to set up the network. For my old user, where wifi used to work I did as follows:

sudo nmcli --ask dev wifi connect SSID password PWD

however, it returns

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

At the begging I checked that nmcli radio wifi is on. I can also see the wireless antenna next to the clock.

nmcli dev wifi list returns the 5ghz and the 2.4 ghz networks and their SSIDs

.
The only problem I see is nmcli dev status, which says wlan0 wifi disconnected
I will appretiate your help

2

From what to what (we are not clairvoyant, sorry, you have to tell us the full story)?

4

I have three options on Yast.
Yast>NEtwork Steup Method> 1)Network service disabled 2) Wicked Service 2) Network Manager.

Currently I am using 3) Network Manager. I don’t remember what the original was.

5

Not very helpful, in the first place for you, but also for those who try to understand your problem.

I assume that it wasn’t 1), because then there would have been no networking at all (and you say there was).
I also assume that it wasn’t 2), because Wicked does not configure for a user, but on a system wide base, thus for all users.
Riddles!

That then is NOT for that user, because you do that command as root and not as the user.

I assume you have also problems understanding the nature of Unix/Linux as a multi-user/multi-session operating system.

6

This command activates existing connection. Show

nmcli -f 802-11-wireless-security connection show SSID | cat
7

I also tried to set up the wireless via the network manager. This does not work either.

8

the output is

sudo nmcli -f 802-11-wireless-security connection show  SSID | cat

802-11-wireless-security.key-mgmt:      wpa-psk
802-11-wireless-security.wep-tx-keyidx: 0
802-11-wireless-security.auth-alg:      --
802-11-wireless-security.proto:         --
802-11-wireless-security.pairwise:      --
802-11-wireless-security.group:         --
802-11-wireless-security.pmf:           0 (default)
802-11-wireless-security.leap-username: --
802-11-wireless-security.wep-key0:      <hidden>
802-11-wireless-security.wep-key1:      <hidden>
802-11-wireless-security.wep-key2:      <hidden>
802-11-wireless-security.wep-key3:      <hidden>
802-11-wireless-security.wep-key-flags: 0 (none)
802-11-wireless-security.wep-key-type:  unknown
802-11-wireless-security.psk:           <hidden>
802-11-wireless-security.psk-flags:     0 (none)
802-11-wireless-security.leap-password: <hidden>
802-11-wireless-security.leap-password-flags:0 (none)
802-11-wireless-security.wps-method:    0x0 (default)
802-11-wireless-security.fils:          0 (default)
9

psk-flags: 0 means that secret is stored as part of connection definition and is probably wrong. Did you check it?

This command seems to update secrets in the connection definition and I can reproduce it when I provide incorrect key as the value of password.

12

`

This command seems to update secrets in the connection definition and I can reproduce it when I provide incorrect key as the value of password.

`

thank you for you help. Unfortunately, I don’t know how to check it. This entire secret thing puzzles me.
I tried deleting the remembered connections, this did not help either.