My domain is: reports.aztreasury.gov
I ran this command: certbot certonly -d reports.aztreasury.gov
It produced this output:
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: reports.aztreasury.gov
Type: unauthorized
Detail: During secondary validation: 104.18.40.24: Invalid response from http://reports.aztreasury.gov/.well-known/acme-challenge/1CcVE9u5Fym4Jhk2Kz1npIVxthKviBvREBcw52_Haso: 403
My web server is (include version):
httpd -version
Server version: Apache/2.4.62 (Amazon Linux)
Server built: Jul 23 2024 00:00:00
The operating system my web server runs on is (include version):
Amazon Linux 2023
My hosting provider, if applicable, is: AWS
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):
certbot --version
certbot 3.0.1
I ran our website through letsdebug, and discovered that the attempt by the letsencrypt server to retrieve the verification file from my webserver is being intercepted by cloudflare's "Verifying You Are Human" page. Apparently the letsencrypt system doesn't know how to get past this, so our attempt to renew certs fails.
The only way I discovered this is from the output of letsdebug. It clearly showed the html for "Verifying You Are Human" was being returned, instead of the verification file.
Is there anything that can be done on my server or the certbot process to bypass this? Changing our dns to bypass cloudflare is an option, but short of that is there anything we can do otherwise?