Hi there,
My MacBook is running on the MacOS 26 beta. However, Ziti doesn’t seem to work on it. The buttons within Ziti Desktop Edge don’t function For example, the “Turn Ziti On“ button just doesn’t do anything anymore.
I need to add a new profile to Ziti but I can’t configure MFA because the buttons within the apps don’t work at all. Does anyone else have this issue? And is there a way for me to setup my new profile? Because I can’t use the app at all now.
Thanks!
Hi @mingus28. Welcome to the OpenZiti discourse, and thanks for letting us know about the issue with macOS 26! I’ve been working with the iOS 26 betas without issue, but to be honest I haven’t updated my Mac systems to 26 yet. Your post is a wake up call for me! I’ll check it out shortly.
I’ve seen this after updating before. Rebooting will likely fix the issue. If you don’t want to reboot, you might be able to remove the Ziti app and then manually remove Ziti under Settings/VPN, and re-install.
Hi @smilindave26 ! Thanks for the reply. Unfortunately, this has been going on for a few weeks. I’ve already rebooted, reinstalled, and removed the VPN configuration but sadly, none of it worked.
Hi! Thanks for the reply! I hope you can find something! Thanks 
You bet! Although I’m sorry to say that I haven’t gotten very far yet. I was hoping to install Tahoe in a Parallels VM, but apparently there are restrictions on what you can do in a macOS VM - including signing into the App Store or (more crucial for me) signing into Xcode (which of course requires getting Xcode first, which seems to only be available from the App Store these days…).
So I’m trying a few things to get a working Tahoe install with Ziti Desktop Edge on it. If I’m still striking out with the VM route out by tomorrow then I’ll take the plunge and install the developer beta on my M1 rig.
In the meantime if you could send me the “Application” and “Packet Tunnel” logs (“Z” menu –> “Logging”) by DM I might see something useful in them. You can DM them to me here or email at scarey@netfoundry.io if DMing with attachments isn’t working for you.
Thanks!
Thanks for the logs, that’s exactly what I was looking for. I see a couple of interesting things.
First, it looks like the private key for your identity are no longer in the keychain. The key would have been stored in the local keychain, not iCloud. Is there any chance you migrated to a new system and didn’t backup/restore your local keychain(s)? You mention this is a new profile so probably not.
[2025-08-20T06:49:32:564Z] INFO CZiti:ZitiTunnel.swift:208 loadAndRunZiti() Starting 71arxU2-u5:"Optional("XXXXXX (1).jwt")" at https://XXXXXX.YY:8441
[2025-08-20T06:49:32:622Z] ERROR CZiti:ZitiKeychain.swift:307 getCertificate() The specified item could not be found in the keychain.
[2025-08-20T06:49:32:622Z] ERROR CZiti:Ziti.swift:390 run() unable to retrieve certificates
The timestamp is also noteworthy. The last time the tunnel attempted to start was a couple of weeks ago.
Secondly (and probably secondarily) it looks like the Ziti Desktop Edge app isn’t allowed to post notifications:
[2025-08-20T06:49:32:626Z] WARN PacketTunnelProvider:UserNotifications.swift:107 post() Not authorized to send notifications
This is probably why the “Turn Ziti On” button seems to just do nothing. I’m guessing you’d at least get some indication that something was broken in the notification.
I’ve run out of things to try for getting Ziti Desktop Edge running in a macOS VM, so I’m going to put the Tahoe beta on my dev box and see if I see what you’re seeing.
Are you successfully enrolling the identities before this happens?
Thanks for checking! I did indeed make a new profile, but that’s because my Ziti environment had to be rebuild for other reasons. I installed 26 beta before I needed a new profile, and I had the same issue there. on my old, working profile.
An interesting thing to note is that I WAS able to connect with my old profile on the MacOS 26 beta using a very specific way. The ziti icon in the control panel (top right of the screen) was fully functional. I was able to connect and use MFA. Because I wasn’t using the buttons in the app, but the Dock version of Ziti.
However, since I had to make a new profile, this method doesn’t work for me anymore, because I need to configure MFA before I’m able to connect, and unfortunately, that only seems to be possible within the app.
I’m running macOS 26 now, and I think I’m seeing the same issue that brought you here. The “Turn Ziti On/Off” button in the main window is completely inactive. I’m running an unreleased version of the app so you wouldn’t see this, but there are other (new) elements in the UI that are also not active. Breakpoints that I set in the action handler functions are never even hit.
I am still able to connect through the “Z” menu though. If that still isn’t working for it’s worth trying to start the tunnel from the VPN section of the System Setting app.
I’m looking into the UI issue, I’ll let you know when I figure it out.
Thanks!
Thanks for the useful update! The Z menu does work, but the problem is that I cannot make a connection without MFA set up. And in order to set up MFA, I need the functioning button in the app where I can set it up. So as long as there is no way for me to configure MFA, I will not be able to connect.
This issue is fixed with Ziti Desktop Edge version 2.51. I just submitted it to the macOS App Store for review, so if all goes well you should see it there later today or tomorrow.
Thanks again!
You legend! Thanks a lot, it works great now.
Thanks for the very quick support and fix!
Very sorry, I'm gonna have to reopen this thread again 
The buttons work! But when I press “Enroll“ to setup MFA, the app crashes. I’ll send you a log via e-mail
I’m sorry you’re still having problems. I’m looking into it, but so far I’m not seeing the enroll/mfa issue that you’re having now.
Unfortunately the crash report that you sent isn’t immediately revealing as it is “unsymbolicated”. I can look at mapping the addresses in it to symbols in the application. In the meantime could you set your log level to TRACE (in the “Z” menu) and send me the Packet Tunnel and Application logs after attempting another enrollment?
Thanks.
Thanks for the reply! TRACE logs have just been sent!
The logs indicate that the connection to your controller is timing out when the enrollment is attempted:
(26802)[2025-09-05T09:01:26.633Z] VERBOSE ziti-sdk:ziti_ctrl.c:145 start_request() ctrl[https://openziti.2.24x7.nl:8451] starting GET[/.well-known/est/cacerts]
(26802)[2025-09-05T09:01:41.643Z] WARN ziti-sdk:ziti_ctrl.c:177 ctrl_resp_cb() ctrl[https://XXXXXX.YY:8451] request failed: -60(connection timed out)
(26802)[2025-09-05T09:01:41.643Z] WARN ziti-sdk:ziti_ctrl.c:336 internal_version_cb() ctrl[https://XXXXX.YY:8451] CONTROLLER_UNAVAILABLE(connection timed out)
Initially I tried to reproduce this by simply stopping my controller for the enrollment attempt, but that resulted in a “connection refused” error and Ziti Desktop Edge did not crash. Then I crafted a jwt with a controller address that was unreachable from my Mac. When enrolling this jwt I do see a connection timeout error before Ziti Desktop Edge crashes.
Now that I can reproduce this I’ll look into why connection timeouts seem to be a special case that leads to a crash. I imagine that you’ll be running without issue once you fix whatever is causing your controller connections to time out.
The crash was a mistake on my end, I just found this out. You mentioned in your e-mail that the address might be incorrect. I contacted the admin of my Ziti environment and he might have shared an old JWT profile with me. I requested another one and now it works with the correct address.
Sorry for the inconvenience there, and thanks again for your help. Thank you so much!
Awesome, thanks for the update! Regardless the client should not crash though. I’ll create an issue for this and look into it.
Thanks again!
For reference, I wrote up ziti_enroll leads to crash when controller connection fails · Issue #910 · openziti/ziti-sdk-c · GitHub to track the crash that you saw when enrolling with an invalid/old controller.