mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1286] Is there some sort of spam protection? #912
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#912
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 @lastmetroid on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1286
Hello,
I have a problem using the NTFY service, that randomly messages wont give any JSON response, mostly after rending multiple messages in a short pteriod of time, like every x seconds or so one message, randomly it happens after a while, that it stops working.
@wunter8 commented on GitHub (Mar 5, 2025):
Are you using the public ntfy.sh instance? Are you hitting the rate limits and getting a 429 HTTP error?
@lastmetroid commented on GitHub (Mar 5, 2025):
Yes, it was the rate limit. I was debugging with a Tasmota ESP32 device sending messages to it, but there was no Json feedback from the server after a while. When I then used curl, I got a error json back notfying about a rate limit. Do you maybe know why this is the case? It seems the error Json is somehow different than the normal Json the server sends. Not sure if that is optimal.
@wunter8 commented on GitHub (Mar 5, 2025):
You should get an error JSON body initially. If you keep sending messages and ignore the 429, your IP address will be (temporarily) banned. Then the connection would timeout, and you would get no response. Maybe that's what you saw?
@lastmetroid commented on GitHub (Mar 5, 2025):
Thank you for the information. That was mostly what I was seeing because of temporary IP bans. Would you be alo affected by this if you used a VPN that the IP might randomly be blocked by the NTFY server?
@wunter8 commented on GitHub (Mar 5, 2025):
The VPN's IP wouldn't be "randomly blocked," but if you or others using the VPN send requests to ntfy.sh and ignore 429 responses, the VPN's IP address could be blocked.
@lastmetroid commented on GitHub (Mar 8, 2025):
@wunter8 I sometimes get a weird respons from the server in the form:
01:24:39.005 ntfy.sh status=1 response=
or
1:27:55.391 ntfy.sh status=2 response=
what are status code 1 and 2?
@wunter8 commented on GitHub (Mar 8, 2025):
Where are you seeing that? What is it in response to?
@lastmetroid commented on GitHub (Mar 8, 2025):
I tried to do it on a ESP32 with Tasmota and Berry in the form:
tasmota.add_rule('SSerialReceived#Message',
def (value,trigger,data)
var wc = webclient()
wc.begin('https://ntfy.sh/MYTOPIC')
var status = wc.POST(f'{value}')
var response = wc.get_string()
print(f'ntfy.sh {status=} {response=}')
wc.close()
if status == 200
tasmota.cmd('SSerialSend2 WebQuerySent')
else
tasmota.cmd('SSerialSend2 WebQueryError')
end
end, 'SSerialReceivedRule1')
It most of the time works, but sometimes I get status code 1 or 2 back with no message from the NTFY server.
@wunter8 commented on GitHub (Mar 8, 2025):
I'm not sure what that is. I don't think ntfy ever returns
1or2as an HTTP code. Is it possible that is an error/exit code from thewc.POSTcommand?