[RESOLVED] Adding Wireguard vpn config fails…because OpenVPN support is missing?

[faster1]

I’m trying to add a wireguard config file that I downloaded from my VPN provider to my Kubuntu 25.04 system. I opened the system settings app, found the network page, and clicked add new network connection. When I select import saved VPN config, and import the config file the settings app gives an error.

Failed to import VPN connection: NetworkManager is missing support for OpenVPN

What’s up with this? I’m importing a Wireguard config-not an OpenVPN one. Appreciate any help!

[faster1]

I did some more testing, and finally learned that that the WireGuard config files have to be named in a specific format of "wgX.conf" for them to be imported. X should be replaced with whatever number of VPN connections you need. My VPN provider didn't name these files according to this rule. After renaming the file it imported as expected.

[Snowhog]

Failed to import VPN connection: NetworkManager is missing support for OpenVPN

AI Overview

The error "Failed to import VPN connection: NetworkManager is missing support for OpenVPN" in Kubuntu 25.04 indicates that the necessary plugin for managing OpenVPN connections within NetworkManager is not installed. This plugin, network-manager-openvpn, allows NetworkManager to handle .ovpn configuration files and establish VPN connections.

Check to see if you have network-manager-openvpn installed. If not, install it, then restart the NetworkManager: sudo systemctl restart NetworkManager After restarting, you should be able to import your .ovpn file through the NetworkManager settings.

[faster1]

AI Overview

Check to see if you have network-manager-openvpn installed. If not, install it, then restart the NetworkManager: sudo systemctl restart NetworkManager After restarting, you should be able to import your .ovpn file through the NetworkManager settings.

The config is for WireGuard though-not OpenVPN. Why would support for OpenVPN matter? And the config file is a .conf file-not a .ovpn file.

[Snowhog]

Okay. Again, AI Overview based on a search of: kubuntu linux 25.04 how to get NetworkManager to recognize wireguard


Import a configuration file using nmcli

You can also import your WireGuard configuration file using the NetworkManager command-line interface nmcli. Open a terminal and run the following command, replacing /path/to/wg0.conf with the actual path to your configuration file:

nmcli connection import type wireguard file "/path/to/wg0.conf"

Once imported, you can manage the connection through the NetworkManager GUI or using nmcli.

Verify the connection

After establishing the WireGuard connection, you should verify that it's working properly.

• Check Connectivity: Try accessing resources that should be reachable through the VPN.
• DNS Leak Test: Consider using an online tool like https://ipx.ac/run or https://www.dnsleaktest.com to ensure your DNS is being resolved through the VPN and not leaking your real IP address.

By following these steps, you should be able to get NetworkManager in Kubuntu 25.04 to recognize and manage your WireGuard VPN connections.

[faster1]

Anyone know how to get the GUI VPN configurator to work though? Wondering if I should post a bug report on KDE or something.

[claydoh]

Maybe this?
https://bugs.kde.org/show_bug.cgi?id=501544

I found an old wireguard config file for my provider, and reducing the filename length allows it to be imported just fine.
It doesn't work, but that could be for any sort of reason, like its age.

Now, this config file is pretty basic, so even manually entering the information isn't hard, nor is using nmcli to import it.

[Interface]
Address = xx.xxx.xxx.xxx
PrivateKey = **********************************************************8=
DNS = ***.***.***.***,***.***.***.***

[Peer]
PublicKey = ***********************************************************=
Endpoint = ***.***.**.**:1337
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 25​

With the keys, that '=' at the end needs to be there, at least for the peer.

[faster1]

I did some more testing, and finally learned that that the WireGuard config files have to be named in a specific format of "wgX.conf" for them to be imported. X should be replaced with whatever number of VPN connections you need. My VPN provider didn't name these files according to this rule. After renaming the file it imported as expected.