SSL cert fails for

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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: letsencrypt certonly -w /home/byfaz_live/code/wordpress -d

It produced this output:
Challenge failed for domain
http-01 challenge for
Cleaning up challenges
Some challenges have failed.


My web server is (include version): nginx 1.14

The operating system my web server runs on is (include version): ubuntu/bionic64

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): 0.38.0

Note: This subdomain is deployed on a different server and hence there are multiple A records. shows “” as A record which is main domain however is hosted on and added as a new ‘A’ record on GoDaddy.

Thank you for your help!


Hi @Pankti

that “new A record” isn’t visible, so that can’t work.

Host T IP-Address is auth. ∑ Queries ∑ Timeout A Scottsdale/Arizona/United States (US) -, LLC Hostname: yes 1 0
AAAA yes

The check must see the new ip, not

PS: Checked manual, now the new ip address is visible -> ah, the check is one day old - 14.04.2020 12:18:10.

So first step: Recheck your domain to see your current configuration.


Yeah. But rightly shows the IP address “” for while “” for I need to issue ssl only for because the main domain has its own certificate.

Is there any solution for this ?

Hi Team,

Any suggestions for this problem ? We are unable to receive the wildcard certificate for main domain from godaddy so we need to generate the new one for subdomain. correctly points to “” and could generate the ssl. Seems it took long to propagate.


Now you have rechecked your domain.

“check your website” uses the authoritative name servers, so the results are fresh. But if you don’t recheck your domain, you see the old informations.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.