switchboard-plug-network
switchboard-plug-network copied to clipboard
Cannot import .ovpn file on Loki
While trying to import a VPN configuration file from OpenVPN access server, I get "Cannot import VPN Connection"
An Error pop's up:
The file 'client.ovpn' could not be read or does not contain recognized VPN connection information
Error: the plugin does not support import capability.
I have used the same file to import into Centos and Fedora without issue. Not sure if the .ovpn file needs to be in another format or if there is another issue. Thanks!
Launchpad Details: #LP1639954 Brad Thresher - 2016-11-07 21:32:18 +0000
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Added 10$ Bounty:
https://www.bountysource.com/issues/39132785-cannot-import-ovpn-file-on-loki
Launchpad Details: #LPC Elias Gabrielsson - 2016-12-13 20:39:26 +0000
Have you tried this yet?
http://elementaryos.stackexchange.com/questions/109/interface-to-configure-openvpn
Launchpad Details: #LPC Levo - 2016-12-14 22:38:27 +0000
I've had success using ovpn files from NordVPN, maybe their documentation for openVPN is helpful: https://nordvpn.com/tutorials/linux/openvpn/ (I'm not sponsored or affiliated)
I have received three or four OVPN files from my client for connecting to their intranet, and none of them worked with elementaryOS (or Ubuntu for that matter). The error message is misleading: "the plugin does not support import capability" sounds like OpenVPN files can't be imported in general, but usually the issue is that the file contains invalid or outdated options.
Here are a few examples of settings that need to be removed/changed in the OVPN file before the importer will accept it: https://askubuntu.com/questions/761684/error-the-plugin-does-not-support-import-capability-when-attempting-to-import
I think the best way to fix this would be for OpenVPN to be more lenient when it comes to parsing options. The next best thing would be useful error messages ("option XYZ is invalid"). And if no upstream project is interesting into making this process smoother, the switchboard plug could maybe link to a FAQ page with common OpenVPN configuration issues.
Some possible problems:
- Do you have openvpn installed? => solution: sudo apt install openvpn
- Do you have network-manager-openvpn-gnome installes? => solution: sudo apt install network-manager-openvpn-gnome
- Have you restarted your network-manager? => sudo service network-manager restart
@jlnr Were able to resolve the parsing issues or does it still affects Juno? Currently parsing is handled by nm-connection-editor but eventual plan is to move to a native implementation.
Is this still relevant?