Closed haacked closed 5 years ago
It looks like you set WebRootPath
to %HOME%\site\letsencrypt
, but I suspect no environment variable expansion is taking place so I wonder if it put the challenge file under the verbatim folder "%HOME%
" (easy to check).
If the relevant issues are any indication, you should set the web root path to the expanded folder, i.e. D:\home\site\LetsEncrypt
. It should be safe as the D:\home
path is documented.
Thanks! That fixed that issue.
I'm running my target App Service from package, but I followed the instructions to set up the
%HOME%/site/letsencrypt/.well-known/acme-challenge
directory in my app and added virtual directories pointing to them.I made sure to configure the webjob app to point to
%HOME%/site/letsencrypt
via theletsencrypt:webAppName-webRootPath
setting (yes, I replacedwebAppName
with my app's actual name).With ll that, when I run the job, I can see in the log that Kudu logs that it created the file. But there's no file.
I checked within Kudu to see if it's just a problem serving the file, but the file isn't there.
I manually created the test.txt file to ensure that I was serving that directory properly. You can see that it's being served up properly. http://www.getaboard.net/.well-known/acme-challenge/test.txt
I double checked that I created the Principal correctly and gave it access to the resource group that contains both my App Service Plan and my App Service. It has the contributor role.
Any ideas on why the challenge file isn't being created?
Full logs are here: