Failed to renew certificate www.bikecheckin.tw with error: Some challenges have failed

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. https://crt.sh/?q=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:bikecheckin.tw, edisk.com.tw

I ran this command:certbot renew

It produced this output: Renewing an existing certificate for www.bikecheckin.tw

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: www.bikecheckin.tw
Type: connection
Detail: 60.250.84.80: Fetching https://www.bikecheckin.tw.well-known/acme-challenge/JGn_kYIVik5Nx8CxluIPywJ4hAdsrCc5rjee6rIbgAI: Invalid host in redirect target "www.bikecheckin.tw.well-known". Check webserver config for missing '/' in redirect target.

Renewing an existing certificate for www.edisk.com.tw

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: www.edisk.com.tw
Type: connection
Detail: 60.250.84.80: Fetching https://www.edisk.com.tw.well-known/acme-challenge/mizzMUlN7620w-q3fXaYj6MbRM3ekCVH2gVsFWb2Kxk: Invalid host in redirect target "www.edisk.com.tw.well-known". Check webserver config for missing '/' in redirect target.

My web server is (include version): Apache/2.4.51 (Fedora)

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

My hosting provider, if applicable, is: I own this server.

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.19.0

I believe the error message is pretty self-explanatory? Can you perhaps explain what isn't clear about it?

5 Likes

I don't know what the "https://www.bikecheckin.tw.well-known/" came from, especially the ending .well-known

From an incorrect HTTP to HTTPS redirect. Please make sure it has a / at the end of the destination in the redirect, as suggested by the error message.

4 Likes

I did change the vhost.conf as:
<VirtualHost *:80>
DocumentRoot /var/www/html
ServerName www.edisk.com.tw
ServerAlias www.edisk.com.tw

Redirect permanent / https://www.edisk.com.tw/

<VirtualHost *:80>
DocumentRoot /var/www/bike
ServerName www.bikecheckin.tw
ServerAlias www.bikecheckin.tw

Redirect permanent / https://www.bikecheckin.tw/

=================================
And got the error message as:

Renewing an existing certificate for www.bikecheckin.tw
Failed to renew certificate www.bikecheckin.tw with error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type : : Error creating new order :: too many failed authorizations recently: see Failed Validation Limit - Let's Encrypt


Processing /etc/letsencrypt/renewal/www.edisk.com.tw.conf


Renewing an existing certificate for www.edisk.com.tw
Failed to renew certificate www.edisk.com.tw with error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see Failed Validation Limit - Let's Encrypt

So, it will be ok if I wait for one hour?

1 Like

You should test using the testing/staging environment [not production LE systems].

3 Likes

Thanks, but I just don't understand about the " testing/staging environment", shall I own another domain for testing?

Or that can be tested to another virtual host in the same domain?
I am old in age but new in doing this.

2 Likes

Staging Environment - Let's Encrypt (letsencrypt.org)

3 Likes

Wow, thanks!

2 Likes

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