Uptime kuma ssl

Hi,
Im struggling with uptime kuma addon. I installed addon from official repo. Started and addon runs.
The problem is somehow related to ssl. I can’t open web ui while using ssl. I tried to open web ui using nabu casa remote access but I only get
ERR_CONNECTION_TIMED_OUT
I have ssl cert generated by dynu dns addon ( it’s a copy of let’s encrypt addon). I’m running nginx ssl proxy. I tried various thing to open uptime kuma web ui while logged with ssl on, but nothing seems to work.
I tried two server blocks, one with subdomain - no luck, one server block listening to 443 and 3001 - no luck.
I created another domain with uptimekuma.anotherdomain.com and I was able to connect to the dashboad using https://uptimekuma.anotherdomain.com but this is a partial solution while I still can’t access web ui using my ssl cert.
When I click on web ui I get
https://mydomain.com:3001 with message
ERR_SSL_PROTOCOL_ERROR
Tried different browsers, the same thing.
Is anyone running uptime kuma over ssl cert?

1 Like

I’m having this issue. No idea how to get it working.
Did you manage to get it fixed?

No, I didn’t. It seems that the problem is somewhere in uptime kuma and ha developers will have to make changes in uptime kuma addon to make it work with ssl.
Maybe I misunderstood some thing but as I understood this is the case.
I don’t know anyone who managed to make uptime kuma work with ssl and nabu casa cloud.

Ah that’s a shame. It’s not end of the world. But it would be nice.

I moved my installation from debian supervised to docker-compose installation. I moved everything to docker containers and now I can use ssl on uptime kuma. Yeah, you have to learn some basic things about docker, but it’s way much easier to install and manage everything in docker containers.
Now I have four subdomain with ssl certs, for home assistant, duplicati backup, syncthing and uptime kuma.
With supervised I had problem with high cpu and memory usage. Using standalone installation it’s easy to limit container cpu and memory usage and I don’t have this problem any more. High memory usage killed my server twice and than I decided to move everything to docker compose.