Certbot fail to give cert

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:kaidesign.uk

I ran this command: certbot --nginx -d kai.kaidesign.uk

It produced this output:
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: kai.kaidesign.uk
Type: dns
Detail: DNS problem: SERVFAIL looking up A for kai.kaidesign.uk - the domain's nameservers may be malfunctioning; no valid AAAA records found for kai.kaidesign.uk

My web server is (include version):

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

My hosting provider, if applicable, is:

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):1.22.0

Glad to see you have a new domain name. But, you are still missing an A or AAAA record that points to your server. You could also use the DNS Challenge instead now that you have Cloudflare as your DNS. See the Certbot docs for how that works.

https://eff-certbot.readthedocs.io/en/stable/using.html#dns-plugins

3 Likes

i alaready created a A point with my server ip address now it gives me this error

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: kai.kaidesign.uk
Type: dns
Detail: no valid A records found for kai.kaidesign.uk; no valid AAAA records found for kai.kaidesign.uk

Yes, I see now. The IP address is a private IP address so cannot be used by the Let's Encrypt Servers to validate your domain. It is not missing but is just not valid for this purpose. Using the HTTP Challenge as you are requires the LE Server to make an HTTP request to your domain but cannot with a private IP.

It's OK to have a private IP address in the DNS for your own purpose. But, you will need to use the DNS Challenge in this case. I already provided the links for this.

Also see this:

5 Likes

The certbot-dns-cloudflare documentation has some examples that show you how to obtain a certificate in your situation. You'll need to install the python3-certbot-dns-cloudflare package first. Congrats on the domain.

4 Likes

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