I have the same problem recently.
I have a CentOS 8.2 instance that will not renew its Let’s Encrypt certificate. It succeeded three months ago when setup but now the URL gets a 404 error. Since the validation file remains for such a short time I can’t be sure whether it is actually created but I did create a test.txt file which causes the same 404 error.
In Webmin config/SSL/Let’s Encrypt settings I choose “other directory” (/var/www/html) as the validation root directory. I am expecting the external URL to be http://<ip_address>/.well-known/acme-challenge/test.txt.
The result displayed in Firefox is
Not Found
The requested URL /.well-known/acme-challenge/test.txt was not found on this server.
My Webmin FQDN resolves correctly with both IPv4 and IPv6 addresses. Let’s Encrypt validation appears to prefer the IPv6 address.
In my ignorance I’m not sure whether Webmin miniserv or Apache will serve this URL. Which is it?
Neither log shows any related errors. But would I need to change the log level? and where?
Permissions seem OK and certainly the same as my other CentOS 7 instance.
I’m at a loss to know why the URL is not being served, and especially why it once was, but not now.
I have installed many updates through Webmin/Virtualmin in this interval.
The Webmin FQDN domain is not a virtual domain on this server.
Virtualmin domain LE certificates are renewing perfectly as expected.
Webmin LE certifcates have always renewed manually for me, but consistently never automatically!
Any clues that can help me troubleshoot this would be most appreciated. Especially the answer to which webserver is used by Webmin for its own FQDN.
Thanks
Webmin version 1.955
Usermin version 1.803|
Virtualmin version 6.12
Authentic theme version 9.54