mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
unable to get local issuer certificate (when setting up notifications to mattermost) #762
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#762
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DanielMabbett on GitHub (Jan 20, 2022).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ 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:
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