starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Self signed certificate Rocketchat notifications #875

New issue

Open

opened 2026-02-28 02:02:09 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:02:09 -05:00

Owner

Originally created by @Paulpatou on GitHub (Feb 28, 2022).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

New Notification

🔖 Feature description

Is it possible to add a self-signed certificate for notifications with Rocketchat ?

I currently have an alert about this

Debug log in docker =>

✔️ Solution

I tried NODE_TLS_REJECT_UNAUTHORIZED: 0 as indicated here #19 but it doesn't work

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @Paulpatou on GitHub (Feb 28, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Notification ### 🔖 Feature description Is it possible to add a self-signed certificate for notifications with Rocketchat ? I currently have an alert about this ![Self_signed cleaned](https://user-images.githubusercontent.com/33478981/155946640-89848113-ae6c-4315-9abe-4cc370e0f11c.png) Debug log in docker => ![error_selfsigned cleaned](https://user-images.githubusercontent.com/33478981/155946665-fac4b36d-2a7c-4783-a8e0-bd35689a835f.png) ### ✔️ Solution I tried `NODE_TLS_REJECT_UNAUTHORIZED: 0` as indicated here #19 but it doesn't work ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:notifications

labels

2026-02-28 02:02:09 -05:00

deekerman commented

2026-02-28 02:02:11 -05:00

Author

Owner

@jkoppen89 commented on GitHub (Jan 17, 2025):

Hi,

I've got the same error but using with Gotify.

Error: Error: AxiosError: Request failed with status code 404
at Gotify.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)
at Gotify.send (/app/server/notification-providers/gotify.js:23:18)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Socket.<anonymous> (/app/server/server.js:1304:27)

@jkoppen89 commented on GitHub (Jan 17, 2025): Hi, I've got the same error but using with Gotify. `Error: Error: AxiosError: Request failed with status code 404` ` at Gotify.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)` ` at Gotify.send (/app/server/notification-providers/gotify.js:23:18)` ` at process.processTicksAndRejections (node:internal/process/task_queues:95:5)` ` at async Socket.<anonymous> (/app/server/server.js:1304:27)`

deekerman commented

2026-02-28 02:02:13 -05:00

Author

Owner

@demaniak commented on GitHub (Jan 21, 2025):

I managed to get a SmallStep-CA selfhosted cert working by adding a env variable like so:

- NODE_EXTRA_CA_CERTS=/app/data/docker-tls/root_ca.crt

Where "/app/data/docker-tls" is a path, that in my case, is being bind mounted into the container from an external source.

The "root_ca.crt" is the root certificate generated by smallstep-ca

Could something like that maybe help with your selfsigned situation @Paulpatou ?

@demaniak commented on GitHub (Jan 21, 2025): I managed to get a SmallStep-CA selfhosted cert working by adding a env variable like so: ``` - NODE_EXTRA_CA_CERTS=/app/data/docker-tls/root_ca.crt ``` Where "/app/data/docker-tls" is a path, that in my case, is being bind mounted into the container from an external source. The "root_ca.crt" is the root certificate generated by smallstep-ca Could something like that maybe help with your selfsigned situation @Paulpatou ?

deekerman commented

2026-02-28 02:02:13 -05:00

Author

Owner

@raxod502 commented on GitHub (Feb 3, 2025):

NODE_EXTRA_CA_CERTS is the recommended approach and is documented at https://github.com/louislam/uptime-kuma/wiki/Environment-Variables.

@raxod502 commented on GitHub (Feb 3, 2025): `NODE_EXTRA_CA_CERTS` is the recommended approach and is documented at https://github.com/louislam/uptime-kuma/wiki/Environment-Variables. Similar issues: https://github.com/louislam/uptime-kuma/issues/4514 https://github.com/louislam/uptime-kuma/issues/4302 https://github.com/louislam/uptime-kuma/issues/4000 https://github.com/louislam/uptime-kuma/issues/1380

deekerman referenced this issue

2026-02-28 02:07:56 -05:00

MQTT monitor type doesn't store ping data. #1033