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:
roger.kiwi.nz
I ran this command:
certbot certonly --force-renew
It produced this output:
http-01 challenge for roger.kiwi.nz
Cleaning up challenges
Some challenges have failed.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
My web server is (include version):
nginx
The operating system my web server runs on is (include version):
ubuntu 20.04.5 LTS
My hosting provider, if applicable, is:
digitalocean
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):
0.40.0
Please do not use options of which you don't understand their purpose. E.g., the --force-renewal does NOT magically let you get a certificate without any validation. And as such it wouldn't help you with your issue what so ever, but, if used improperly, could lead to bad things such as rate limits.
By the way, renewal is usually done by running sudo certbot renew.
Also:
This version of Certbot is quite old. It's recommended to use snap to install Certbot and keep it (automatically) up to date. See https://certbot.eff.org/ for more info.
Now, to your issue: could you please post the contents of the renewal configuration file? It probably is /etc/letsencrypt/renewal/roger.kiwi.nz.conf.
Also, please post the output of the command sudo nginx -T.
I had also tried certbot renew, but it failed with the same output as the command I shouldn't have run! (thanks for the feedback). This server had been neglected for some time, I will keep a better eye on it now
Ah, perhaps there was something in your nginx configuration confusing for the ancient Certbot, but easy to manage in the most recent one
That's probably because "deep down" they were doing the same thing. I didn't know you already tried certbot renew though, so I thought I'd just mention certbot renew.