Http challenge is failing

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:
support.gtbank.co.rw

I ran this command:
I am using java client, GitHub - shred/acme4j: Java client for ACME (Let's Encrypt)

It produced this output:
On checking the status of http challenge after 2-3 retries it gives the status as INVALID without any exception or anything.

We have build the whole infra around letsencrypt to get the certificate here at Freshworks.
I am able to issue the certificate for other domains without any issue. All http challenges are getting successed but this one.
My ca account url that I am using for this certificate is, https://acme-v02.api.letsencrypt.org/acme/acct/608488176

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): GitHub - shred/acme4j: Java client for ACME (Let's Encrypt) version: 2.12

There seems to be a DNS issue.
See: Let's Debug (letsdebug.net)

2 Likes

Authoritative nameservers:

gtbank.co.rw    nameserver = ns9.afriregister.co.ke
gtbank.co.rw    nameserver = ns3.afriregister.com

They respond with "nothing":

nslookup support.gtbank.co.rw ns9.afriregister.co.ke
nslookup support.gtbank.co.rw ns3.afriregister.com
4 Likes

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