Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
My web server is (include version): Apache 2.4.9 (through WAMP)
The operating system my web server runs on is (include version): Windows Server 2019 10.0.17763 Build 17763
My hosting provider, if applicable, is: Me
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): No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): 1.7.0
I have a .htaccess file that specifies custom ErrorDocuments for 400 401 403 404 and 500. But I kinda would like that so that when a user goes to an unintended part of the site it will retort with that. Why would updating the certificate have anything to do with that? And I’m not using any plugins to my knowlege
You are always using one authenticator plugin. Another way to check what it is is to look in /etc/letsencrypt/renewal/johnbrettbuchanan.com.conf, and look at what the authenticator line says.
Right, I understand the value in an error document. It's just that your webserver ends up in an infinite redirect loop whenever it hits an error document, probably because you have misconfigured it some way.
Quite possibly it has nothing to do with it - that all depends on what authenticator plugin you are using.