Forticlient 7.2.2 Mac OS 14 Sonoma

[cronos6]

Hi,

I made the mistake of uninstalling an old version of Forticlient to install the 7.2.2 and since then Forticlient doesn't work for any of my clients.

When I try to log on, it gets stuck on "connecting".

I gave full disk access to both Forticlient and fctservctl2.

But I haven't enabled the "extension" which was prompted in mac OS 13 in "security and privacy" but not anymore in Mac OS 14.

How do you enable forticlient extension in Mac OS 14?

I have the same issue with older version now.

log of fortitray.log:

20231208 19:24:56 TZ=+1100 [FortiTray:INFO] AppDelegate.swift:128 App: FortiClient-7.2.2.0776
20231208 19:24:56 TZ=+1100 [FortiTray:INFO] AppDelegate.swift:129 OS: Version 14.1.2 (Build 23B92)
20231208 19:24:56 TZ=+1100 [FortiTray:INFO] AppDelegate.swift:261 Checking privileged helper.
20231208 19:24:56 TZ=+1100 [FortiTray:INFO] AppDelegate.swift:270 Privileged helper was installed.
20231208 19:24:56 TZ=+1100 [FortiTray:EROR] ConfigManager.swift:1802 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}))
20231208 19:24:56 TZ=+1100 [FortiTray:INFO] AppDelegate.swift:136 App is ready
20231208 19:24:56 TZ=+1100 [FortiTray:INFO] AppDelegate.swift:149 Configuration is ready
20231208 19:24:56 TZ=+1100 [FortiTray:INFO] AppDelegate.swift:143 Privileged helper is ready
20231208 19:24:56 TZ=+1100 [FortiTray:EROR] ConfigManager.swift:1802 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}))
20231208 19:24:56 TZ=+1100 [FortiTray:EROR] AppDelegate.swift:452 Failed to get current VPN configuration, unable change VPN configuration
20231208 19:24:56 TZ=+1100 [FortiTray:INFO] AppDelegate.swift:155 Configuration is validated
20231208 19:24:56 TZ=+1100 [FortiTray:INFO] AppDelegate.swift:140 VPN system extension is ready
20231208 19:24:56 TZ=+1100 [FortiTray:EROR] ConfigManager.swift:1802 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"

[hbac]

Hi @cronos6,

What was the old version and how did you uninstall it? Please make sure you follow this article to uninstall: https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-uninstall-FortiClient-on-macOS/ta-p...

You can try a different FortiClient version. 

Regards, 

[cronos6]

Hi hbac,

It was 7.0, I uninstalled using the FortiClientUninstaller.app

The problem I think is how to enable forticlient extension on Mac OS 14?

Like I said in my message, I tried other older versions, same problem, it's a general installation problem on Mac OS14.

Regards

Yoan.

[funkylicious]

Hi,

I also upgrade to 14.1.2 a few days ago and installed 7.2.2.0776 and had a similar issue if not identical, because I installed the new forticlient version on top of the existing one.

I just did a uninstall of all packages/files of FortiClient and did a fresh install of FCT 7.2.2 and everything was ok afterwards.

[cronos6 · Accepted solution]

Hi,

I tried to follow the above procedure to uninstall Forticlient but it's an obsolete procedure, it doesn't work with Mac OS Sonoma. For example, trying to move the forti app to the bin give this error message "The Bin can’t be completely emptied because “FortiClient.app” is locked. To empty everything in the Bin, including locked items, press the Option key while you choose Finder > Empty Bin." Strange message as the bin in already empty.

So I tried the following:
- Close forticlient from the taskbar
- Delete the files from Library/LaunchDaemons
- Delete the files from Library/Application Support/Fortinet
- Uninstall forticlient using forticlientuninstaller.app
- Reboot the computer
- Install Forti client 7.2.2.0776

During the installation, Forti Client asked me to accepted notification from Forti Client, this pop-up wasn't there before. I accepted, checked that both FortiClient and fctservctl2 and had full disk access then rebooted my computer. It then worked!

Regards
Yoan.

[luca219]

Go to 'System Settings > General > Login Items & Extensions > Network Extensions' to modify these system extension(s)

check with

systemextensionsctl list

AH4XFXJ7DK com.fortinet.forticlient.macos.vpn.nwextension (7.0.12/0437) vpnprovider [activated enabled]

[callmeahero]

The error log suggests there’s a problem with the configuration data being corrupted, and also with the VPN system extension.

It is a NSCocoaErrorDomain and there are hundres of them which I have learned while reading that: https://meaning.bot/what+is+error+domain+nscocoaerrordomain+error+message+could+not+find+the+specifi... 

Here’s how you can try to fix it:

Enable FortiClient System Extension: On macOS 14, the system extension may need to be manually enabled:

- Go to System Settings > Privacy & Security.
- Look for any prompts to enable system extensions for FortiClient or FortiTray (related to VPN). If you see it, click Allow.

Clear Corrupted Data: The log indicates a data corruption issue ("Cannot parse a NULL or zero-length data"). This can happen if configuration files were left behind after uninstalling the old version. Try deleting FortiClient’s configuration files manually.

They are typically located in ~/Library/Application Support/FortiClient/ or ~/Library/Preferences/ and might include files like com.fortinet.forticlient.plist.

Reinstall FortiClient: Uninstall FortiClient again, make sure all residual files are removed, then reinstall FortiClient 7.2.2. Sometimes a fresh install can resolve lingering issues.

Check Disk Permissions: Ensure full disk access is granted for both FortiClient and fctservctl2, which you've already done, but double-check if there are any new permission requests after reinstalling.