I am using Fedora 31 with KDE Plasma. I have been using this particular configuration for about 6 months. I started at Fedora 29 and upgraded to 30 and then 31.
I am having trouble connecting to my VPN. I have been using this VPN very regularly and have never had this issue the entire time.
The VPN is confirmed as working as I can connect successfully to it from Windows and my co-worker can also connect successfully from his Ubuntu system.
When ever I click on the Network icon and under available connections click Connect next to the VPN it says
The service providing the VPN connection was stopped.
I have had the VPN configured on this machine since fc29 (currently on fc31) and have never had this issue until recently.
I tried restarting the system and it had no effect on the problem.
I double-checked all of my configuration settings for the VPN and they are correct.
I also run fc31 on my laptop. The VPN was connecting fine this morning.
However, after running
dnf update
And updating kernel, kernel-core, kernel-devel, kernel-modules, kernel-modules-extra to 5.5.7-200.fc31 ⌠the VPN no longer connects on the laptop, either!
What do I do? How do I get around this? I tried restarting the computer and selecting the previous kernel but I am experiencing the same problem (cannot connect).
OK - this is now getting extremely complicated. Previously, I just had to enter a gateway, username, password, pre-shared key and click connect. Now, I have to generate certificates, read a large manual, and spend hours of attempts in configuring correctly on command-line.
I will dive into it⌠but this sucks, it just worked before the âupgradesââŚ
  Some another example (scrollable), proton-example.ovpn:
# ==============================================================================
# Copyright (c) 2016-2017 ProtonVPN A.G. (Switzerland)
# Email: contact@protonvpn.com
#
# The MIT License (MIT)
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in all
# copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR # OTHERWISE, ARISING
# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
# IN THE SOFTWARE.
# ==============================================================================
client
dev tun
proto udp
remote nl-free-02.protonvpn.com 80
remote nl-free-02.protonvpn.com 443
remote nl-free-02.protonvpn.com 4569
remote nl-free-02.protonvpn.com 1194
remote nl-free-02.protonvpn.com 5060
remote-random
resolv-retry infinite
nobind
cipher AES-256-CBC
auth SHA512
comp-lzo no
verb 3
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
persist-key
persist-tun
reneg-sec 0
remote-cert-tls server
auth-user-pass
pull
fast-io
# anti-DNS-leaks-stuff; idk about this matter.
script-security 2
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf
<ca>
-----BEGIN CERTIFICATE-----
## cut by vits95 ##
-----END CERTIFICATE-----
</ca>
key-direction 1
<tls-auth>
# 2048 bit OpenVPN static key
-----BEGIN OpenVPN Static key V1-----
## cut by vits95 ##
-----END OpenVPN Static key V1-----
</tls-auth>
I have ______ out all information that is secret. They are not actually _______.
I am looking at the example file you have posted and it seems like a totally different paradigm - I donât know how to correspond/translate from one to another.
Iâm really happy with using openvpn client on F31.
Iâm not sure why itâs such a problem, but itâs really useful for server and client use and management if you donât have a problem with the environment configuration and key setting parts.
It is pretty basic L2TP VPN connection that I use to connect to a network I use for work purposes.
The IPSec part should be irrelevant⌠as I said, it worked perfectly for many months and then after a recent upgrade to the kernel (and to some other NetworkManager related stuff, I would assume) it stopped workingâŚ
There is no problem with the NetworkManager service, but please refer to the installed status below. You need to specify the port opening for the VPN configuration and firewall configuration. Have a nice day.
OK I have almost the exact same output for status NetworkManager and nearly the same packages installed related to openvpn
I am unclear what you mean by which port⌠I believe there are several ports we would be using since there are several services that we use over the VPN. I know the IP ranges that I would like the VPN to use - but the ports list is a bit more difficult to obtain⌠only because previously I did not have to worry at all about ports, it was all automatic.
This seems like a huge downgrade and step backwards from something that configured itself to something I now have to specify manually. My lab partners are asking me WTF is wrong with my OS that I have to specify ports for the VPN connection.