Next day after 22.04 beta install, WireGuard will no longer connect

[juanejot]

How did you upgrade to 22.04? (Fresh install / Upgrade)

Upgrade from 21.10

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

WireGuard (made accessible to the GUI by https://github.com/max-moser/network-manager-wireguard)

Issue/Bug Description:
Upon 22.04 beta install (without reboot) WireGuard connections I had previously configured worked. They may have continued to work upon warm reboot the same day; I didn’t research. Upon cold boot the next day, they simply didn’t connect (with a dialog box announcing they hadn’t). Reinstallation of WireGuard or network-manager-WireGuard did not solve the issue, but reverting to a 21.10 refresh did.

Steps to reproduce (if you know):
Try to use WireGuard connection

Expected behavior:
That it work as previously.

Other Notes:
As above.

[xploz1on]

This also has been reported to happen with NordVPN. It was kinda of happening with ProtonVPN but after a few days of updates, now the CLi and GUI interface of it connects without any problem.

[juanejot]

This bug is still happening in 22.04 final.

[juanejot]

This may be related to VPN connection editors on multiple distros (see https://bugzilla.redhat.com/show_bug.cgi?id=2057719 and https://bbs.archlinux.org/viewtopic.php?id=275815 ) using gnome-control-center on Gnome 42, not being able to load (apparently needing a port to GTK4 they haven’t got yet).
I just tried the same on the latest Arch (with Gnome 42), even having gotten the network-manager-wireguard referenced above to build & actually installed the older nm-connection-editor & built the VPN connection in it; still no dice with the same “Connection failed / Activation of network connection failed” message popping up.
That said, if Pop!_OS is stepping away from Gnome for COSMIC & switching to something internally Rust-based, then it sounds like a GTK4 replacement may be necessary sooner than later, to keep VPN connections which are mission-critical for many users, working. Or switch back to an older version of gnome-control-center that doesn’t need GTK4 (dunno if that’s an element of the FrankenGnome that Ubuntu 22.04 has got going).

[juanejot]

Continuing to tinker with it, I added libgtk-4-dev to the packages I used to compile Max Moser's network-manager-wireguard (above), and that did allow me to see WireGuard configurations I had configured (where having only libgtk-3-dev installed amongst the other packages necessary did not allow me to see the details of any installed WireGuard configuration inside gnome-control-center.
Sadly, that did nothing to actually allow a WireGuard configuration to connect; same error dialog as above. Even when a new WireGuard configuration was created, after re-building/re-installing network-manager-wireguard with libgtk-4-dev installed.
So I'm missing something. Something which a few commercial VPNs have evidently figured out, and not 100% on System76's to-do list, as it's more about how a network-manager package for each individual (kind of) VPN could be added to the Network pane of gnome-control-center.
In the meantime, my workaround is going to have to be setting up my wireguard client & connecting completely from the CLI. I'm not going to close this issue right now, however, in hopes that someone at System76 or another Pop!_OS 22.04 user might have more insight into how to get WireGuard configurations setup and connecting/disconnecting from the GUI. Moderators, please let me know if you'd rather I close.

[ipeacocks]

Seems it's not distro fault, it's wireguard vpn plugin needs to be updated. Maybe because of NetworkManager latest changes.

[mmstick]

VPNs have to update their software to support 22.04 and OpenSSL 3.0

[juanejot]

Right on. And in the case that one “rolls their own” VPN? Assuming OpenSSL 3.0 is installed, how does one ensure the server’s wg0.conf utilizes it correctly (if it wasn’t already, which I have no reason to believe it wasn’t)? Also, what other support for 22.04 is necessary?
I realize these questions go outside the scope of the Pop!_OS side of things. But if servers need to be updated to play nice with it (in the GUI), some guidance to the right resources would be most appreciated. Thanks!