You are not logged in.
My last update was a few months ago and my vpn connection to corporate vpn was fine. Updated this morning which included the open ssl updates and was not able to connect to corporate vpn anymore due to an apparent dbus failure. Corporate vpn does not use two factor auth so I dont think it is this networkmanager-openvpn issue
$ nmcli connection up myvpn --ask
You need to authenticate to access the Virtual Private Network “myvpn”.
Password (vpn.secrets.password):
Error: Connection activation failed: Unknown reason
Hint: use 'journalctl -xe NM_CONNECTION=someID + NM_DEVICE=enp7s0' to get more details.
looking at the journal gives:
Nov 08 13:54:49 effervescence NetworkManager[43818]: <info> [1667886889.7187] vpn[0x5608682ec370,someID,"myvpn"]: starting openvpn
Nov 08 13:54:51 effervescence NetworkManager[43818]: <warn> [1667886891.8830] vpn[0x5608682ec370,someID ,"myvpn"]: dbus: failure: connect-failed (1)
Nov 08 13:54:51 effervescence NetworkManager[43818]: <warn> [1667886891.8831] vpn[0x5608682ec370,someID ,"myvpn"]: dbus: failure: connect-failed (1)
I have tried the using networkmanager-openvpn-git which did not fix the problem. I am currently unable to build openvpn-git due to a separate problem so it seems like there is no resolution.
As you can tell this is my first post here, any advice on how to debug further or fix would be appreciated.
Offline
Welcome to the forums. You likely need to post the complete journal. journal -b --no-pager. If there's a lot of it, you can post it elsewhere (wiki instructions linked below) and post the link.
See https://bbs.archlinux.org/viewtopic.php?id=281086. Have you tried without NetworkManager? That's suggested in one of the posts there.
Last edited by cfr (2022-11-08 06:21:07)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
It would appear my CA certificates are too weak as they use SHA1 or MD5 meaning regular openvpn will not connect. I will regenerate and see if I still get the issue.
Thank you for pointing me in the right direction!
Offline