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

Changing default version to 0.4.0 #15

Merged
merged 1 commit into from
Feb 22, 2016
Merged

Changing default version to 0.4.0 #15

merged 1 commit into from
Feb 22, 2016

Conversation

serialh0bbyist
Copy link
Contributor

This should close issue #14

danzilio added a commit that referenced this pull request Feb 22, 2016
Changing default version to 0.4.0
@danzilio danzilio merged commit 70eb3eb into voxpupuli:master Feb 22, 2016
@danzilio
Copy link
Member

👍

@Kriechi
Copy link

Kriechi commented Feb 22, 2016

Thanks!

No usage of the renew command though... see here

@serialh0bbyist
Copy link
Contributor Author

@Kriechi It looks like the current command will renew it, although on a per certificate basis. From my understanding, and please correct me if I'm wrong, the current cronjob will renew, but renews each certificate rather than all at the same time. I'm assuming that if all of your letsencrypt certificates are managed via this module then the end result is the same. Is that not the case?

Running letsencrypt renew will renew all certificates that are within the renewal window (by default, certificates within 30 days of expiry). If you would like to renew a single certificate, you should call letsencrypt certonly -d with the exact same domains that are specified in the certificate you are trying to renew. For example:

letsencrypt certonly --keep-until-expiring --webroot -w /var/www/example.com -d example.com,www.example.com -w /var/www/thing -d thing.is,m.thing.is

This module essentially does the "single certificate" renewal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants