Certificate renewal errors

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: omitttradeschool.com
XAMPP version: 7.4.12
Ubuntu version: 20.04.2 LTS

I ran this command: sudo certbot certonly --cert-name omitttradeschool.com --webroot -w /opt/lampp/htdocs/omitttrade -d "omitttradeschool.com, www.omitttradeschool.com" --deploy-hook "sudo /opt/lampp/lampp reloadapache"

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Cert is due for renewal, auto-renewing...
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for omitttradeschool.com
http-01 challenge for www.omitttradeschool.com
Using the webroot path /opt/lampp/htdocs/omitttrade for all unmatched domains.
Waiting for verification...
Challenge failed for domain omitttradeschool.com
Challenge failed for domain www.omitttradeschool.com
http-01 challenge for omitttradeschool.com
http-01 challenge for www.omitttradeschool.com
Cleaning up challenges
Some challenges have failed.


My web server is (include version):

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

My hosting provider, if applicable, is: Apache 2.4.46

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 0.40.0

1 Like

The error message explains what happens perfectly. It even includes a hint for you to check. I can't explain more than that? Did you even look at the error message at all?

1 Like

There's a mistake that may seem obvious to someone with experience. With some guidance, I'm confident I can fix the issue.

1 Like

I'm not even seeing an http to https redirect for http://omitttradeschool.com/.well-known/acme-challenge/test, which is perfectly fine, but unexpected given your original post. Did something change since you posted, @coldje?

I am seeing the following redirects that indicate http to https redirection has generally been disabled:

302 Found
200 OK

302 Found
200 OK


Yes, that was a temporary test. The redirect is back.

1 Like

Things don't appear to have changed.

I uncommented and have been playing with different examples of redirection found online. This is what redirect-checker.org provides.
Frustrating because I changed the redirection in the httpd-ssl.conf file (where my vhosts are defined) to:
<VirtualHost *:80>
Redirect 301 / https://omittradeschool.com

and yet I'm still getting the 302 redirect issue.

1 Like

Did you reload apache after the changes?

sudo /opt/lampp/lampp reloadapache

Thank you very much. It is fixed now. I swear I did put the / after the domain name in the redirect previously and reloaded apache. But I read and read, and looked and looked and eventually did it again. This time the cert renewed fine. I don't know.

1 Like

Ghosts in the machine? :man_shrugging:

I'm just glad it's working. :partying_face:

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