FortiClient issues on MacOS

Hi @akmal,

Are you using SAML authentication? Can you try a different FortiClient version?

Regards,

Hi @akmal,

Can you try to follow this document and make sure everything is properly configured on MAC "https://docs.fortinet.com/document/forticlient/7.2.2/macos-release-notes/223986/special-notices". 

Regards,
Minh

Hi!

No, just using a login/password mode. No SAML or other integrations. Tried to lower 7.xx version, didn't help.

Verified all security preferences listed in the reference doc. It all looks correct.

The only thing, I didn't find anything in Added Extensions settings.

The FortiClient Tray icon is successfully loaded though.

When I try to connect, it's just stuck saying connecting. I don't see any network requests from forticlient.

I checked all my LittleSnitch rules and everything related to FortiClient software are allowed to access the network.

Thanks.

Dear Team,

 from the macOS, if the Remote Gateway is configured as IP, the VPN is connecting, however if the Remote Gateway is configured as domain, the VPN is not connecting and getting an error 'state fatal decode error
ssl_ accept failed, 1: unexpected EOF while reading

Please check and connact u us

Hi!

Any updates? Can you help?

I have exactly the same problem, but in Ventura (13.6).

I have tried all different sub-versions of version 7 of FortiClient VPN, and the same happens.

I have tried every solution I can find online in forums, and checked all the security settings, unistalled the antivirus (SentinelOne) that we have, restarted a number of times, but nothing works.

I have looked in the log files for FortiClient, and the system and found the following

FortiTray	os_unix.c:46922: (2) open(/Library/Application Support/Fortinet/FortiClient/data/endpoint_message.db) - No such file or directory   [sqlite3:EROR] sqlite3_util:46 error opening message db: unable to open database file  [LIBAVENG:EROR] av_api:316 failed to load /Library/Application Support/Fortinet/FortiClient/bin/libav.dylib: No such file or directory  [update:EROR] fcn_upgrade:1269 failed to load av engine /Library/Application Support/Fortinet/FortiClient/bin/libav.dylib  [FortiTray:EROR] ConfigManager.swift:1749 Data corrupted: Context(codingPath: [], debugDescription: "The given data was not a valid property list.", underlyingError: Optional(Error Domain=NSCocoaErrorDomain Code=3840 "Cannot parse a NULL or zero-length data" UserInfo={NSDebugDescription=Cannot parse a NULL or zero-length data}))

In these folders, the files it is looking for is missing. It seems like the install is not complete.

We have the same problem on two computers.

I just worked through this same issue this morning.  Initially, I had no issues with 7.2.1 on Sonoma 14.0, but when I upgraded to 14.1 (23B73), I upgraded to FortiClient VPN 7.2.2 and it quit working at that time with the same unable to open database file error.

I followed the Fortinet MacOS special notice and confirmed that systemextensionsctl showed all of the Fortinet extensions showed as [Active Enabled] but still nothing worked even after multiple uninstalls and reinstalls of various versions.

The way I was able to get it to work was to change my system startup security level to reduced security and allow user management of kernel extensions.

Steps to fix that worked for me.

1) have the client installed and broken with the db error and extensions showing as enabled. (May not be necessary to be in this situation)

2) open system preferences - go to Privacy and Security and click on Enable System Extensions.

3) Follow directions to change system startup security level to reduced security and check box to allow user management of kernel extensions.

4) Uninstall and reinstall FortiClient VPN - It is now able to prompt you to allow it to add VPN profiles during the install.

For me, the client functioned correctly after this. Next step will be to test if it continues to work after re-enabling the high startup system security setting.