FailedProxy/Varaverk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Track what happens to every certificate, and show it on the Certs tab

Browse Source 
NPM knows what a certificate is today and nothing about what it was, so ten of them could fail
renewal for months — 1001 certbot runs, zero successes — without anything on any page saying so.
Counts start at zero and are only ever observed; only first_seen is seeded, from NPM's own date.
This commit is contained in:
Gmer4Lfe
2026-08-15 18:51:38 -04:00
parent 13de1dab82
commit 71ba0a239f
6 changed files with 554 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Plugin/unraid/pages/readme/ui-map.md
+10
View File
@@ -1196,6 +1196,16 @@ Saved into `master.conf`, which does not need to be opened by hand.
| `BUG_REPORT_LOCAL_ENABLED` | a switch | in this section | LOCAL ON — reports go to your own Gitea (see HOSTN_BUG_REPORT_* in host*.conf) and stay there. They do NOT reach the Varaverk maintainer. Turn it on if you want your own backlog. LOCAL OFF — reports open a prefilled GitHub issue you submit under your own account. |
| `BUG_REPORT_GITHUB_REPO` | a text box | in this section | — |
## Certificate History
Route: Settings tab → All settings → *Certificate History*
Saved into `master.conf`, which does not need to be opened by hand.
| Setting | Control | Where | What it does |
|---|---|---|---|
| `CERT_HISTORY_STRIKES` | a number box | in this section | expired passes before a domain is retired from the active list |
## Certificate Monitor
Reachable from: