uptime-kuma: Matrix - Unable to verify the first certificate
⚠️ Please verify that this bug has NOT been raised before.
- I checked and didn’t find similar issue
🛡️ Security Policy
- I agree to have read this project Security Policy
📝 Describe your problem
I set Matrix (Synapse) as notification-provider but when I send a test-message, I get an error.
and Log:
Now my question, how can I install my self-signed RootCA or deactivate TLS-Check?
PS.: Uptime-Kuma has a Proxy over Traefik
I import the CA Certificate on the host, with curl -XPOST -d '{"type": "m.login.password", "identifier": {"user": "botusername", "type": "m.id.user"}, "password": "passwordforuser"}' "https://home.server/_matrix/client/r0/login" I became a right output without faults.
🐻 Uptime-Kuma Version
1.17.1
💻 Operating System and Arch
Ubuntu 20.04.4 LTS
🌐 Browser
GC 103.0+
🐋 Docker Version
20.10.17
🟩 NodeJS Version
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 23
In the case of certificates issued from Letsencrypt etc… the full chain of certificates including the CA (certificate authority), the intermediate CA certificate as well as your own domain’s issued certificate must be supplied added to your service (e.g. homebridge / nginx etc… must use the fullchain.pem which contains the full chain) or some devices will be unable to verify the trust chain from your domain’s certificate back to a trusted root CA certificate due to the missing middle link of the intermediate certificates.
This issue was originally filed by someone trying to use their own root CA and sub-certificates (I think). If using your own certificate authority, the details of adding the new CA certificates/trust chain are detailed in https://github.com/louislam/uptime-kuma/issues/1380 using the NODE_EXTRA_CA_CERTS environment variable.
so for my problem with homebridge (via node.js) the solution was simple. In the config of homebridge I just changed the path to
cert.pemtofullchain.pem.Can no one help?