Support will be removed on both client and server side.

The process of removing OpenVPN from our app starts today and may be completed much earlier.

  • pineapple@lemmy.ml
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    2
    ·
    13 days ago

    If wire guard is just bettr then I don’t see any reason to suport OpenVPN anyway.

    • TheReturnOfPEB@reddthat.com
      link
      fedilink
      English
      arrow-up
      16
      ·
      edit-2
      12 days ago

      i can’t get wire guard to work on my home network so it is not better for me

      edit: to be fair my internet connection is being tapped and recorded by law enforcement so i am assuming that is the problem.

      • pineapple@lemmy.ml
        link
        fedilink
        English
        arrow-up
        7
        ·
        13 days ago

        Is that with any vpn provider? or hosting your own? And that is kind of a shame I guess you just won’t be able to use Mullvad vpn, good thing there are heaps of other options.

      • communism@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        12 days ago

        How are you trying to using WG? I had issues with wg quick up or whatever it is, not bothered to check, but adding wireguard connections as NetworkManager interfaces works flawlessly for me.

      • NekuSoul@lemmy.nekusoul.de
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        13 days ago

        That’s kind of weird, because the reason why I never bothered with (selfhosted) VPNs before Wireguard was because it was the first one that just worked. Granted, due to its nature, you don’t get a lot of feedback when things don’t work, but it’s so simple in principle that there’s not a lot that can go wrong. For external VPNs like this, it should just be: Load config, double-check, done.