Error on forticlient VPN after upgrading to 25.10

To fix the issue I upgrade to version 7.4.3.1736, this seems to fix the issue with the connection but after connecting I don't see any longer any indicator the the forticlient is running (other than checking on the sites behind the VPN).

So it seems that there will be a new release of the forticlient to be able to work properly on new releases.

7.4.0 is old. Try with 7.4.3 (latest).

 Hi @AEK the second post is the issue I'm having with the most current version as of today 7.4.3.1736, the only relevant part in the logs would be this one:

> all windows are destroyed. quit the app.

$ forticlient gui ERROR: Failed to add module "FortiClient ZTNA". Probable cause : "/opt/forticlient/libcertd.so: cannot open shared object file: No such file or directory". 17:55:22.779 › Failed to add libcertd.so: Error: Command failed: /usr/bin/modutil -add "FortiClient ZTNA" -dbdir sql:/home/jjuvan/.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".  17:55:23.288 › Server init() port number is 17:55:23.289 › Fail to retrieve port number from file. 17:55:24.290 › Server init() port number is 41631 17:55:24.291 › Main process - Websocket open ws://127.0.0.1:41631/websocket 17:55:24.294 › WindowManager handlePossibleProtocolLauncherArgs argv=["/opt/forticlient/gui/FortiClient"] 17:55:24.294 › WindowManager handleCreateMainWindow 17:55:24.310 › MAIN Starting FortiTray 17:55:24.311 › MAIN MainWindow - createWindow Platform detected: ubuntu 17:55:24.335 › web-contents-created contents.id=1 17:55:24.346 › Saml - init 17:55:24.347 › Saml - listenSamlLoginRequest 17:55:24.348 › Server init() port number is 41631 Connected 17:55:24.669 › Renderer process - Websocket open ws://127.0.0.1:41631/websocket 17:55:24.671 › compliance configDir=/home/jjuvan/.config/FortiClient/config 17:55:24.675 › MAIN did-finish-load 17:55:24.676 › MAIN ready-to-show 17:55:31.394 › IPC_RENDERER_REQUEST.LOADED 17:55:31.395 › WindowManager handleWindowLoaded 17:55:31.895 › WindowManager handlePossibleProtocolLauncherArgs argv=["/opt/forticlient/gui/FortiClient"] 17:55:31.896 › WindowManager handleCreateMainWindow 17:55:35.623 › Vpn - start doSamlConnect 17:55:37.705 › Vpn - doSamlConnect e="INVALID GATEWAY" 17:55:37.854 › IPC_RENDERER_REQUEST.SAML_LOGIN_CANCELLED err={"msg":"SSLVPN SAML request is cancelled."} 17:55:37.855 › Saml - closeServer 17:55:38.531 › Receive websocket type=FCT_VPN_DISCONNECTED 17:55:43.296 › Vpn - start doSamlConnect 17:55:44.239 › remoteInfo=[object Object] 17:55:44.240 › Saml - IPC_RENDERER_REQUEST.SAML_LOGIN url=https://vpn2.example.com:10443/remote/saml/start 17:55:44.241 › Server init() port number is 41631 17:55:44.250 › Saml - doSamlAuth samlReq={"connection_name":"bassols vpn2","url":"https://vpn2.example.com:10443/remote/saml/start","authTimeout":"120","ignoreCert":false,"type":1,"redirect":true,"redirectUrl":"https://vpn2.example.com:10443/remote/saml/auth_id","sso_port":"8020"} 17:55:44.252 › Saml - closeServer 17:55:44.252 › Saml - startServer sso_port=8020 17:55:44.254 › Server running on http://localhost:8020 17:55:44.255 › Saml - openExternal url=https://vpn2.example.com:10443/remote/saml/start?redirect=1 17:55:50.110 › Saml - redirect auth_id to tray 17:55:50.111 › Saml - closeServer 17:55:50.112 › Saml - closing server 17:55:50.122 › sendSslvpnAuthId - Failed to load template 17:55:50.124 › Events - IPC_MAIN_RESPONSE.SAML_LOGIN_VPN_RESPONSE 17:55:50.125 › Vpn - handleSAMLLoginResp samldata.length=35 17:55:50.351 › Receive websocket type=FCT_VPN_CONNECTING 17:55:50.351 › VpnHandler UNHANDLED {"isTrusted":true} 17:56:07.177 › Receive websocket type=FCT_VPN_CONNECTED 17:56:07.237 › WindowManager WindowManager - handleWindowClosed 17:56:07.238 › WindowManager WindowManager - all windows are destroyed. quit the app.

After this the connection i still up, but there is no GUI in the application to indicate that's running, I can open the gui again to disconnect, but it's not optimal