Hmm, there seems to be a difference between networkmanager in KDE and in Gnome:
Situation is, there are two users, A and B. B defined this VPN connection and wants to start it. If only B is logged in (directly, not remotely), she can start the VPN in both KDE and Gnome. If B is logged in remotely, she can start it only if it's a KDE session, not in Gnome. A cannot start the VPN: in a KDE session, networkmanager asks for a password (which A doesn't know); in a Gnome session, no password dialog is shown at all (which cannot work, obviously...). I already tried to store the password in the VPN config file at /etc/ NetworkManager/system-connections/..., followed by a service network-manager restart but it didn't work: ... [vpn] ... password-flags=0 ... [vpn-secrets] password=PASSWORD Any ideas? Thank you. Best, Bernd On Tuesday, August 9, 2022 11:09:44 AM CEST B.M. wrote: > nmcli con up <VPN NAME> doesn't work either: nothing happens except the > three dots where the VPN icon is shown and after 90 seconds a timeout > message appears in the terminal window; so exactly the same behaviour :-( > > Bernd > > On Monday, August 8, 2022 3:03:17 PM CEST Harald Dunkel wrote: > > Hi BM > > > > if your VPN is IPsec, then you might want to examine charon's output via > > journalctl. Probably openvpn, wireguard and others can be found there, > > too. > > > > Another thing to try is to establish the VPN connection using nmcli in a > > terminal window, e.g. > > > > nmcli con up "VPN name" > > > > Maybe you get a usable error message this way. > > > > > > Regards > > > > Harri
