Closed alexzorin closed 2 months ago
This is happening to real users too: https://community.letsencrypt.org/t/certbot-1-21-webroot-http-500-1-20-works/164870/9
I was able to acquire it using the certbot command despite the same problem I had
Thanks
We've made a lot of changes to Certbot since this issue was opened. If you still have this issue with an up-to-date version of Certbot, can you please add a comment letting us know? This helps us to better see what issues are still affecting our users. If there is no activity in the next 30 days, this issue will be automatically closed.
This issue has been closed due to lack of activity, but if you think it should be reopened, please open a new issue with a link to this one and we'll take a look.
I encountered the same issue and was able to resolve it by granting administrator full permissions to the <webroot>/.well-known
folder. This adjustment allowed the necessary access and resolved the problem. Hope this helps others facing the same issue!
This is a reopening of #8597. I suspect there is more than one cause to this error message. I've struggled with this while testing #9054.
My operating system is (include version):
Windows Server 2019
I installed Certbot with (snap, OS package manager, pip, certbot-auto, etc):
git master @ https://github.com/certbot/certbot/commit/d250d341934448e9b4a712f9c7801d655256cbd8
I ran this command and it produced this output:
Certbot's behavior differed from what I expected because:
The webroot plugin shouldn't be crashing with a permissions error.
It looks like in
_copy_win_ownership
, when Certbot tries to copy the owner (SYSTEM
) from the source folder (C:\inetpub\wwwroot
) to the destination folder (C:\inetpub\wwwroot\.well-known
), Windows spits out this error.If I repeat the same Certbot command 2 or 3 times more, it will issue the certificate, because it will create
.well-known
, crash, createacme-challenge
, crash, then finally create the challenge file and succeed.This is a stock standard Windows 2019 server from binarylane.com.au with IIS installed. If it's helpful, I can provide a virtual machine where this issue occurs.
cc @adferrand
Here is a Certbot log showing the issue (if available):