It produced this output:
-------------------------------------------------------------------------------
Processing /etc/letsencrypt/renewal/www.fsmk.org.conf
-------------------------------------------------------------------------------
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/www.fsmk.org/fullchain.pem (failure)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: www.fsmk.org
Type: unauthorized
Detail: Invalid response from
http://www.fsmk.org/.well-known/acme-challenge/muTU4SGdlS7z3hAyDF6K6VX8ajB5fFah-NOVGSa2ADw:
"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html lang="en" dir="l"
Domain: fsmk.org
Type: unauthorized
Detail: Invalid response from
http://fsmk.org/.well-known/acme-challenge/RmjeOUtXrmqaGcqkOq7sFKvpIGdn-L_kYM_IWoGQu1E:
"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html lang="en" dir="l"
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address.
My operating system is : Debian 7
My web server is (include version): apache 2.2
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Virtualmin 5
Sounds like there is a problem with your Apache configuration that is preventing access to the directory that Certbot is placing the validation content in. Can you share your Apache config? Perhaps someone would be able to spot the issue.
After disabling the .htaccess file in the weroot folder i was able to access the file placed in .well-known/acme-challenge/file but reunning certbot-auto renew --dry-run produced the same error!