Daniel Dekovic

Same error here. This all begin after updating to home assistant 2024.5 This is the log ``` 2024-05-02 21:33:54.032 ERROR (MainThread) [custom_components.uptime_kuma] Request timeout for 'https://uptimekuma.myserver.com/:443/metrics' 2024-05-02 21:34:24.909 ERROR (MainThread)...

I'm using ngnix with letsencrypt in docker. I bought a domain and configured some of the containers to use subdomans like https://uptimekuma.myserver.com/. Certs are renewed automatically every few months. I...

I'm using ver. 1.23.13 This is my docker-compose file: ``` uptime-kuma: image: louislam/uptime-kuma:1 container_name: uptime-kuma environment: - TZ=Europe/Zagreb volumes: - ./uptime-kuma-data:/app/data - /run/docker.sock:/run/docker.sock ports: - 3001:3001 restart: always ``` I...

I reviewed my nginx settings. I created access list to allow connections only from my local ips. I removed that from all containers I put it on and now I...

I tied to turn on/off additional options, restore it from backup, rebuild image. Nothing. The only thing I didnt try is to delete container, it's image, local files, pull it...

I think that problem is the same for uptime kuma, frigate and adguard integration connecting them over ssl. If I want to connect frigate over ssl I get timeout error...

No. I tried to add uptime kuma from hacs repository but ha wont let me add it as this integration is already built in home assistant.

Oh sorry gave you wrong info. Was working on something else. Yes, I have integration v.2.30 from HACS.

I tried and it created integration. I just used homeassistant.local. I doesnt make much sense to me. I have glances integration that is using https and it is working, no...

I'm not running addon, I'm running uptime kuma in docker container. And everything else for that matter. I can stop homeassistant container and uptime kuma is.. up with all 47...