Need help with auto renewing my certificate

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: https://n00bserver.duckdns.org/

I ran this command: sudo certbot renew

It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/n00bserver.duckdns.org.conf


Renewing an existing certificate for n00bserver.duckdns.org

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: n00bserver.duckdns.org
Type: connection
Detail: 87.195.250.114: Fetching http://n00bserver.duckdns.org/.well-known/acme-challenge/bcE6vXVeDNPb6lGOERkjub1r_HJDBENuEY6I-PCKywE: Error getting validation data

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.

Failed to renew certificate n00bserver.duckdns.org with error: Some challenges have failed.


All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/n00bserver.duckdns.org/fullchain.pem (failure)


1 renew failure(s), 0 parse failure(s)

My web server is (include version): Jellyfin 10.10.4

The operating system my web server runs on is (include version): Ubuntu 24.04.1 LTS

My hosting provider, if applicable, is: DuckDNS

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

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

A Let's Debug test shows an HTTP request (port 80) failing with "No Route to Host". Yet, HTTPS requests (port 443) work fine.

This is probably a port-forwarding or NAT problem in your router or local network. Make sure HTTP requests on port 80 reach the same machine you run Certbot on.

4 Likes

Yup I opened port 80 and I can renew it again, thanks!

2 Likes

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