Search Criteria
Package Details: forticlient 7.4.2.1698-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/forticlient.git (read-only, click to copy) |
---|---|
Package Base: | forticlient |
Description: | Fortinet VPN client ZTNA edition |
Upstream URL: | https://www.forticlient.com |
Keywords: | forticlient |
Licenses: | custom |
Provides: | forticlient |
Submitter: | Harms |
Maintainer: | Meowser |
Last Packager: | Meowser |
Votes: | 18 |
Popularity: | 0.011297 |
First Submitted: | 2018-10-29 20:50 (UTC) |
Last Updated: | 2024-12-18 15:51 (UTC) |
Latest Comments
1 2 3 4 5 6 7 Next › Last »
rhysperry111 commented on 2025-01-20 17:30 (UTC)
Still a no here, however I should note that my employer has been in talks with Fortinet about Linux support (even the "supported" Ubuntu package has a lot of issues) so I might be able to push some things to get looked at soon.
catrail commented on 2025-01-20 17:10 (UTC)
Anyone able to get this to work with Zero Trust? I seem to be getting stuck on error about missing /opt/forticlient/XMLs/hv.conf file.
rhysperry111 commented on 2025-01-03 14:26 (UTC)
Just checking in to see if anyone's managed to get the SSLVPN tab showing up while connected to the EMS yet?
I did some snooping around and FortiClient seems to think that the EMS is telling it that SSLVPN shouldn't be enabled for its current profile, but I have no idea why the EMS (or Forticlient) is behaving differently since this is effectively just a shuffled-around version of the Ubuntu package.
butterfiles commented on 2024-11-25 07:57 (UTC) (edited on 2024-11-25 07:59 (UTC) by butterfiles)
I was having the same problem as @guilherme44 was having and figured it out by using:
It turns out the installation processes never creates the
/etc/forticlient
directory which causes forticlient to be unable to fail to access the file(s) it needs. In this case it's specifically:/etc/forticlient/custom_machine_id.conf
.I solved the problem by:
sudo rm -rf /opt/forticlient
rm -rf ~/.config/FortiClient
sudo rm -rf /etc/forticlient
sudo mkdir /etc/forticlient
systemctl start forticlient
I'm not sure about every one else but I have to manually start /opt/forticlient/fortitray and then use the FortiClient gui to start the VPN and then get to the EMS.
Somewhat related, I'm using Sway right now and the fortitray icon appears as a red frowny face and cannot activate its menu.
guilherme44 commented on 2024-11-12 18:21 (UTC)
@rhysperry111 and @pellle87 I had the same issue. I think that is a some permission.
pellle87 commented on 2024-10-16 11:14 (UTC) (edited on 2024-10-16 11:16 (UTC) by pellle87)
@rhysperry111 I had the same problem but did install the forticlient-vpn package, then replaced it with this package and after that it works and stays connected.
However i dont seem to get any config from the EMS server but cant find any errors in logs. the whole "remote connection" tab is gone from the gui for me.
rhysperry111 commented on 2024-09-05 15:16 (UTC)
Has anybody been able to get this working for the purpose of remote connect? I'm able to connect using an invite and I show up in the EMS, however it says "Not reachable" after the first 60 seconds and never shows button for remote connect.
Musikolo commented on 2024-05-25 02:46 (UTC)
@Medowser, thanks for owning this package and keeping it up to date! I noticed line 15 of the PKGBUILD produces a warning because the indicated file doesn't exist in the package. I not only verified that's correct, but the file doesn't exist in my filesystem at all. So, I think it would be nice to drop it: - https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=forticlient#n15
Thanks!
snis commented on 2024-05-12 15:54 (UTC)
Right now the latest release is: 7.2.4.0809 with sha512sum: 417ab5bf8623f81f2894aef9e8e1415d48ca13be098de989036a99d2289953398614b9af8594608b037b9fe6e676f079ba9f6d357d96b36eea92c319fa44cd89
Update the PKGBUILD with these and i will install. For the mantainer; please update the package and maybe the description with: "Zero Trust Fabric Agent"
1 2 3 4 5 6 7 Next › Last »