A small number of our attempts to use APNS are returning this error. Is anyone else seeing this?
OpenSSL::SSL::SSLError: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read server session ticket A
Hello,
Could everyone who's seeing this please file a bug report right away at https://developer.apple.com/bug-reporting so the APNs server team can investigate?
They do not see anything amiss on our end, and this appears to be affecting a subset of developers.
Please include this information in the bug report:
1. Your app's bundle ID
2. Your push server's IP address(es)
3. The date, time, and timezone when connections to APNs failed
4. Complete error messages from your push server
5. Please run the s_client test at Problems Connecting to the Push Service and include those results in the bug report.
Best regards,
--gc
I'm having this issue as well. No cerificate was changed on our side, just started to get errors a few days ago...
This issue seems resolved on our end (knock on wood). We haven't seen any failures for about 12 hours.
Hello,
Could everyone who's seeing this please file a bug report right away at https://developer.apple.com/bug-reporting so the APNs server team can investigate?
They do not see anything amiss on our end, and this appears to be affecting a subset of developers.
Please include this information in the bug report:
1. Your app's bundle ID
2. Your push server's IP address(es)
3. The date, time, and timezone when connections to APNs failed
4. Complete error messages from your push server
5. Please run the s_client test at Problems Connecting to the Push Service and include those results in the bug report.
Best regards,
--gc
Submitted as #25733059. Thanks for your support.
They must have found something. Error rates on my app dropped to almost 0 on the 14th 🙂
As a follow up: errors did stop suddently on April 14th. Problem is considered as solved for us. Thanks for your help!
We have seen the issue stop with no changes on our end. (Also seemed to stop around the 14th.) However, it's now happening again.
Apparently this time it was our doing, one of our many APNS certificates was expired.
