unable to get local issuer certificate (when setting up notifications to mattermost) #762

Open
opened 2026-02-28 01:57:13 -05:00 by deekerman · 0 comments
Owner

Originally created by @DanielMabbett on GitHub (Jan 20, 2022).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I am trying to set up an intergration between uptime-kuma and a mattermost instance, both certs signed by an internal CA.
I currently see this when I am clicking create in the logs:

Error: unable to get local issuer certificate 
    at Mattermost.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:32:15)
    at Mattermost.send (/app/server/notification-providers/mattermost.js:117:18)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Socket.<anonymous> (/app/server/server.js:1036:27)

Screenshot 2022-01-20 at 16 53 18

Any help would be appreciated on this to understand why this happens and steps on what I need to do here.

🐻 Uptime-Kuma Version

Version: 1.10.2

💻 Operating System and Arch

Alpine Linux v3.12

🌐 Browser

Google Chrome Version 97.0.4692.71

🐋 Docker Version

helm.sh/chart: uptime-kuma-1.1.0

🟩 NodeJS Version

No response

Originally created by @DanielMabbett on GitHub (Jan 20, 2022). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I am trying to set up an intergration between uptime-kuma and a mattermost instance, both certs signed by an internal CA. I currently see this when I am clicking create in the logs: ```log Error: unable to get local issuer certificate at Mattermost.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:32:15) at Mattermost.send (/app/server/notification-providers/mattermost.js:117:18) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:95:5) at async Socket.<anonymous> (/app/server/server.js:1036:27) ``` ![Screenshot 2022-01-20 at 16 53 18](https://user-images.githubusercontent.com/15195905/150384776-eb757831-6538-41a6-bce7-f8e5e000a953.png) Any help would be appreciated on this to understand why this happens and steps on what I need to do here. ### 🐻 Uptime-Kuma Version Version: 1.10.2 ### 💻 Operating System and Arch Alpine Linux v3.12 ### 🌐 Browser Google Chrome Version 97.0.4692.71 ### 🐋 Docker Version helm.sh/chart: uptime-kuma-1.1.0 ### 🟩 NodeJS Version _No response_
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#762
No description provided.