Package Details: forticlient-vpn 7.4.3.1736-1

Git Clone URL: https://aur.archlinux.org/forticlient-vpn.git (read-only, click to copy)
Package Base: forticlient-vpn
Description: Build through the official package of FortiClient VPN only
Upstream URL: https://www.fortinet.com/support/product-downloads
Keywords: FortiClient Fortinet VPN
Licenses: custom:fortinet
Conflicts: forticlient
Provides: FortiClient, fortivpn
Submitter: douglasimcabral
Maintainer: Meowser
Last Packager: Meowser
Votes: 18
Popularity: 1.28
First Submitted: 2020-09-05 13:48 (UTC)
Last Updated: 2025-04-03 03:33 (UTC)

Dependencies (23)

Required by (0)

Sources (1)

Pinned Comments

douglasimcabral commented on 2022-11-10 15:37 (UTC) (edited on 2023-03-10 00:41 (UTC) by douglasimcabral)

Community,

The Fortinet provides two products, "FortiClient EMS" and "FortiClient VPN only". This package only correspond to "FortiClient VPN only" and your lastest version is 7.0.7.0246 at 03-09-2023.

If you are interested in "FortiClient EMS", I suggest following the AUR package 'forticlient' [https://aur.archlinux.org/packages/forticlient]

Latest Comments

1 2 3 4 5 6 .. 10 Next › Last »

benz commented on 2025-05-21 11:42 (UTC)

I'm facing the same issue as idrisakintobi in the comments below, where popups are not showing up. HOWEVER... it WAS working on my machine before. I reinstalled my arch though and ever since, the dialogs are not showing up anymore. Before, they'd also show up when connecting via cli.

I suppose there is some GUI dependency missing... may that be?

Using the GUI is impossible without the dialogs being shown.

ni.mou commented on 2025-05-20 07:18 (UTC) (edited on 2025-05-20 07:26 (UTC) by ni.mou)

Same experience here.

I’d like to take this opportunity to thank the maintainers for this package.


@Maverick.Cheung a commenté le 2025-05-03 00:43 (UTC)

After update to 7.4.3.1736-1, it failed at startup:

[2025-05-03 08:36:28.436] [info]  Failed to add libcertd.so: Error: Command failed: /usr/bin/modutil -add "FortiClient ZTNA" -dbdir sql:/home/maverick/.pki/nssdb -libfile /opt/forticlient/libcertd.so -force
ERROR: Failed to add module "FortiClient ZTNA". Probable cause : "/opt/forticlient/libcertd.so: cannot open shared object file: No such file or directory".

aplnx commented on 2025-05-15 19:12 (UTC) (edited on 2025-05-21 12:11 (UTC) by aplnx)

Hello, after creating the package it asks for a PGP key. How can I solve this problem?

[cfd@alien forticlient-vpn]$ sudo pacman -U forticlient-vpn-7.4.3.1736-1-x86_64.pkg.tar.zst

loading packages...

:: Import PGP key XXXXX...XXX? [Y/n] Y

error: key "XXXXX...XXX" could not be retrieved remotely

error: missing required key in keyring

error: 'forticlient-vpn-7.4.3.1736-1-x86_64.pkg.tar.zst': unexpected error

I ended up solving my own problem. I would like to take this opportunity to thank the maintainers for this package!!

SOLUTION:

1. Export the local PGP public key to a .asc file

gpg --export -a <KEY_ID> > mykey.asc

2. Add the exported key to pacman’s keyring

sudo pacman-key --add mykey.asc

3. Locally sign (trust) the key

sudo pacman-key --lsign-key <KEY_ID>

4. Install the package

sudo pacman -U <package-name>.pkg.tar.zst

Maverick.Cheung commented on 2025-05-03 00:43 (UTC)

After update to 7.4.3.1736-1, it failed at startup:

[2025-05-03 08:36:28.436] [info]  Failed to add libcertd.so: Error: Command failed: /usr/bin/modutil -add "FortiClient ZTNA" -dbdir sql:/home/maverick/.pki/nssdb -libfile /opt/forticlient/libcertd.so -force
ERROR: Failed to add module "FortiClient ZTNA". Probable cause : "/opt/forticlient/libcertd.so: cannot open shared object file: No such file or directory".

idrisakintobi commented on 2025-04-04 01:09 (UTC) (edited on 2025-04-04 10:28 (UTC) by idrisakintobi)

Token input modal does not show up. I installed the package afresh, and I am stuck on the connecting screen. After entering my password, an “OK” and “Cancel” button appear, which I believe are meant to confirm the token input. However, there was no field to input the token. After clicking “OK,” I remained stuck on the connecting screen. Please help.

[PC]
OS: Manjaro Linux x86_64
Host: HP EliteBook 840 G5 SBKPF
Kernel: 6.12.20-2-MANJARO
[sslvpn.log]
...
20250404 10:23:41.847 TZ=+0100 [sslvpn:INFO] main:1781 State: Logging in
20250404 10:23:41.848 TZ=+0100 [sslvpn:INFO] vpn_connection:2447 /remote/info
20250404 10:23:42.009 TZ=+0100 [sslvpn:INFO] main:1781 State: Waiting user confirm remote certificate
20250404 10:23:42.009 TZ=+0100 [sslvpn:DEBG] main:1611 Create socket connection
20250404 10:23:42.054 TZ=+0100 [sslvpn:DEBG] main:1689 Message to UI: You are connecting to an untrusted server, which could put your confidential information at risk. Would you like to connect to this server?

Edited: If you're having the same issue. You can use the cli to connect. /opt/forticlient/forticlient-cli vpn

gofree commented on 2025-04-03 09:28 (UTC)

Thanks for updating the package, I noticed strange ( perhaps ) new behaviour. After connecting to vpn the window closes ( it didnt in previous version ) , still works, but sometimes I forget im connected to vpn ( as the tray is not working in gnome ). DO you have the same behaviour - can it be configured ?

Meowser commented on 2025-04-03 03:10 (UTC) (edited on 2025-04-03 03:36 (UTC) by Meowser)

I stumbled on the vpnagent fix also, but because it's not linked to a version I'm reluctant on implementing the change. I've had no luck trying to find an alternative to the intial filestore setup, but I will look into pulling from the debian repo this weekend.

  • Update - figured out the new filestore url just followed the redirect

alexbraga commented on 2025-04-03 02:39 (UTC)

For anyone having trouble with the .deb file not being downloaded, replacing the following values in the PKGBUILD file solved the problem for me:

source=("https://links.fortinet.com/forticlient/deb/vpnagent")
sha256sums=('45c465ca669d4bc6d0f1d3a93f4eb765b996e05c10f6e8e9e2db2fa6728a541c')

NOTE: Keep in mind this will download the latest version available, and the package listed here may be out of date, as it is at the moment of this writing. The sha256sums above corresponds to version 7.4.3.1736

r3f commented on 2025-03-29 16:52 (UTC)

Has anyone managed to run IKEv1 on IPsec or is this not possible in principle?