Hide Forgot
Description of problem: Cannot connect to VPN using nmcli (console) and getting this error message: Sep 25 19:51:08 zappa.orion NetworkManager[27230]: <info> [1474847468.7123] vpn-connection[0x560861f55130,147985e0-44be-46c4-bd2b-aff76808b71b,"this_is_my_vpn",0]: VPN plugin: requested secrets; state connect (4) Sep 25 19:51:10 zappa.orion NetworkManager[27230]: <error> [1474847470.0076] vpn-connection[0x560861f55130,147985e0-44be-46c4-bd2b-aff76808b71b,"this_is_my_vpn",0]: Failed to request VPN secrets #4: No agents were available for this Sep 25 19:51:10 zappa.orion NetworkManager[27230]: <warn> [1474847470.0097] vpn-connection[0x560861f55130,147985e0-44be-46c4-bd2b-aff76808b71b,"this_is_my_vpn",0]: VPN plugin: failed: connect-failed (1) Sep 25 19:51:10 zappa.orion NetworkManager[27230]: <info> [1474847470.0098] vpn-connection[0x560861f55130,147985e0-44be-46c4-bd2b-aff76808b71b,"this_is_my_vpn",0]: VPN plugin: state changed: stopping (5) Sep 25 19:51:10 zappa.orion NetworkManager[27230]: <info> [1474847470.0099] vpn-connection[0x560861f55130,147985e0-44be-46c4-bd2b-aff76808b71b,"this_is_my_vpn",0]: VPN plugin: state changed: stopped (6) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Import openvpn configuration with nmcli conn import type openvpn file file.conf 2. Try to up it with nmcli -a -s this_is_my_vpn 3. Actual results: Fails with error message above Expected results: Succeeds Additional info:
(In reply to David Hill from comment #0) > Version-Release number of selected component (if applicable): Which NM version is it? Can you please attach logs with debug level (i.e: nmcli general logging level DEBUG nmcli -a connection up my_vpn )?. Thanks!
(In reply to David Hill from comment #0) > 2. Try to up it with nmcli -a -s this_is_my_vpn I assume you did nmcli -a conection up this_is_my_vpn ? The other isn't a valid command.
(In reply to Thomas Haller from comment #2) > (In reply to David Hill from comment #0) > > > 2. Try to up it with nmcli -a -s this_is_my_vpn > > I assume you did > > nmcli -a conection up this_is_my_vpn > > ? The other isn't a valid command. -s actually shows my password so I'm sure I'm not doing any typos.
I found the problem. It seems like the problem is that auth-user-pass won't be imported as "username=my_username" and adding that line to my /etc/NetworkManager/system-connections/this_is_my_vpn and restarting NetworkManager solves the issue.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.