mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1585] Broken rate limiting #1116
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#1116
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @thoughtsunificator on GitHub (Jan 31, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1585
syslog is currently being spammed with errors that basically say
It keeps spamming me about failures from 30 days ago, what the hell is going on?
how many messages did I send today? 0
yes I did restart/recreate/rebuild the container
@thoughtsunificator commented on GitHub (Jan 31, 2026):
I sure do hope (until I have to reverse engineer everything and make sure I guess?) that it's not really calling home with
the upstream-url being unset.
What's more is that I am also being spammed client-side, even though the go client/daemon is the only one that really "works" I have to workaround that broken rate limiting spam...
@binwiederhier commented on GitHub (Jan 31, 2026):
Thank you for submitting a bug ticket. Unfortunately, you didn't describe at all what's wrong, and you were also doing that in not the nicest way. If you'd like help, then you should probably be more specific of what you think is broken, and you should have a nicer tone.
We are always happy to help if you are respectful and specific.
@thoughtsunificator commented on GitHub (Jan 31, 2026):
I am not sure what else I can do beside copy pasting the logs, if you
want something else just ask I will do my best to provide. But for the time being
Rate limiting is broken as per the logs I have attached in the OP.
PS: It's not that I am not nice its' just that I being direct which is completely different. I am sorry not to be sorry if it looks that way to you or anyone.
On Sat, Jan 31, 2026 at 09:05:15AM -0800, Philipp C. Heckel wrote:
--
Cordialement,
Romain LEBESLE.
@binwiederhier commented on GitHub (Jan 31, 2026):
The logs look perfectly normal. What do you THINK is broken.
@thoughtsunificator commented on GitHub (Jan 31, 2026):
How is that perfectly normal? What is rate limiting me? I am sending
notifications through my own channels.
On Sat, Jan 31, 2026 at 09:32:02AM -0800, Philipp C. Heckel wrote:
--
Cordialement,
Romain LEBESLE.
@thoughtsunificator commented on GitHub (Jan 31, 2026):
Furthermore, I will have to repeat myself unfortunately but the rate
limiting messages mention topics that I haven't used in almost a month
so it's quite obvious that nothing is normal. So even if it did call
home for absolutely no reason there would still be something broken.
On Sat, Jan 31, 2026 at 09:32:02AM -0800, Philipp C. Heckel wrote:
--
Cordialement,
Romain LEBESLE.
@binwiederhier commented on GitHub (Jan 31, 2026):
Please refer to the manual: https://docs.ntfy.sh/config/#rate-limiting
@thoughtsunificator commented on GitHub (Jan 31, 2026):
Sure, in what section should I be looking for "Why are you messages from
1 month ago still being sent and causes you to be spammed by rate limiting messages?"
On Sat, Jan 31, 2026 at 09:37:28AM -0800, Philipp C. Heckel wrote:
--
Cordialement,
Romain LEBESLE.
@thoughtsunificator commented on GitHub (Jan 31, 2026):
I also need the section "How can I avoid being rate limited by mistake"
On Sat, Jan 31, 2026 at 09:37:28AM -0800, Philipp C. Heckel wrote:
--
Cordialement,
Romain LEBESLE.