Push Notification cert server broken for (old) MacOS Server?

We maintained group calendars on MacOS Server until Apple removed the functionality in High Sierra. So instead, we dedicated an old surplus Mini to run MacOS Server on Sierra and continue serving just our calendars.


This worked fine until recently. The Apple Push Notification certificates need to be renewed every year, usually just a couple of clicks. But when I tried it on Friday, I got "An unexpected error (-80010) has occurred." I let it sit for a few days in case it was a temporary server outage, but it persists. I fear that perhaps Apple has decommissioned the servers that hand out the certificates. Has anyone else encountered this?

Mac mini, macOS 10.12

Posted on Dec 23, 2024 10:28 AM

Reply
Question marked as Top-ranking reply

Posted on Dec 29, 2024 9:19 AM

A subsequent communication from Apple crushes my hopes for remediation:


Following our call, I reached out to a member of our engineering team for further insight into the macOS Profile Manager email notifications you’re receiving. After discussing the matter with him, I learned that macOS Profile Manager will no longer be supported by Apple moving forward. 

As a result, to continue managing your devices in the same manner, you will need to consider an alternative Mobile Device Management (MDM) solution from a third-party provider or from Apple known as Apple Business Essentials. There are several MDM solutions available, and I recommend evaluating key aspects such as hosting options and pricing to determine which is the best fit for your organization.

For guidance on selecting an MDM solution, I recommend reviewing the following resources:
Apple Platform Deployment User Guide

Introduction to Planning Your MDM Migration


While my team in Deployment Programs Support typically assists with Apple Business Manager account administration, I believe the best team to assist you further with this issue is Apple Business Support. You can reach them at 866-902-7144, Monday through Friday, from 8:00 a.m. to 8:00 p.m. CDT.


My response was:


This mission is creeping in a direction I really don't wish to explore. 

All I want to do is establish some simple shared calendars for my family on some server that isn't public. I should think something this simple would be possible without the necessary to forge an authoritarian empire controlling every iDevice owned by my family. 

If legacy support for Mac OS Server has degraded to a point where Apple can no longer provide this service, I'll just have to add a calendar server to our existing Linux web host machine. I'd like to do this within Apple offerings, but I can't afford to take on a new administrative nightmare that exceeds the benefit obtained.


Now my effort is currently stymied by the new Linux-based calendars being perfectly accessible by every Apple device in my family except one crucial MB Air that is maxed-out at Monterey.


I miss the days when Apple stuff "just worked."

16 replies
Sort By: 
Question marked as Top-ranking reply

Dec 29, 2024 9:19 AM in response to MP_CZ

A subsequent communication from Apple crushes my hopes for remediation:


Following our call, I reached out to a member of our engineering team for further insight into the macOS Profile Manager email notifications you’re receiving. After discussing the matter with him, I learned that macOS Profile Manager will no longer be supported by Apple moving forward. 

As a result, to continue managing your devices in the same manner, you will need to consider an alternative Mobile Device Management (MDM) solution from a third-party provider or from Apple known as Apple Business Essentials. There are several MDM solutions available, and I recommend evaluating key aspects such as hosting options and pricing to determine which is the best fit for your organization.

For guidance on selecting an MDM solution, I recommend reviewing the following resources:
Apple Platform Deployment User Guide

Introduction to Planning Your MDM Migration


While my team in Deployment Programs Support typically assists with Apple Business Manager account administration, I believe the best team to assist you further with this issue is Apple Business Support. You can reach them at 866-902-7144, Monday through Friday, from 8:00 a.m. to 8:00 p.m. CDT.


My response was:


This mission is creeping in a direction I really don't wish to explore. 

All I want to do is establish some simple shared calendars for my family on some server that isn't public. I should think something this simple would be possible without the necessary to forge an authoritarian empire controlling every iDevice owned by my family. 

If legacy support for Mac OS Server has degraded to a point where Apple can no longer provide this service, I'll just have to add a calendar server to our existing Linux web host machine. I'd like to do this within Apple offerings, but I can't afford to take on a new administrative nightmare that exceeds the benefit obtained.


Now my effort is currently stymied by the new Linux-based calendars being perfectly accessible by every Apple device in my family except one crucial MB Air that is maxed-out at Monterey.


I miss the days when Apple stuff "just worked."

Reply

Dec 28, 2024 4:15 PM in response to macswe

Hi,

just want to let you know... I have same issue, "error -80010" on two macOs server - one at version 5.12.2 and one even older (version for High Sierra). But in our case our push certificates will expire at 2nd of January 2025, e.g. in lees than 14 days, so i should go through now... And I also did not see option to renew certificate on web (identity.apple.com) I see there only option to "rewoke" certificate or create new one... So i am worrying, that waiting wont help :/ (unless there is some other unusual hidden catch - like that certificates for 2025 cant be renewed in 2024, or certificates cant be renewed before expiration, so their "14 days" are meant "after expiration")

Reply

Dec 24, 2024 2:43 PM in response to macswe

Worked with a pair of extremely competent pros at Apple's push-certificate group (an actual public phone number), who advised me that the certificates aren't really "ready" for renewal until about two weeks prior, despite OS Server's nag message that gets sent a month prior; and that they can be renewed on the web at identity.apple.com if the Server isn't cooperating. So I'm waiting out the two weeks before trying again.

Reply

Jan 7, 2025 9:06 PM in response to macswe

Yes, I encountered it just today. My systems are also running Sierra...


Apple is killing its older products off, and with it my loyalty to the platform which spans decades, and the company which goes all the way back the Apple II.


I loved how easy the Server.app was to use. "Business Essentials" is a subscription - I HATE SUBSCRIPTIONS.


If I need a cobbled together solution for my mix of old and newer hardware, I might was well sell all that Apple Stock I own and try something totally different.


