-
-
Notifications
You must be signed in to change notification settings - Fork 215
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
Documentation about Let's Encrypt is wrong #2614
Comments
@Flaburgan Thanks for pointing this out. @kyrofa had suggested this method in a solved issue. Could you check the Wiki and suggest alternative? I have no way of double checking that this works since my encryption is managed by reverse proxy. |
@kyrofa I'd like to suggest something like this:
and
because of: would you agree? |
Yeah whatever we put there, someone should confirm! |
I've just been hit by this 😓 so yeah, doc is wrong.
@scubamuc what about doing this after the original rm command? |
Yes, that's right @scubamuc ! Thanks! |
Hello,
After migrating my snap to another Ubuntu installation, I had to change the domain names for which Certbot had to renew the SSL certificate. The documentation says:
And then asks to run
sudo nextcloud.enable-https lets-encrypt
.If one does so, this second commands is failing with:
To fix this I had to manually recreate the
certs
and thencerbot
directories.So, the documentation looks wrong, why do we need to
rm -rf
the directories and not only the content? Or why should we remove the certificates anyway?The text was updated successfully, but these errors were encountered: