starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

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

New issue

Open

opened 2026-02-28 03:56:05 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-28 03:56:05 -05:00

Owner

Originally created by @DunklerPhoenix on GitHub (Aug 9, 2025).

Originally assigned to: @ashhley04 on GitHub.

nothing found

🛡️ Security Policy

I have read and agree to Uptime Kuma's 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

Block ntfy endpoints with proxy
open only some
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

Originally created by @DunklerPhoenix on GitHub (Aug 9, 2025). Originally assigned to: @ashhley04 on GitHub. ### 📑 I have found these related issues/pull requests nothing found ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/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 ```bash session ```

deekerman added the

bug

A:notifications

help wanted

labels

2026-02-28 03:56:05 -05:00

deekerman commented

2026-02-28 03:56:08 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Aug 9, 2025):

Feel free to create an PR.
I would be happy to review it, but do not have the time to invest into this issue otherwise.
With 100s of notification providers, constant maintainer time just does not scale.

The ntfy code is here

https://github.com/louislam/uptime-kuma/blob/master/server/notification-providers/ntfy.js

Our contribution guide includes how to get an environment setup:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

@CommanderStorm commented on GitHub (Aug 9, 2025): Feel free to create an PR. I would be happy to review it, but do not have the time to invest into this issue otherwise. With 100s of notification providers, constant maintainer time just does not scale. The ntfy code is here https://github.com/louislam/uptime-kuma/blob/master/server/notification-providers/ntfy.js Our contribution guide includes how to get an environment setup: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

deekerman commented

2026-02-28 03:56:09 -05:00

Author

Owner

@ashhley04 commented on GitHub (Oct 8, 2025):

can i work on this ?

@ashhley04 commented on GitHub (Oct 8, 2025): can i work on this ?

deekerman commented

2026-02-28 03:56:09 -05:00

Author

Owner

@ashhley04 commented on GitHub (Oct 8, 2025):

please assign this issue to me

@ashhley04 commented on GitHub (Oct 8, 2025): please assign this issue to me

deekerman commented

2026-02-28 03:56:09 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 8, 2025):

shure, why not

@CommanderStorm commented on GitHub (Oct 8, 2025): shure, why not

deekerman commented

2026-02-28 03:56:09 -05:00

Author

Owner

@ashhley04 commented on GitHub (Oct 9, 2025):

sure will work on this and report within one week

On Wed, Oct 8, 2025 at 9:48 PM Frank Elsinga @.***>
wrote:

CommanderStorm left a comment (louislam/uptime-kuma#6050)
https://github.com/louislam/uptime-kuma/issues/6050#issuecomment-3382304876

shure, why not

—
Reply to this email directly, view it on GitHub
https://github.com/louislam/uptime-kuma/issues/6050#issuecomment-3382304876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGGTP2B273SKVXAHYXLJIWD3WU2L3AVCNFSM6AAAAACDQOYX62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBSGMYDIOBXGY
.
You are receiving this because you were assigned.Message ID:
@.***>

@ashhley04 commented on GitHub (Oct 9, 2025): sure will work on this and report within one week On Wed, Oct 8, 2025 at 9:48 PM Frank Elsinga ***@***.***> wrote: > *CommanderStorm* left a comment (louislam/uptime-kuma#6050) > <https://github.com/louislam/uptime-kuma/issues/6050#issuecomment-3382304876> > > shure, why not > > — > Reply to this email directly, view it on GitHub > <https://github.com/louislam/uptime-kuma/issues/6050#issuecomment-3382304876>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BGGTP2B273SKVXAHYXLJIWD3WU2L3AVCNFSM6AAAAACDQOYX62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBSGMYDIOBXGY> > . > You are receiving this because you were assigned.Message ID: > ***@***.***> >

deekerman commented

2026-02-28 03:56:09 -05:00

Author

Owner

@Anas-Dew commented on GitHub (Nov 25, 2025):

still not resolved. ntfy doesnot works

@Anas-Dew commented on GitHub (Nov 25, 2025): still not resolved. ntfy doesnot works