-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connecting to VPN has no effect on Debian testing "Bullseye" #133
Comments
I recently just upgraded from stretch to buster and found simply having the SUDO -E option had no effect. My I posted my openfortigui notes - maybe it will be of some help? |
On Linux Mint 20/Cinnamon I am not seeing any effect when clicking on Connect, nothing in logs at all, nothing in the shell that the app is launched from. No difference with sudo. |
If you run (Type it into a command-line terminal, don't use the GUI button) |
This sudo message simply mean there is no matching sudo rule for openfortigui found and so it trys to ask for a password interactively which is not possible in this case as there is no input terminal available. In short: Something is wrong with your sudo configuration. You can try to copy the contents of /etc/sudoers.d/openfortigui into /etc/sudoers and try again. But as Bullseye is not really released now it can also be some OS bug. |
I was running it in the command line terminal, there was just no output there whatsoever. I did find the logs though. I suspect this issue may be because Linux Mint 20 changes the name of the release to no longer match Ubuntu (it's 'ulyana' now but based on Ubuntu 'focal'). This was just starting the gui and clicking on connect on the one entry I have added:
There was no effect within the GUI, and the VPN didn't connect. I am otherwise able to connect openfortivpn with the same values I am using via the CLI. |
I suspect for Mint 20 this list also needs to include 'ulyana': f84df66#diff-679ac72c3b2af32ee1c0fa28feb4dbedR1171 Output of
They used to mirror the Ubuntu releases they were based on, but it appears they stopped doing that somewhere along the way. |
From your logs:
@blitzd I've not used Mint with Openfortigui, but what theinvisible posted to OP may affect you, as well. Have you checked my notes? We may be on a different system, but I fiddle with my overall setup quite a bit so what affects me may be similar for others with non standard/"supported" setups, too. |
Having same issue:
Any solution? At the same time Linux Mint 19.3 MATE it works. I also notice, that trusted certification is not available in Linux Mint 20 Cinnamon. Currently found a workaround:
|
@angela-d Sorry for the late reply. I retried again today after a long time and the error disappeared. I'm still not able to connect to my VPN because the program doesn't prompt me to insert the OTP, but that's another issue. I checked my
In my
My current openfortigui version is 0.9.3. |
I'm not sure we're are in the same problem, but a workaround that works for me is start it from the command line with sudo, like: No other way works for me, and it seems to be something specific with openfortigui. |
Strange, but when SUDO -E Option setting enabled, it will not query certificate. So I first disable that option, then I get certificate. But even I run |
Indeed, was a bit late to update project site. There is now 0.9.5 available, also a real build .deb package for bullseye is now available: http://apt.iteas.at/iteas/pool/main/o/openfortigui/openfortigui_0.9.5-1_amd64_bullseye.deb |
Just to keep the thread, In the latest version, when trying to connect as a regular user, I get the following logs.
|
This means your sudo ist not configured correctly for your user, best is to start with this sample configuration and adjust to your system: https://github.com/theinvisible/openfortigui/blob/master/openfortigui/sudo/openfortigui |
No, my sudo is working fine (it is autoconfigured by Openfortigui), just VPN certificate was outdated. Now it works again. Haven't fully tested everything. I'm just user and not VPN-server admin. |
Hi! Debian 11 bookworm (in "testing" release) Running nonGUI with "sudo openfortivpn" connects OK. (v.1.17) Running GUI (v 0.9.5) with/without sudo opens OK, but when connnecting to VPN nothing happens and error shows up in "journalctl":
|
Oops! Enabling checkbox: |
Thank you @edmundlaugasson ! This works.
|
Solved in Debian 12, using Solution with screenshot in #189 |
Thats a NetworkManager plugin and has nothing to do whit OpenfortiGUI |
I'm actually using OpenFortiGUI v0.9.2-1 on my Debian testing "Bullseye" system, installed from the https://apt.iteas.at/iteas APT repository for "buster" distribution.
Clicking on "Connect" button does not have any effect. The underlying cause can be found in the logs:
This looks like a long time recurrent error in Debian and Debian based distros (e.g. Ubuntu), and I detected its occurrence is intermittent between versions: the errors seems to be fixed in certain versions and then reappears in new ones.
The setting "SUDO -E Option" is already enabled. It is enabled by default.
I already tried several times to clean up the program configuration in my home dir.
The text was updated successfully, but these errors were encountered: