Cilex
My feedback
5 results found
-
3 votes
An error occurred while saving the comment -
148 votes
This was planned for a while because initially with only the individual status pages there was no way to specify any text. But now that we have the multi-site status pages (e.g. https://demo.updown.io/), there is a free text "description" at the top, which supports links, newlines and emojis. This allows for this kind of use-case (roughly) as you can edit this field to indicate incidents, times, some emoji to catch attention on current status, link for more details, etc..
Now that we have this, I prefer to wait before implementing more specific status page features because we don't really want to become a full-fledged status page provider otherwise people will ask for MUCH more (notifications to clients, RSS, integrating other metrics, custom design, etc..) and we have enough work to spend our time on the core product (the monitoring) already ☺
An error occurred while saving the comment Cilex
commented
~~I understand that devolopping a full system, with API etc, is a big task. What about just having a simple 1-line text field, "About this page" or "See more", where we can put
- some text
- and a link a a full page on our servers with info regarding incidents, maintenance etc?~~:facepalm: How can I be sooo stupid, this already exists... so we linked the customer status page to our global man-made Status page with explanations for outages and announcements for next planned service interruptions.
-
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 Cilex
commented
Same here - using provider OVH, and we can't define when they'll renew the certificate.
-
7 votesCilex
supported this idea
·
-
25 votesCilex
supported this idea
·
Or better, allow users to define their preferred order... perhaps regexp shoud allow this?