Closed domenicdistefano closed 10 months ago
Happened to me as well, Waiting for a fix hopefully.
I'll need some logs or more information since it is working fine for me on os 11.4
Also make sure you've followed the same setup instructions:
NOTE: If you have issues connecting, try creating an uptimekuma API key and using that with NO username for the credentials. If you are still having issues,make sure you can successfully connect to http(s)://your_uptimekuma.url/metrics
I disabled the authentication in Uptime Kuma and it now works. Note: even though it says "Host\Url" in the configuration of the package, "192.168.10.3" didn't work and "http://192.168.10.3" did work.
I've seen a few reports like this. My general digestion is to use a valid ssl certificate using something like ngixproxymanager.
Could be related to: https://github.com/meichthys/uptime_kuma/issues/84
Someone fixed something in the last couple of days because I just re-ran the update on the rolled back VM and now post-update everything still works.
Previously I had to turn off authentication for the integration to work (had been working for several months). Now after upgrading the OS to 11.4 authentication is broken completely which also makes any existing / associated entities disappear.
I am running on a VM so luckily made a snapshot before the upgrade and after rolling back everything is back to working - for now....