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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: americanrevolution(dot)org
I ran this command: explained below
It produced this output: explained below
My web server is (include version): Apache 2.4.52
The operating system my web server runs on is (include version): Ubuntu 22.04
My hosting provider, if applicable, is: N/A
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.21
So we're trying to make a fresh install on the server for troubleshooting. But I can't do this because the new domain (subdomain on a different domain because we are redirecting all subdomains on the production domain to the homepage) doesn't appear with certbot --apache
The new subdomain is in sites-enabled and shows up with apachectl -S
It is difficult to offer much in the way of specific assistance when you haven't provided the domain name that you are having trouble finding with certbot.
The domain that you did mention sits behind the Cloudflare proxy. If you aren't using Full (strict) encryption, you will have an insecure site. You also have insecure TLS versions enabled in your Cloudflare account. Anything lower than TLS 1.2 hasn't been considered secure for some years now.
There are other settings in Cloudflare that can interfere with Let's Encrypt certificate issuance. Always use HTTPS is potentially one such setting.
Without more specific details, it may be hard for anyone to offer much guidance. I encourage you to share the exact certbot command that you are running and its output.
I have switched from full to full (strict) on both sites. Always use https is off. The dev domain is dev(dot)goalsarenotstrategies(dot).com. Still experiencing both issues.
