element-hq
No notifications and Error: HTTP 507 on Test Push loop back
Steps to reproduce
- I log into the app 🙂
- I get a message from my friend, but I do not get a notification
- I run the "trouble shoot notifications"
Outcome
What did you expect?
I expected there to not be a problem.
What happened instead?
I get "Error: HTTP 507" on Test Push loop back, and I do not know what that means 🥲
Your phone model
FP5
Operating system version
13
Application version and app store
Element X version 25.04.3
Homeserver
matrix.org
Will you send logs?
Yes
Are you willing to provide a PR?
No
I too am struggling with notifications.
I get a different error and the first time I ran the trouble shouting I got a notification but with the final http error.
Run it again and I get a visual motivation sometimes.
I get "Error: HTTP 507" on Test Push loop back, and I do not know what that means 🥲
This HTTP error means 'insufficient storage': https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/507, although it seems like the NTFY gateway implementation uses it to warn you that you've been rate-limited: https://github.com/binwiederhier/ntfy/blob/630f2957deb670dcacfe0a338091d7561f176b9c/docs/config.md?plain=1#L1098
I get a different error and the first time I ran the trouble shouting I got a notification but with the final http error.
This may be related, but it's a different error: the 429 HTTP status code is for 'too many requests', so you're being rate-limited, either you personally or the Element X client. The solution should be the same, use a different gateway, as for the previous issue.
Thank you for the clarification! 🙂
How do I go about using another gateway?
Same question, I'm using Firebase as I thought this would be more reliable. But could switch to self hosted nfty.
I can't see how element x can be rate limited on firebase and if it's my client do you know what the limit is. I am only using to combine what's app and signal and I'm not exactly a social butterfly with hundreds of messages a day :)
Sent with Spark On 12 May 2025, 08:21 +0100, Loppansson @.***>, wrote:
Loppansson left a comment (element-hq/element-x-android#4702) Thank you for the clarification! 🙂 How do I go about using another gateway? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
How do I go about using another gateway?
You'd have to either find an alternative gateway (sorry, I don't know any myself) or self-host (https://unifiedpush.org/users/gateway/) and use your own, then in NTFY or any other push client app go to settings and change the default gateway.
Same question, I'm using Firebase as I thought this would be more reliable
Looking at your screenshot it doesn't look that way, it says your current push provider is UnifiedPush, not Firebase. In any case, the answer is the same as above.
I understand. That is unfortunatly not an option for me right now 🥲 Is that the only options for resolving the issue?
I understand. That is unfortunatly not an option for me right now 🥲 Is that the only options for resolving the issue?
Sadly, I think it is. The problem seems to be the gateway, so I don't think you can do anything else than using a different one.
Aright, thank you for your help identifying the issue 🙂 I am a bit curious tho; my account is at matrix.org. It sounds like this issue would effect other users who have an account there? I don't really know what a gateway is tho. Is the "gateway" at my end somehow?
How do I go about using another gateway?
You'd have to either find an alternative gateway (sorry, I don't know any myself) or self-host (https://unifiedpush.org/users/gateway/) and use your own, then in NTFY or any other push client app go to settings and change the default gateway.
Same question, I'm using Firebase as I thought this would be more reliable
Looking at your screenshot it doesn't look that way, it says your current push provider is UnifiedPush, not Firebase. In any case, the answer is the same as above.
Sorry I was doing some testing so you are correct I was then using UnifiedPush.
However the issue is still present.
it seems tests work but I dont receive the notification in the app for real messages.