-
Notifications
You must be signed in to change notification settings - Fork 126
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
A little misleading. "nosudo" eventually requiring sudo? #70
Comments
You don't need sudo if you use the '-f' or '--file-based' option. That creates a file in your existing webserver. You might need to change your .htaccess to allow access to the specified directory |
So do you just run the python command without sudo?
|
No, you don't run that command but use your existing webserver. Part of the validation is to retrieve a file from your web server. If you do have sudo you can run that one-line command to handle the validation request. If you don't have sudo, when you run sign_csr.py command, add the '-f' option. That eventually tells you to create a file with a specific name and content and make that available via a specified URL on your existing web server. After the validation is successful you can remove the file. |
Where do I put the
it said:
So then I removed the
and then it said:
|
|
but still, wouldn't it be possible to use another port instead of port 80? just some random high port. that might make it possible to run it without sudo? edit: sorry, just saw you wrote that here: #67 (comment) so why not make it default? |
When Let's Encrypt does the validation, it connects to your server on port 80 to retrieve the challenge. You can't change which port it connects to. There are several ways to do that:
|
This took a bit of digging for me to get, perhaps this should be more obvious in the readme, since I would imagine most people would be using this repo because they don't have root on their webserver. |
If you use the |
Am I naive?
The text was updated successfully, but these errors were encountered: