louislam/uptime-kuma

[BETA] ntfy: test button does not verify if message is sent

Open

#6050 opened on Aug 9, 2025

View on GitHub
 (6 comments) (0 reactions) (1 assignee)JavaScript (86,760 stars) (7,844 forks)batch import
A:notificationsbughelp wanted

Description

📑 I have found these related issues/pull requests

nothing found

🛡️ Security Policy

📝 Description

The test button for ntfy notifications does not verify if a message is really sent. It says always ok, if the domain is reachable.

My ntfy server is behind an auth-proxy and I opened only the following endpoints: /api/* /json /sse /status/* <- topic used in uptime kuma

The testmessage does not get sent. I can see in the proxy logs that uptime kuma gets redirected to the auth page with 302 and I can see that the token was not used for a request in ntfy (last seen), but the test always say "Sent successfully" in a green.

The official ntfy client can connect to the topic and can receive messages.

Access Log Proxy for Uptime Kuma traefik-1 | IP - - [09/Aug/2025:22:59:06 +0000] "POST / HTTP/1.1" 302 743 "-" "-" 22 "ntfy@docker" "-" 47ms

I set the server url in uptime kuma to "https://ntfy.domain.com/status" to get it working, because uptime kuma sent the post direct to https://ntfy.domain.com/

Offtopic: It would be better I think if uptime kuma uses the ntfy.domain.com/topic_name endpoints which seems to be the preferred method in ntfy documentation

👟 Reproduction steps

  1. Block ntfy endpoints with proxy
  2. open only some
  3. sent test message in uptime kuma

Configuration: server: https://ntfy.domain.com topic: status priority: 4 auth: token

👀 Expected behavior

Uptime Kuma should say that the message can't be sent.

😓 Actual Behavior

Uptime Kuma say it is sent. Even if it gets redirected via 302 to some different service.

🐻 Uptime-Kuma Version

2.0.0-beta.3

💻 Operating System and Arch

Debian 13

🌐 Browser

Brave

🖥️ Deployment Environment

Docker

📝 Relevant log output

Contributor guide

Tech stack
javascriptvuenodejs
Domain
backendtesting
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
understand HTTP response codesbasic Node.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the notification test button logic in the ntfy provider. Locate the file that handles sending test notifications, likely in `server/notification providers/ntfy.js` or similar. The current implementation probably only checks if the HTTP request succeeded (2xx status), but does not verify the actual delivery. To fix, the code should check for redirects (3xx) and explicitly verify that the message was accepted by ntfy (e.g., expect 200 OK and no redirect). Review the ntfy API documentation and compare with existing implementations for other notification providers like Telegram or Slack.