Cannot renew 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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: sudo certbot-auto certonly -d -d

It produced this output:
owner1@Ubuntu11:/etc/letsencrypt$ sudo certbot-auto certonly -d type1diabetics. org -d
Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?

1: Apache Web Server plugin (apache)
2: Spin up a temporary webserver (standalone)
3: Place files in webroot directory (webroot)

Select the appropriate number [1-3] then [enter] (press ‘c’ to cancel): 1
Plugins selected: Authenticator apache, Installer None
Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for
http-01 challenge for
Waiting for verification…
Challenge failed for domain
Challenge failed for domain
http-01 challenge for
http-01 challenge for
Cleaning up challenges
Some challenges have failed.


My web server is (include version): Apache/2.4.29 (Ubuntu) Server

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

My hosting provider, if applicable, is: home network

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):certbot 1.5.0

Did but cannot find error

What next?

1 Like

Your Apache configuration is seriously misconfigured. See the error message for yourself:

It even states the reason of the error message.

Also, your HTTPS sites has a redirect loop.

That's because that site-checker has way too much information which often tends to be very cryptic to be actually useful IMHO. Not your fault.

1 Like

Hi @tombokman

read your output.

sends content, so your port 80 is a https port, not a http port.

If it's a home server, may be you have a wrong port forwarding

port 80 extern -> port 443 intern.

And you see:

works too, so you have a working port 443.

Your check is old, may be you have now created additional errors.

1 Like

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