-
-
Notifications
You must be signed in to change notification settings - Fork 979
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
Manual validation feature for http-01 and tls-sni-01 challenges #60
Comments
I had a quick look at what the "manual" plugin does for the official client. |
Curl commands are not necessary. I think just printing the challenge with some instructions and waiting user's action to continue would be sufficient. For example, something like this for http-01:
|
+1 |
1 similar comment
+1 |
Is there a way to use this for an automated process of what an admin would do with it? I am interested in getting a cert that covers a group of machines, say 20 subdomains where each subdomain is only hosted from one machine in a way to avoid rate limits. |
@Gaillard Why not get a SAN cert for the 20 subdomains and then distribute them across your machines? |
Wondering if this is still necessary anymore; and even if so, if it is a good idea at all. The goal is to automate the process of managing certificates. If there a manual step is possible, then we fall short of that and people continue to rely on manual ways. |
When we cannot run an ACME client on the target server a "manual" mode for the
http-01
andtls-sni-01
challenges would be helpful.Adding
--manual
flag torun
command can be a solution imho.Btw, Let's Encrypt client has a plugin for this.
The text was updated successfully, but these errors were encountered: