This is working for me now. When I import into Network Manager, it
literally tells me which line is the problem now, and whatever line that
is, I comment it out and it works. Before, it would just tell me that
there was an issue importing but it wasn't specific. But at least now,
Network Manager helps me figure out the issue. I recently switched to
Ubuntu GNOME, so I'm not sure if there's something specific with the
GNOME implementation that displays specific errors, or if Network
Manager has changed. At least it's working for me now, albeit with
manual intervention being required.

In my opinion, the real issue at this point is that even though
commenting out some lines helps, each line is valid and should be
accepted. If I export an .ovpn file and use it via the command line, it
works without issue (even without commenting out anything). In my view,
if the config file is valid enough for OpenVPN itself, it should surely
be valid for Network Manager. Perhaps the OpenVPN spec has updated and
Network Manager hasn't been updated to match?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606365

Title:
  unable to import config with inlined ca, cert, key or tls-auth

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to