Update... I finally went back to my Sept conf and vhosts files.
With the old configuration files, acme-challenge folder became
available again. So I was able to get my certs refreshed, and I
then restored the current conf files. That at least tells me it's
something in the conf files. But I really don't want to make this
my official process every three months when I refresh the certs.
I guess I'll start with an A-B comparison of the conf files. But
the only real significant change I can remember in the last three
months was enabling http 2.0. Doesn't seem to me that anything in
that area of config would be locking out folders with certain
names (??). In any case, I can brute-force this and back out
changes one by one. But if any of you have a hint as to what
could be happening causing one specifically-named folder to be
blocked (or a way to dig deeper into logs to figure it out), it'll
save me a lot of time and effort.
I have an apache install that has been up and running for
months. I use LetEncrypt for certificates. I went to renew all
of my certificates using an automated script that worked fine 3
months ago on the last refresh. It failed on every domain
saying the challenge file was not found. I put a test.html file
in /.well-known/acme-challenge folder, and tried to access it
with a browser, and it gave me a 404. After moving the
test.html file around into other folders, it was found correctly
in every folder except acme-challenge. I even renamed
acme-challenge to acme-challenge1 and acme1challenge, and
test.html was found in folders by those names. Renamed it back
to acme-challenge and I'm again getting 404. I have about 15
virtual hosts defined. Exact same situation in every virtual
host The folder specifically named "acme-challenge" is somehow
now being blocked or hidden by apache.
I'm using WAMP 3.1.3 (Apache 2.4.33). The only .htaccess file
in the entire wamp tree is in the php folder, and I'm not using
php. I'd say I haven't made any changes that would cause this
problem since the last time I refreshed certificates. But I
guess I did 'something'. But I'm clueless.
One thing I did notice.... In the browser, if I look for a
non-existent file in any other folder, I get one 404 line saying
the requested file was not found on the server. Fine. But when
I look for that same non-existent file in the
/.well-known/acme-challenge folder, I get that same line. But I
also get another line I haven't seen before that says:
Additionally, a 404 Not Found error
was encountered while trying to use an ErrorDocument to handle
So not only can't find the file, it
can't find a file to tell me it can't find the file... (???).
But this line ONLY appears when trying to get a file from that
one specific directory named 'acme-challenge'.
Help.... certs have expired....