Arch Linux User Repository

Just bumped this to 7.4.3.

I'm wondering - is anyone here using some of the more advanced features of Forticlient (e.g. web filtering, USB port blocking), and if so are there any issues? There's a few libraries mentioned in the Ubuntu source[1] that aren't on this package yet.

[1] https://repo.fortinet.com/repo/forticlient/7.4/ubuntu22/dists/stable/non-free/binary-amd64/Packages

Sorry about the late response, I wasn't getting alerts for this package. I guess I need to revisit my AUR setup.

I added the change mentioned in the comment https://aur.archlinux.org/packages/forticlient#comment-1011850 to the current build. I also add @rhysperry111 as one of the co-mantainers.

@Meowser, thanks for maintaining this package. It would be greatly appreciate it if you could implement the improvements that @rhysperry111 suggested a few days ago.

Regards.

Bump.... @Meowser if you need some help I'm happy to (co-)maintain for the foreseeable future as I'm usually working with Forticlient setups daily.

It pains me so much that this is the stupidest god damn fix - but I managed to get things working just by making the directories /opt/forticlient/{XMLs,quarantine}. Seems to populate them when you sync with the EMS and now I can get remote access working (yay!).

@Meowser might be worth bumping the PKGBUILD to add those in, and possibly reworking it so that any new directories that appear in the .deb automatically get copied over.

EDIT: Found the PKGBUILD issue - you've got !emptydirs in the options=() array which removes all empty directories from the final package.

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.

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.

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.

I was having the same problem as @guilherme44 was having and figured it out by using:

strace /opt/forticlient/forticlient-cli epctrl detail

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:

1. Uninstalling forticlient
2. sudo rm -rf /opt/forticlient
3. rm -rf ~/.config/FortiClient
4. sudo rm -rf /etc/forticlient
5. Reinstall forticlient
6. BEFORE starting forticlient service sudo mkdir /etc/forticlient
7. 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.

@rhysperry111 and @pellle87 I had the same issue. I think that is a some permission.

sudo /opt/forticlient/forticlient-cli epctrl detail
fopen() failed to open UID file [2]
Failed to set machine ID file permissions [2]
fopen() failed while setting custom UID [2]

=====================================
 FortiClient License Details
=====================================
...