I’ve seen many similar problems but not this exact one.
And get this (domain name has been changed):
... Invalid response from http://mydomain.com/.well-known/acme-challenge/LJf7H3mThOewfe7ZPVHSuerctGN1lP5z5nhLVpJgjgM: ...
So I create a file in
LJf7H3mThOewfe7ZPVHSuerctGN1lP5z5nhLVpJgjgM and verify that I can access it:
# curl -i http://mydomain.com/.well-known/acme-challenge/LJf7H3mThOewfe7ZPVHSuerctGN1lP5z5nhLVpJgjgM HTTP/1.1 200 OK Date: Sat, 25 Feb 2017 01:20:39 GMT Server: Apache/2.4.18 (Ubuntu) Last-Modified: Sat, 25 Feb 2017 01:20:09 GMT ETag: "5-54950a5ab9baf" Accept-Ranges: bytes Content-Length: 5 Content-Type: text/plain haha
That works both from my host and from my local computer, so it’s accessible over the internet.
Then I run
letsencrypt renew again and get this:
... Invalid response from http://mydomain.com/.well-known/acme-challenge/kJ0HkAahabrr-Ugv6TRom07LdxU5K4nkqlxyF48MFDw ...
Note that the filename that it’s looking for has changed (from
So it seems that it picks a new random filename each time. Which means that I can’t pre-arrange for that file to be there. How do I get around this?
I also tried to do the command manually:
letsencrypt certonly --renew --email firstname.lastname@example.org -a manual -d mydomain.com -d www.mydomain.com --dry-run --agree-tos
Any got essentially the same error.
I could maybe do some apache redirect/forwarding trickery so that any url that starts with
/.well-known/acme-challenge would match some valid text file, but that seems like a lot of trouble to go to. Any easier solutions?
I’m on ubuntu 16.04 with Apache/2.4.18 and letsencrypt 4.0.1.