My domain is: BobbyCycles.in
My web server is (include version): nginx version: nginx/1.18.0 (Ubuntu)
My hosting provider, if applicable, is: Hetzner
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 : certbot 1.21.0
I've successfully produced certificates for BobbyCycles.in (I've checked by certbot certificates also.
Pls note that I've put this domain name to forward to another domain name.
And also, that it (certificates for this domain and domain forwarding) was working ok 2-3 days ago.
Yet, when I type BobbyCycles.in in any browser, it either gives 'Problem Loading Page' error: The connection has timed out or forwards to some wrong domain (BobbyCycles.com). Though earlier this forwarding was set. But no longer. At this day/moment, my conf file is set to forward https://BobbyCycles.into forward to BathindaHelper.com.
With regard to your seemingly duplicate certificate: if both the renewal configuration files are equal in contents, you should be fine with deleting just one of the two configuration files, e.g. bobbycycles.in-1.conf
With regard to your initial question: works for me now, the only thing I noticed currently is that there's no HTTP to HTTPS redirect for the .com site. Couldn't check the rest from where I am now.
If I'd delete one, both would go. And even though I could delete this one and create new one, but I'm afraid there would be remnants of the old certs. Particularly because I did tinker with cert/renewal files manually. So if there is some command which could delete all related cert files without leaving any remnants, then it could be great. And then I could create/go for creating new one.
One one thing still would bother me, what if it said that I've already generated 5 times (though I remember to have generated only 3, or at the most 4, times)? So, is there another way with which I could backu the these (corrupt or non-standard) certs first?
Certbot "knows" about its certs due to the renewal configuration files in /etc/letsencrypt/renewal/ and those renewal configuration files contain links to the files in /etc/letsencrypt/live/.
With my post aboven I only refered to the configuration files in /renewal/, NOT the files in /live/ or /archive/.
If the problem is with the webserver, there is absolutely NO NEED to keep forcibly renewing perfectly fine certificates. If you don't force certificate renewals, there's no problem with the rate limit you're mentioning.
I got it. But I found that while Godaddy is allowing me to create/edit 'a' records for my domain BathindaHelper.com (and others), it is not allowing (the option is grayed out) me to edit 'a' records of BobbyCycles.in
Seems that problem has been resolved. (by deleting the duplicate conf file in /etc/letsencrypt/renew and correcting the domains 'A' records in GoDaddy panel (after removing domain forwarding set inadvertently).