Forum Discussion
letakeda
Cirrus
CirrusF5Access | MacOS Sonoma
I upgraded my MacOS to Sonoma (the latest version of MacOS) and now F5 Access does not open
When I try to open the application, nothing happens. The icon in the up menu bar does not appear.
Is an...
Thank you for your patience. F5 Access 2.1.0 for MacOS is now available in the Apple app store. Please refer to the following resources for more information.
LiefZimmerman
Admin
AdminLatest I heard about on the case is this:
A review of the logs showed
"the server is requesting a certificate from the client and F5 Access cannot access the private key"
Guidance from there is to
"...ensure that if performing client cert auth, the client certificate is installed and accessible from F5 Access."
This is, I think, just one customers' logs, which then assumes the common thread of "performing client cert auth".
If you can confirm that you are NOT performing client cert auth and you still have an issue 'smash that reply button' and let us know.
Hope this helps.
- LiefZimmerman
this was on my mind...checking-in to see if
A) this makes sense?
and if so
B) has it unblocked anyone on this thread?
CristianMAltocumulus
Hello, For me the application is not starting and I get this error.
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------Process: F5Access [74136]
Path: /Applications/F5Access.app/Contents/MacOS/F5Access
Identifier: com.f5.access.macos
Version: 2.0.3 (2023.08011438.345)
App Item ID: 1243219105
App External ID: 859046056
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501Date/Time: 2024-04-18 22:07:29.3803 +0200
OS Version: macOS 14.4.1 (23E224)
Report Version: 12
Bridge OS Version: 8.4 (21P4222)
Anonymous UUID: 06D6BA0F-5ADB-4F97-5BB3-9ACDE16F705ESleep/Wake UUID: F3B8C650-A69E-4A9F-9E33-BB4D799F78AD
Time Awake Since Boot: 350000 seconds
Time Since Wake: 3266 secondsSystem Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process: exc handler [74136]
I think many of us have the same problem after update to version 14.4 and 14.4.1. In attachment you find entire log. Let me know if I can help you with something else but please we already wait for to long and this issue is a blocker for many of us.- LiefZimmerman
Pushing this DIRECTLY into the ticket stream - hope it brings some clarity > resolution.
Thanks CristianM
letakedaI just give up. It's amazing how a company like F5 would take this time to fix an issue. There are a lot of professionals impacted around the world.
It's really sad. It's not the professionalism I would expect from a company like that :(
- LiefZimmerman
I hear ya letakeda
and I thank you for taking the time you did / when you did - you've done enough.
Hopefully on the shoulders of your initial effort a solution will, nevertheless, be forthcoming.
(Tip: you can unfollow specific content (ahem-chatty or frustrating posts) by toggling to UNFOLLOW at the top right)