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: *.site it.click and site it.click and daildaisite.click
I ran this command:
certbot certonly --manual -d *.siteit.click -d site it.click -d daildaisite.click --preferred-challenges dns-01 --server https://acme-v02.api.letsencrypt.org/directory
and other command
certbot certonly --manual --preferred-challenges "dns-01" --server "https://acme-v02.api.letsencrypt.org/directory" --domain "*.siteit.click" --domail "siteit.click" --domain "daildaisite.click"
It produced this output:
Multi, wildcard both output normally in three code forms
My web server is (include version):
apache 2.6.2 httpd
The operating system my web server runs on is (include version):
CentOS stream9
My hosting provider, if applicable, is:
The name server is set up and only the domain is purchased from aws.com.
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
install certbot3
The web server page opens normally, and the authentication code written in the DNS of the provider through the Internet subscription line is normally printed in the nslookup -q=TXT _acme-challenge.domain. and dig _acme-challenge.domain, TXT command, but it is not printed in the toolgoogleapps.com/#TXT/_acme-challenge.domain. displayed during installation, and the certificate is not issued. Despite Google's guidance that it may take up to 72 hours, the certificate has not been issued for 3 weeks due to an error that the name server DNS could not be found. What is the cause?