I have imported the .ovpn file, I try to connect all according to this one article
and it don’t know why it does not work. When I import it using KDE itself it asks for a password, or secret, that as far as I know does not exist, when I import it using the CLI like the guide says I get hit with “User authentication failed” whether I paste the password, or type each character individually.
Does anybody have any information on this? Is there a different package that I should be using?
This is the start of the .ovpn file, for reference. I redacted that bit.
client
dev tun
proto udp
remote [REDACTED]
resolv-retry infinite
nobind
persist-key
cipher AES-256-GCM
auth SHA1
persist-tun
reneg-sec 0
remote-cert-tls server
verb 3
key-direction 1
auth-nocache
auth-user-pass
As far I know, openvpn3 is not yet supported by Fedora, so big chance that the KDE imports profiles for use with OpenVPN2. Since the profile contains auth-user-pass, it’s not surprising that it asks for username and password. If you import in KDE as user, you should start the connection as user. Using command line “nmcli” as root will complain, because it assumes the password is in the NetworkManager’s system connection file after import by nmcli as root.
Nevertheless, I installed openvpn3 from copr, and tried a ProtonVPN config. Thanks a big mistake of me, a user readable file containing user and password, it worked immediately.
But after removing the file name behind “auth-user-pass”, it prompted for username and password and worked. So I think you have to check the openvpn3 logging facilities to find out what’s wrong.
Keep also an eye on Selinux, and try “sudo setenforce 0” to disable it temporary. OpenVPN3 starts background processes via dbus which might have less SELinux rights as a foreground OpenVPN2.
Addition: I have the idea that there is something wrong with the VPN password in the KDE version, preventing the OpenVPN(2) to start. I have to figure out what exactly is wrong later.
nm-connection editor and VPN start with nmcli (as user) is fine.
If you want to activate the connection at startup or manually by root, store its secrets in the connection profile, otherwise it only works for active user session when using KWallet.
I have the impression that there is something wrong with the password storage in some of the packages involved. According to “seahorse” , in the gnome-keyring just the password is stored. In KDE, seahorse displays the kwallet, and the OpenVPN password is stored there but it looks like some structure containing username and password.
In KDE, the connection fails to come up until timeout. The log shows that the OpenVPN remote control is waiting for credentials.
Funny thing is, at least on my system:
Password stored in both GNOME and KDE, KDE switched to “Ask each time for password”, so password field greyed out: Upon starting the VPN, no password entry field appears, but the connection just comes up…
So somewhere there is confusion about where to get the credentials from. I’m not able to find or send a bug report now. Is it NetworkManager or one of the related openvpn packages?
Anyhow, OpenVPN3 from COPR with the corresponding CLI commands should ask for username and password and connect.