Created attachment 549460 [details] /var/log/messages after upgrading my KDE and networkmanager environment a couple months back the fortisslvpn connections do not work any more when initiated from the plasma-nm application. the standalone CLI openfortivpn application that this calls still works. I've attempted to re-install all dependencies as well as deleted all vpn's in plasma-nm and reconfigured them with no change. This is reproducible on both my Gentoo installs running the KDE layman overlay.
I've experienced similar issues in the past. Does it work when you connect to the vpn through nmcli? Or when you use the standalone openfortivpn client? A week or two ago everything started working again for me, unfortunately I can't really pinpoint what the exact reason was as I don't connect to this vpn regularly. I'm currently running networkmanager 1.14.0, networkmanager-fortisslvpn 1.2.8, pptclient 1.8.0 and plasma-nm 5.13.5-r1.
This issue bit me again but I found a solution that worked for me. Forgot this bug also existed so forgive for not adding the info earlier. I found this bug report at Gnome which describes the same issue someone else had and discussed over there: https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/issues/9 The solution there was to add logfile filename in /etc/ppp/options. I tried it and it also worked for me. Can you give it a try?
Closing because no feedback and implementation is currently working with the Fortinet VPN I have to test with.
This bug is not resolved, I'm experiencing the exact same issue as described here by Joe Keen. I've tried the "Use a One-time Password" and the "2FA" options under the Advanced button in all 4 possible combinations, but the the openforticlient refuses to connect when it's combined with a FortiToken via the GUI. It does work fine without a FortiToken. - I've tried this in Gnome on another PC and it's working fine in Gnome when you enter the FortiToken. - I've tried connecting using the openfortivpn on the CLI and here it's working fine too and asking for the FortiToken. As a workaround I'm connecting via a terminal right now, but that's not the ideal situation. Please tell me what additional logging you would need to reproduce the error, as I can reproduce the error relatively easy.
