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

DietPi-LetsEncrypt | Authentication method updates #2688

Merged
merged 3 commits into from
Apr 5, 2019
Merged

Conversation

MichaIng
Copy link
Owner

@MichaIng MichaIng commented Apr 5, 2019

Status: Ready

  • Changelog

Reference:

Commit list/description:

  • DietPi-LetsEncrypt | Lighttpd: Use webroot authentication method (instead of standalone) to allow CertBot auto-renewal succeed even that webserver is running (thus blocking port 80).
  • DietPi-LetsEncrypt | Apache/Nginx: Revert to --apache/--nginx module authentication. The reason to use webroot has been fixed with CertBot 0.21.0 and Debian Stretch repo now ships 0.28.0
  • DietPi-LetsEncrypt | Pre-answer sharing mail with EFF prompt with "no", to allow non-interactive run while preserving privacy: DietPi-LetsEncrypt | Pre-answer sharing mail with EFF prompt with "no" #2500
  • DietPi-LetsEncrypt | Minor coding and wording

+ DietPi-LetsEncrypt | Lighttpd: Use webroot authentication method (instead of standalone) to allow CertBot auto-renewal succeed even that webserver is running (thus blocking port 80).
+ DietPi-LetsEncrypt | Apache/Nginx: Revert to --apache/--nginx module authentication. The reason to use webroot has been fixed with CertBot 0.21.0 and Debian Stretch repo now ships 0.28.0
+ DietPi-LetsEncrypt | Pre-answer sharing mail with EFF prompt with "no", to allow non-interactive run while preserving privacy: #2500
+ DietPi-LetsEncrypt | Minor coding and wording
MichaIng added 2 commits April 5, 2019 02:23
+ CHANGELOG | DietPi-LetsEncrypt: When applying to Lighttpd, "webroot" authentication is now used instead of "standalone"
+ DietPi-LetsEncrypt | Failsafe coding
@MichaIng MichaIng merged commit 88d62aa into dev Apr 5, 2019
@MichaIng MichaIng deleted the letsencrypt branch April 5, 2019 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant