Can’t get certificate

Help
1

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:http://dspace.av.amrita.edu/

I ran this command: sudo certbot --apache

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): dspace.av.amrita.edu
Requesting a certificate for dspace.av.amrita.edu

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: dspace.av.amrita.edu
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for dspace.av.amrita.edu - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for dspace.av.amrita.edu - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version):

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

My hosting provider, if applicable, is:

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

2

When using the http-01 challenge, which is the challenge used by the --apache authenticator plugin, the hostname in question needs to have an IP address associated with it. And it seems your dspace.av.amrita.edu hostname does not have any IP address configured. Worse even: that subdomain doesn't even exist according to the DNS nameservers. (See e.g. the NXDOMAIN result in dspace.av.amrita.edu | DNSViz)

So you need to add the IP address of that server to the DNS zone of dspace.av.amrita.edu and try again. Or use the dns-01 challenge if that host doesn't have a public IP address. But that challenge is often more difficult to implement and automate.

3 Likes
3

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