Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Information on Let's Encrypt generation / cron #74

Open
trajche opened this issue Jul 31, 2021 · 2 comments
Open

Information on Let's Encrypt generation / cron #74

trajche opened this issue Jul 31, 2021 · 2 comments

Comments

@trajche
Copy link

trajche commented Jul 31, 2021

Any information on what schedule/how often the certificate generation runs would be great. I migrated a production-ready site on a Saturday and now am left wondering if this is something that requires assistance from Seravo as the website is throwing an error Your connection is not private on browsers.

Even better would be the option to run Certbot through something like 'wp issue certificate'.

@serter
Copy link
Contributor

serter commented Aug 2, 2021

The certs are issued whenever we detect that the site's dns name points to us, this is scanned roughly 4 times per hour.
Certs are reissued near their expiration date with weeks of overlap.

In either case, the end user doesn't have to worry about it.

Thanks for the suggestion, we'll consider it for future improvements.
As the LE cert validation (http-01 or dns-01) needs A/CNAME/TXT record to work, the automation usually does the job better.

@serter serter self-assigned this Aug 2, 2021
@TeemuSuoranta
Copy link

I'd recommend also adding a tip to lower TTL before release as 1 hour TTL in domain might make SSL be delayed for 1 hour instead of next check cycle.

@ypcs ypcs unassigned serter Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants