I know there are many other threads in the forum about openvpn issues, but none of them have helped nor have any proposed solutions worked for me. Although I suspect it to be a selinux issue, I don’t know enough about how Fedora implements that to know for sure.
I can use sudo openvpn MyVPN.ovpn to connect via cli, but there is absolutely no configuration via NetworkManager that works and I’m wondering if it’s connected to the fact that ioctl and tun0 can only be accessed via root…
Thanks for the info, @vgaetera; can the certs/keys be sym linked?
So, copying the cert and key files into ~/.cert and running sudo restorecon -R ~/.cert did nothing, as NM still complains the connection fails and journalctl gives me the same errors.
Thank you both, @tjdoyle and @vgaetera! Vladislav, you hit the nail on the head having me move the cert and key files; Tom, you were spot-on to suggest I check the cert path and, alas, that was the problem because after moving everything to ~/.cert NM was still looking in ~/Scripts/openvpn.
The issue is solved. Unfortunately, I can’t mark both of you as providing the solution.
On a related note, why so many hoops to jump through; that is, shouldn’t this be more intuitive?
Actually this is a long standing issue with NetworkManager failing to set the proper SELinux labels for the imported certs and keys.
This behavior is certainly counter intuitive and inconsistent compared to GNOME Boxes that automatically configures SELinux labels for image files.