This repository has been archived by the owner on Mar 3, 2020. It is now read-only.
Fix letsencrypt certbot script #636
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previous arguments to cerbot-auto are deprecated and appear to be unsupported.
|
Just tested for a standalone install, works great. Thanks! |
rfxn
approved these changes
Jun 21, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previous arguments to cerbot-auto are deprecated and appear to be unsupported.
The setup script
extra/provision.shfails and outputs the following messages when it's run with-c certbotas an argument:Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA.The standalone specific supported challenges flag is deprecated. Please use the --preferred-challenges flag instead.There was also a message about rerunning certbot as root which I didn't capture.
Also see:
https://community.letsencrypt.org/t/important-what-you-need-to-know-about-tls-sni-validation-issues/50811
Which states that
tls-sniis not supported at the moment andhttps://letsencrypt.readthedocs.io/en/latest/using.html#standalone
which states that
--standalone-supported-challengesis deprecated.