@matbrgz I think that ends up protected all of uptime kuma and not just the status page . But of course, one can always tinker the configs in such a way that only specific pages are protected (one has to also investigate protecting API requests to the backend etc). I think this has to be implemented in uptime kuma itself to be fixed reliably.
@girish not sure about 0 size ever, but I don't think so.
Anyway, after deleting some new .bak files from /app/data/data, Cloudron System Info now reporting a more reasonable 455Mb size for the deployed app.
Will try and keep an eye on it.
May export, uninstall, reinstall, import.
Although I think I did that once before.
Clearing all stats and shrinking database gives a 1.5Mb size.
@JLX89 have you also made sure, the the existing uptime app has been updated to the latest version with .1 instead of.0?
For me it then immediately worked.
What was a bit strange is that there is no validation for configured domains in Kuma. You simply enter it as it's domain in the dashboard and then it will be served through it. I have now my Kuma reachable from uptime.domain and the public status page at status.domain.
@luckow for reference, this is the Expression I have in my 'text' field:
I output the entire JSON body stringified because I use this webhook for multiple incoming notifications and they contain different payloads. But you can try and extrapolate from here by bringing in just the fields you need, i.e msg, monitor, etc.