-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apple Push Notification service server certificate update #404
Comments
Would you please provide an update on this? |
Personally I'm just waiting until after January 20th to see if things break in sandbox and after February 24th for production. I don't expect anyone who knows the answer to see this issue until after that. |
Hey @paul-brenner, did anything break in your sandbox since January 20th? |
Unfortunately I realized that I don't have a good way to switch over to sandbox without restarting Sygnal, which I think kills push notification for all production users until they open their app again. So I haven't been able to test. |
Thanks for the reply! After doing a bit of digging, I think Apple just wants the server that's running Sygnal to include the "SHA-2 Root : USERTrust RSA Certification Authority" certificate wherever all the other certificates are stored. In my case, Sygnal runs in a Docker container: This certificate's Given that, I don't think I or anyone else who uses one of the official Sygnal Docker images needs to do anything. |
Thanks for the digging. I see that my host (https://etke.cc/) also has the |
Apple has sent out a few emails warning of the following about required changes for APNS. Can anyone confirm whether this impacts Sygnal and, if so, how?
The text was updated successfully, but these errors were encountered: