Can't open console Forticlient VPN 7.4 In Sonoma

[lobo0621]

Hello everyone,

I recently upgraded from FortiClient VPN 7.2 to FortiClient VPN 7.4 on macOS Sonoma. However, I'm encountering a persistent issue where the application crashes immediately after briefly displaying the console screen. I've attempted reinstalling and deleting the /Library/Application Support/Fortinet/ directory, but the problem persists.

Below is an excerpt from the crash report:

Process:               FortiClient [1711]
Path:                  /Applications/FortiClient.app/Contents/MacOS/FortiClient
Identifier:            com.fortinet.FortiClient
Version:               7.4.0.1645 (???)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2024-06-21 17:08:15.2847 +0900
OS Version:            macOS 14.5 (23F79)
Report Version:        12
Anonymous UUID:        211D612A-2605-BAE2-689D-2447A5CCDB76

...

Termination Reason:    Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process:   exc handler [1711]

Application Specific Backtrace 0:
0   CoreFoundation                      0x0000000191a2f2ec __exceptionPreprocess + 176
1   libobjc.A.dylib                     0x0000000191516788 objc_exception_throw + 60
2   CoreFoundation                      0x0000000191963aac -[__NSSingleObjectArrayI objectAtIndex:] + 308
3   guimessenger_jyp.node               0x0000000109b4a34c _ZN13MessageSender12GetECDetailsERKN4Napi12CallbackInfoE + 264
4   guimessenger_jyp.node               0x0000000109b644ac _ZN4Napi12InstanceWrapI13MessageSenderE29InstanceMethodCallbackWrapperEP10napi_env__P20napi_callback_info__ + 84
5   Electron Framework                  0x00000001136975c8 napi_is_detached_arraybuffer + 224

If anyone has experienced a similar issue or has insights into troubleshooting this, I would greatly appreciate your advice.

Thank you in advance!

[Simo5629]

I had the same error with 7.4. When I downgraded to 7.2, it worked fine, so I think it is an issue with 7.4. Until this bug is fixed, I would suggest using 7.2.

[GiveMeVPN]

I had the same error with 7.4. But I don't have 7.2 version. 
Where can I download version 7.2?

[pginete]

You may download the FortiClient 7.2 version from Fortinet support portal (support.fortinet.com). Follow this KB https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-download-different-or-old-versions-... as a guide.

Thank you.

[earthlab1]

Dear Fortinet Team,

I am writing to inform you that the current version of FortiClient VPN (version 7.4) appears to have significant issues. Specifically, the main window does not open on macOS 14.6.1 (23G93), as mentioned in various discussions.

At present, Fortinet has not released a functioning version of FortiClient VPN for Mac users who do not have support. Despite the frequent recommendation from Fortinet to use the latest version, this version does not work.

I understand that users without a support license may not be eligible for support. However, the current situation is problematic. I kindly request that Fortinet make FortiClient VPN version 7.2, which is known to work, publicly available.

Many users are resorting to unofficial and potentially unsafe methods to obtain older versions of FortiClient. This is both risky and unreliable, as I’m sure you would agree.

Thank you for your attention to this matter.

Sincerely,

Earthlab

[xieshgnwu]

same error, and cant downgrade to 7.2

[masohle1]

Yea 7.4.0 has major issues and will not connect a lot of times. Steer clear of that right now. It’s a shame that that’s the version you get when you go to their main forticlient download page.

[jackhsueh]

They don't care and they never fix it, it was broken for several month and their customer service just DON'T CARE.

[xiesw]

If your system language is not English, then when using version 7.4, please set the system language to English. Alternatively, set the language for FortiClient to English in Settings - General - Language and Region. It's frustrating with Fortinet; after such a long time, they still haven't fixed this basic issue.