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
Allow letsencrypt client to pass the web root path on cmd for creation of SimplyHTTP/ACME challenge file #742
Comments
Is the existing --server-root not sufficient?
|
I don't see that option only --nginx-server-root which which for me would be
|
It doesn't matter where your webroot is. Certificates and keys are never copied to your |
Ah, you want to specify directory where SimplyHTTP challenge response files should be written (aka, automatic execution of manual plugin, without executing Python's builtin webserver)... Please update the title of this ticket to make this more clear. |
ok changed the title.. yup @kuba for creation of the well-known uris for verification :) right now I have to manually do it via
where being able to do it on cmd line
with auto creation of the .well-known file would bring manual authentication one step closer to automation that can be scripted by end user |
Mind, you can always stop your current web server and use fully automated |
Yeah unfortunately that would be a problem for other non-443 port sites running on the server. The aim is to integrate Letsencrypt into my LEMP stack's Nginx vhost auto generation routine which currently auto creates the nginx vhost for http and https (self-signed ssl) so hoping it can do that fully from command line for invoking letsencrypt client as I already have the fully running Nginx vhost for https/443 running and setup. Unfortunately, I am not a python programmer so can't do that myself for adding public web root command line support. Not sure if it's as simple as making the expected Ubuntu Apache/Nginx public web root a variable that changes depending on what's passed to the cmd line flag for web root ? If no web root flag is passed it defaults to expected Ubuntu Apache/Nginx public web roots |
I quickly created plugin that should suit your needs, @centminmod. It's not ready to be sent as PR yet, but you can still check it out... Just |
sweet @kuba thanks so much.. will doing this override and wipe the existing /etc/letsencrypt files/config and obtained ssl certs ? |
No, it will not wipe the config files. I'm a bit concerned why do you ask, though. Currently issued certificates have no much value... (https://github.com/letsencrypt/letsencrypt#disclaimer) |
Cheers @kuba the question is thinking forward for when you do go live :) Pretty sure some folks like myself would run into such a situation if living on bleeding edge :) |
Okay tried it and it works nicely with command
but if i true to skip the prompts and just text I with
I get
|
this works though
output
is there a way to pass the Agree on command line ? thanks |
okay figured it out !
perfect @kuba your work taken care of automating non-standard Ubuntu Apache/Nginx setups provided they already have the ssl vhost and web root for their respective domains setup prior !
|
This discussion is off-topic. If you have further problems please don't
piggy back on the same issue, but open a new one or come to our IRC channel
for further support.
|
@kuba oh sorry thought feedback on your plugin by a end user would be on topic :) cheers |
Related to https://community.letsencrypt.org/t/manual-authenticator-way-to-automate-the-acme-challenge-file-creation/583
Passing the webroot via the command line it would help for those sites that have non-standard web roots i.e. frameworks like Laravel and node.js web apps would likely have their /path/to/projectname/public as their web root. WHM/Cpanel, Directadmin, Webmin etc all would have their own web root paths.
If you can pass this as a variable in Letsencrypt client, it will probably be easier for respective control panels and distros to come up with their own integration methods ?
The text was updated successfully, but these errors were encountered: