Closed ZippierOstrich1 closed 2 months ago
Seems to be https://github.com/louislam/uptime-kuma/issues/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 *.url: https://
to the DEFAULT_SETTINGS. But it doesn't get added to the monitor when using type docker, I assume because the monitor type docker doesn't have the property "url".
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!