mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Status page show https certificate expiration remaining days for self-signed certificates #3732
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#3732
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 @plegrand1 on GitHub (Nov 5, 2024).
⚠️ Please verify that this question has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
Hello,
I'm having a small problem checking the expiry of an https certificate.
This one has a particularity in that it is self-signed.
On Kuma's main page, it appears with the number of days remaining.
However, on the status page, the number of days remaining does not appear.
Is this a bug or a misconfiguration on my part?
Thank you for your help.
Best regards,
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.15
💻 Operating System and Arch
Debian
🌐 Browser
Firefox
🖥️ Deployment Environment
@apio-sys commented on GitHub (Nov 5, 2024):
For the expiration date to appear on the status page, you need to switch "Show Certificate Expiry" to on on the bottom left when editing the status page.
@plegrand1 commented on GitHub (Nov 5, 2024):
That's what I did.
The expiration date for non-self-signed certificates appears correctly with the number of days remaining.
But for self-signed certificates this information doesn't appear.
@apio-sys commented on GitHub (Nov 5, 2024):
It works for me but the expiry notice shows below the monitor with the wording "Expiration Cert SSL: nn jours" if running in French. Yours shows "Certificats HTTPS". Looks like we are not running the same version? (I have 1.23.15 also). But haven't tested with self-signed. Let me try that in a bit.
@apio-sys commented on GitHub (Nov 5, 2024):
Indeed, I could reproduce, with a self-signed cert the remaining days do not show anymore in the Status Page. We should either fix it or document that such certs will not show on status pages (since this is more a "customer facing" feature we might not want to show self-signed certs here?). Could find a why in the documentation. I guess this comes from here
/src/components/PublicGroupList.vuebut I haven't a dev environment running right now to test further.@github-actions[bot] commented on GitHub (Jan 6, 2025):
We are clearing up our old
help-issues and your issue has been open for 60 days with no activity.If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
@plegrand1 commented on GitHub (Jan 6, 2025):
Hello,
is there a solution to correct this problem?
I understand that it's just a display problem, but I'd be happy if all my certificate expirations (signed or self-signed) could be displayed on Status page.
Thanks for your help
@Tragen commented on GitHub (Jan 10, 2025):
For most self-signed certificates, I've installed my CA files where Uptime Kuma is running, but there are a lot more of internal devices which create self-signed certificates automatically, and I want to monitor them.
@github-actions[bot] commented on GitHub (Mar 11, 2025):
We are clearing up our old
help-issues and your issue has been open for 60 days with no activity.If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
@Tragen commented on GitHub (Mar 11, 2025):
Still important
@github-actions[bot] commented on GitHub (May 11, 2025):
We are clearing up our old
help-issues and your issue has been open for 60 days with no activity.If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
@Tragen commented on GitHub (May 11, 2025):
Still important
@cc13com commented on GitHub (Jun 26, 2025):
I'm also interested in this feature since a lot of my servers running with letsencrypt certificates.
@apio-sys commented on GitHub (Jun 26, 2025):
For self-signed certs, it affects status pages. Those are typically customer-facing. That was the point of this ticket. If you'd like to see other changes, I'd suggest to create a new proposition.
@cc13com This already works as expected and documented and is not related to this ticket.
@github-actions[bot] commented on GitHub (Aug 25, 2025):
We are clearing up our old
help-issues and your issue has been open for 60 days with no activity.If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
@Tragen commented on GitHub (Aug 25, 2025):
It's open because it's not fixed. Still important.
This is so lazy to just close issues.
@CommanderStorm commented on GitHub (Aug 25, 2025):
Since what you’re describing sounds more like a feature request than a help ticket, I’ve re-labeled it as such. Feel free to look into why self-signed certificates behave different.
I would be open to reviewing an PR, but won't myself invest time to develop an fix since I don't use self-signed certificates