-
Notifications
You must be signed in to change notification settings - Fork 148
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 pushes don't recover after a proxy failure #304
Comments
@MatMaul can you paste some keywords (and the stacktrace?) from the log into the issue, so that they will come up with a keyword search? |
Good idea.
And here is the one for GCM (that manages to recover afterwards):
|
Not happy news: while the proxy restarts every night (we can see the errors from my previous message in the logs every night), the bug is not triggered each time, meaning sometimes it manages to recover and keep sending APNS after the proxy is back. |
I have just noticed the following aioapns bug: Fatal1ty/aioapns#42. It sounds very similar to the symptoms described here. That bug was fixed in aioapns v3---so I am very tempted to think that this might magically work by upgrading to the latest Sygnal release, which requires at least this version: Line 77 in 5f55f42
If we can get some confirmation of this that would be ideal. |
We use sygnal with a HTTP proxy.
Sometimes our HTTP proxy restarts and is unavailable for a short period of time, returning a 503 response.
In this case we can clearly see the related errors in the logs, for both APNS and GCM.
However APNS never recovers after that, and no errors are logged after. GCM manages to recover well.
Here is the logs around the time the proxy restarts.
sygnal_crash.txt
The text was updated successfully, but these errors were encountered: