mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Certificate Dashboard #3496
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#3496
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 @hansenc0705 on GitHub (Jul 25, 2024).
📑 I have found these related issues/pull requests
Would be nice to have a central location to view the status of Certificates for all HTTPs monitors. Someplace where when it's time to update a certificate on multiple platforms I can reference this dashboard to make sure I didn't forget anything.
I just used a status page to kinda do this by adding all my monitors and then adding the cert expiry to the status and just searching for all the ones that said cert expires in xx days.
🏷️ Feature Request Type
Dashboard, Status-page, Certificate expiry
🔖 Feature description
A dashboard that gives the status of all the HTTPs monitors without having to manually add/build them into it.
✔️ Solution
A dashboard that gives the status of all the HTTPs monitors without having to manually add/build them into it.
❓ Alternatives
No response
📝 Additional Context
No response