Renew certificate throws "Some challenges have failed."

I run: certbot --apache -d

It shows:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for
Waiting for verification…
Challenge failed for domain
http-01 challenge for
Cleaning up challenges
Some challenges have failed.


  • The following errors were reported by the server:

    Type: connection
    Detail: Fetching
    Timeout during connect (likely firewall problem)

    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. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

My web server is (include version):
apache 2.4

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

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

When try access via wget:


I am able to get the testfile. So I think that there are no FW problems.

Are there any hints how to renew the certificate?

Hi @hjfh

please read your older topic:

Checking your domain now you have a Grade A - - so /.well-known/acme-challenge works.

But if Letsencrypt can't check your validation file, your regional blocking may be active again.

Indeed, I have some filtered regions …


Sorry for disturbing …

I were very happy if LE could provide the IPs they use …

Thank you very much and have a great sunday.

That will not happen. Read

New Features

In 2018 we introduced several new features, including ACMEv2 support and wildcard certificates. We’ve got some exciting features planned for 2019.

The feature we’re most excited about is multi-perspective validation. Currently, when a subscriber requests a certificate, we validate domain control from a single network perspective. This is standard practice for CAs. If an attacker along the network path for the validation check can interfere with traffic they can potentially cause certificates to be issued that should not be issued. We’re most concerned about this happening via BGP hijacking, and since BGP is not going to be secured any time soon, we needed to find another mitigation. The solution we intend to deploy in 2019 is multi-perspective validation, in which we will check from multiple network perspectives (distinct Autonomous Systems). This means that potential BGP hijackers would need to hijack multiple routes at the same time in order to pull off a successful attack, which is significantly more difficult than hijacking a single route.

So your domain may be checked via different ip addresses - worldwide.

PS: A regional blocking is (my personal position) always wrong.

1 Like

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