Hoder Jensen
My feedback
4 results found
-
7 votesHoder Jensen
supported this idea
·
-
83 votes
There's no plan to add a new feature for this, but it's already possible to do basic grouping by using the check alias (e.g. "Client A / Site 1"), this way you can sort by Alias in your dashboard and have your checks grouped by client/project/etc.
Hoder Jensen
supported this idea
·
-
352 votes
This is not something I have plans for in the near future because of the complexity and the wide other range of feature requests it would attract due to bigger clients (permissions, roles, audit logs, SSO, SLA, etc...). But I might do it at some point if I want to target bigger clients.
Hoder Jensen
supported this idea
·
-
8 votes
Hello,
Actually 14, 7, 1 is already the special schedule for let’s encrypt certificates. This is automatically detected by updown.io so you don’t have to, normal 1-year certificates get an additional 30 days reminder.
The threshold for let’s encrypt certs starts at 14 days because the default renew delay is 30 days before expiration: https://certbot.eff.org/docs/using.html. This can be down to 23 days with a weekly cron for example (pretty common) so that’s why we chose 14 days, so you have plenty of time to renew but still have time to investigate and fix any potential auto-renew issues.
If you’d rather renew your cert only 5 days before expiration that’s up to you but we won’t recommend or support this configuration as we consider it dangerous ☺
I’ll mark this suggestion as “Under Review” to measure the need for this.
An error occurred while saving the comment Hoder Jensen
supported this idea
·
It's also a feature, we would like to see implemented, as we have webhosts (running cPanel, but that might just be their choice and nothing to do with cPanel default config) that renew the certificate as late as the day before, but we also have older systems we monitor, where certificate renewal can't be automated, and a new certificate is installed manually as close as a week before expiry because of planning and to avoid downtime.
So per-check customization would be really nice, but until that it is possible, maybe an option to turn off globally on the account could be a "quick fix. Eg. we would disable 14 day warning, so it would be 30, 7 and 1 on normal certificates, and 7 and 1 on lets encrypt/zero ssl certificates. It would mean, we still would get warnings each 3 months on the few "weird" webhost's we have, but that's doable, until per-check customization is possible ;)