:(


Reply

Jan 8, 2025 3:20 AM in response to macswe

I discovered our commercial SOHO server VM, running cPanel on AlmaLinux, already had CalDAV capability installed as part of cPanel. It wasn't difficult to migrate the data and create new calendar accounts for the family. The problematic Monterey-capped 2018 MBA was replaced with a refurb M3 MBA because it was time anyway.


The only differences I can see are the loss of the "Private" checkbox option on events, and no push notifications (we have to run timed polling instead). Ironically, we could probably have achieved the same results just letting the MacOS Server push certificates expire and running timed polling on the existing system instead... but it's powered down now and that's a smaller electric bill and maintenance headache for me.


RIP, Apple Server.

Reply

Feb 8, 2025 3:39 PM in response to Daniel O'Leary

There are five separate certificates involved that have been discontinued:


  • apns:com.apple.alerts
  • apns:com.apple.calendar
  • apns:com.apple.contact
  • apns:com.apple.mail
  • apns:com.apple.mgmt


But there are other OS Server services that use certificates, such as Web Server. You can get those certificates from anywhere you want (I've been using Let's Encrypt for years, which is an entirely manual system, but not overly burdensome at four times annually). I looked into doing the same for the push certificates, but the stock capabilities of OS Server don't allow you to "import" those as you can its identity (web) certificate, they only allow you to reorder them annually from Apple's central server (which is now dead).


I didn't even try to hack a third-party certificate into the calendar slot, for fear of wasting a lot of effort only to find that our Apple laptops and phones refused to honor the new non-Apple certificate for some abstruse reason.


Reply

Feb 27, 2025 4:27 PM in response to macswe

A reference I found extremely helpful is by Brent Kearney

The final reminder about updating the keychain "certificate preferences" items identified the fact that there are two others for the MacOSX RootCA & IntCA (IntermediateCA_<host>_1) certificates.


There was some LE automation developed for a number of old systems by LE's gctwnl

https://community.letsencrypt.org/t/definitive-version-of-script-to-act-as-deploy-hook-on-macos-server-high-sierra/87305


For those moving away from OSX server - from the depths of my link collection Charles Edge wrote some amazing stuff (His domain was having some issues when I wrote this, so I've included the Wayback link)

Given I've used his site for years, a quick plug :> his books are here:

https://www.amazon.com/stores/Charles-S.-Edge/author/B001JPC32I


For reference - I received the -80010 errors this month, so I'm regretfully turning this off and turning to polling. Using a non-MFA password to renew didn't work either.

Reply

Feb 27, 2025 5:02 PM in response to JPV9

A reference I found extremely helpful is by Brent Kearney

The final reminder about updating the keychain "certificate preferences" items identified the fact that there are two others for the MacOSX RootCA & IntCA (IntermediateCA_<host>_1) certificates.


There was some LE automation developed for a number of old systems by LE's gctwnl

https://community.letsencrypt.org/t/definitive-version-of-script-to-act-as-deploy-hook-on-macos-server-high-sierra/87305


For those moving away from OSX server - from the depths of my link collection Charles Edge (RIP 2024) wrote some amazing stuff, so I've included the Wayback link.

Given I've used his site for years, and to say thank you to his family, please consider buying one of his books here:

https://www.amazon.com/stores/Charles-S.-Edge/author/B001JPC32I


For reference - I received the -80010 errors this month, so I'm regretfully turning this off and turning to polling. Using a non-MFA password to renew didn't work either.

Reply

Feb 8, 2025 2:55 PM in response to Daniel O'Leary

Don't bother to keep trying to renew your old OS Server push certificates. Apple's issuing server is dead, dead, dead.


Your best choices are to migrate to a public shared calendar server like Google, Yahoo, AOL, etc., if you aren't paranoid about your data security; or to a private cloud server if you are. Or, you can try continuing to run OS Server with no push option, only timed polling (I never tried that).


I found the "migration option" packages for maintaining your calendar service on Apple HW, suggested by Apple back in High Sierra when they removed CalDAV from OS Server, to be baroque and unsupportable back in that same time frame. I can't personally recommend any one of them.

Reply

Feb 8, 2025 3:13 PM in response to macswe

That is sad but expected news. It is a shame we cannot hack our server software to point to a different CA, and obtain new certificates that way. I believe that calendar server is not the only service affected by this, it will effect every service that uses the certificate mechanism, right?

Reply

Feb 8, 2025 3:27 PM in response to macswe

macOS Server has been ☠️ for a while. Paths out include NextCloud or alternative hosted locally, or services hosted on a Synology NAS or equivalent box, or hosted services where that’s appropriate.


For those macOS Server installs I’ve been dealing with, I’ve been incrementally migrating services off macOS Server to Synology including Time Machine server for backups, with some other services such as the VPN server and DHCP being hosted else-network such as in the network’s gateway box.


https://www.servethehome.com/apple-macos-server-formally-discontinued/


https://github.com/enzo-zsh/awesome-macos-server/


https://www.synology.com/en-us/dsm/packages


PS: mail server polling was working fine on macOS mail server, when last I was depending on mail hosted on that.

Reply

Feb 8, 2025 3:49 PM in response to MrHoffman

"incrementally migrating services off macOS Server to Synology including Time Machine server for backups"


As it turns out, I found Apple's own Time Machine migration path for local multi-device backups to be perfectly elegant and adequate -- just establish a shared-volume backup storage repository (drive) on a non-mobile, always-on machine in your facility, point your backups there, and forget them. They essentially moved all the old OS Server logic into the main OS itself. Do I assume you are doing essentially the same thing using the stock Apple software and just using Synology NAS as an autonomous server repository?

Reply

Push Notification cert server broken for (old) MacOS Server?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.