-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot send notification when monitor is created with AutoKuma #72
Comments
Seems to be louislam/uptime-kuma#3274 right? |
Well the weird thing is, if I create the same monitor manually in uptime kuma, I receive a notification, so notification settings seem to work. Admittedly, the action button opens an empty tab, but that's not the problem here. The problem is, I don't receive any notification at all if it's created through AutoKuma. It's like there's some hidden difference between a monitor created manually and one created through uptime kuma, which causes this error. |
I'd assume that's because in the uptime-kuma UI the "url" parameter is pre-filled with "https://" even for monitor types where a url doesn't make sense, that's enough to satisfy the ntfy api. You could just replicate this in the DEFAULT_SETTINGS |
Alright I think I understood the problem. I added |
I've added a workaround to mimic the behaviour of the webui, this should allow it to work with stable UptimeKuma until the mentioned fix is rolled out on their side. |
Wow that was quick and could already test it out with the new version. Works as expected, all notifications get sent. Thanks! |
When creating a monitor with AutoKuma, the following error shows in the Uptime Kuma log when a notification should be sent:
When creating the same monitor manually in Uptime Kuma, it works and a notification is sent, so I assume it's a problem with AutoKuma, although I could be wrong. I also assumed all AutoKuma is doing is turn the notification on for all new monitors but somehow it works when creating manually vs when created with AutoKuma.
The following is my docker-compose:
I copied and adjusted a snippet from another issue.
Thanks for any help!
The text was updated successfully, but these errors were encountered: