Hello all! I apologize if this subject has been posted; I searched and didn't find anything.
Since the last update, the Wifi with VPN won't connect automatically; there is a popup asking me to confirm the VPN password (which is already filled in the field), so I have to click 'OK' and the connection is established.
Is there a way not to have this popup, and that the VPN connects without clicking ?
Thank you!

    Remove the connection and re-add?

    Bouquins
    There is a simple solution.

    This usually occurs upon automatic login.

        JoshStrobl Hello, I saw it before, it didn't work. Thanks anyway! I'll see if removing the connection and adding it again work. It's weird.
        @youwer sorry, it seems confusing to me.

          youswer I'd suggest switching languages before posting screenshots as I imagine not many people read (I'm assuming here) Russian.

              Justin

              Ok. Next time.But I signed all the screenshots in English.

                I doesn't seem that it is a keyrong problem. It is specifically bound to the VPN connection.

                Well, this is weird. NordVPN doesn't work for me on Fedora 30 Gnome.

                I have two laptops and one runs Solus and the other runs Fedora 30. I upgraded from 29 via the new rolling-release style instead of doing a clean install. It is an absolute mess.

                About two or three days ago I realized that my NordVPN wasn't coming on. I tried several different ways of running the .ovpn file but none of them work. I have been working all day today to prepare my Fedora machine to be wiped so I can install Solus Gnome. I can deal with most of the issues I have now but I need to have a VPN running. Without it this laptop is useless.

                It would really suck if I did all this and Nord didn't work in Solus either.

                Just checked my Solus Budgie install and NordVPN works fine on it.

                  I use OpenVPN in Fedora 30 using the Network-Manager. No applets I have never gotten them to work right. I was only able to get NordVPN working on Fedora by manually inserting the information from the .ovpn file. I couldn't even import the .ovpn file on Fedora without having to do so manually with this command:

                  sudo nmcli connection import type openvpn file nordvpn-server.ovpn

                  I didn't have any of these problems on Solus. I run Budgie on my other laptop and it imported from the .ovpn file on both my Laptop and my roomates Desktop.

                  It's weird that the original poster and I are both having the same situation with NordVPN connection failure. Maybe it is an issue with NordVPN and not either of the distros discussed here.

                    jrsilvey I seem to be able to turn on/off NordVPN from Network Manager, once I have downloaded the OpenVPN server connection files. No problem. No VPN applet of course, but this will do for me, as long as it works! :-)

                        elfprince Be warned! Using it that way can lead to 'leaks'! It is better to use something that has a native client for solus. My VPN provider is ProtonVPN and they support solus.

                          Leaks occur when:

                          • You still use ISP DNS
                            • Change to VPN DNS
                          • WebRTC is enabled in your browser
                            • Disable it
                          • VPN disconnects and by default there is no 'kill switch'
                            • Use ufw for example and set rules so traffic can only go over tun0

                          https://ipleak.net can help you test for leaks.

                          Edit:
                          btw VPN specific applications like the one for PIA do what I listed above, they just don't require you to know how.

                            I can confirm that PIA only uses basic networking commands to perform it's functionality. I tinkered with it to get it running on Solus. It's like Harvey said, it just strings together a series of already supported events. The only reason it won't run on Solus is it uses the old net-tools commands (which aren't on Solus).

                            Harvey Would you mind explaining how to go about doing what you suggest in your three points? A bit over my head. Thanks! :-)