I generated certificate from certbot on my VPS but there due to some issues I had to reset my VPS, can I get my certificate in this VPS again, if it already exists?

Help
1

My domain is: panel.boiihosting.fun

I ran this command: certbot certonly --nginx -d panel.boiihosting.fun

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for panel.boiihosting.fun

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

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx 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 24.04 Noble

My hosting provider, if applicable, is: RudraCloud

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

2

I'm not sure what the topic title has to do with the info you've posted. Yes, you can get a second cert for the same set of domains, but be aware of the rate limits; you can't create more than five identical certificates within seven days.

But that has nothing at all to do with the error you're seeing; that error says you don't have a valid DNS record for your domain. You'll need that in order to get a cert.

4 Likes
3

How to generate a new certificate for the same set of domains? My subdomains are correctly pointed to the IP address of server but still I am getting these errors.

4

There are no DNS A records for that domain name. I also do not see any record of you getting a certificate for that name before.

https://dns.google/query?name=panel.boiihosting.fun

5

I don't know what subdomains you're referring to, as you only shared one above--and that one (panel.boiihosting.fun) still doesn't have any A records:

dan@Dan-MacBook-Pro-2019  ~  dig panel.boiihosting.fun

; <<>> DiG 9.10.6 <<>> panel.boiihosting.fun
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52520
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;panel.boiihosting.fun.		IN	A

;; AUTHORITY SECTION:
fun.			900	IN	SOA	ns0.centralnic.net. hostmaster.centralnic.net. 814400 900 1800 6048000 3600

;; Query time: 103 msec
;; SERVER: 100.100.100.100#53(100.100.100.100)
;; WHEN: Sat Jan 25 05:19:18 EST 2025
;; MSG SIZE  rcvd: 115

In fact, no NS records are present for boiihosting.fun:

 dan@Dan-MacBook-Pro-2019  ~  dig ns boiihosting.fun

; <<>> DiG 9.10.6 <<>> ns boiihosting.fun
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27012
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;boiihosting.fun.		IN	NS

;; AUTHORITY SECTION:
fun.			900	IN	SOA	ns0.centralnic.net. hostmaster.centralnic.net. 814400 900 1800 6048000 3600

;; Query time: 102 msec
;; SERVER: 100.100.100.100#53(100.100.100.100)
;; WHEN: Sat Jan 25 05:19:48 EST 2025
;; MSG SIZE  rcvd: 109

Is that domain in fact registered?

2 Likes
6

The domain is currently suspended.

https://cf.sjr.dev/tools/check?a8a1dfdc0b764756b25359641e795bc6#whois

2 Likes
7

Yes, the domain is registered. I had generated its SSL certificate with Certbot but I reset my VPS and I don't have the privkey.pem so I am not able to obtain that certificate again for my subdomains.

8

As shown in the post right above yours, no, it isn't (at least not actively so)--it's suspended. Did you pay the registration/renewal fee?

There are no DNS records, at all, for this domain--not even NS records. Until you fix that, you won't be able to do anything with it; getting a cert should be among the lesser of your concerns right now.

5 Likes
9

Sorry for confusion, My domain was suspended and I have renewed it. But how can I solve this error with certbot to obtain SSL certificate for the subdomain(s)?

10

What error you're seeing now?

We don't have crystal balls in our possession, so we don't see what you see unless you share (post) what you see.

11

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for panel.boiihosting.fun

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

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx 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.

[This is the error I am facing while obtaining SSL certificate for my domain with certbot because it is already registered and I don't have its privkey.pem, I had to reset my VPS.]

12

When was this attempt made? DNS seems to be in order (dnsviz, check-host), there is an A record for that subdomain.

Could be a fluke of some kind, try requesting again now or a bit later.

2 Likes
13

Thank you very much brother! I was facing a lot of problems because of this error.

2 Likes