Http-01 challenges failed for domains

The Let'sencrypt auto renewal worked fine for eight month.
Please help me!

My domain is:
nc.lan.karo5.de
talk.lan.karo5.de

I ran this command:
certbot renew --dry-run

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


Processing /etc/letsencrypt/renewal/nc.lan.karo5.de.conf


Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator standalone, Installer None
Running pre-hook command: systemctl stop apache2.service
Simulating renewal of an existing certificate for nc.lan.karo5.de
Performing the following challenges:
http-01 challenge for nc.lan.karo5.de
Waiting for verification...
Challenge failed for domain nc.lan.karo5.de
http-01 challenge for nc.lan.karo5.de
Cleaning up challenges
Failed to renew certificate nc.lan.karo5.de with error: Some challenges have failed.


Processing /etc/letsencrypt/renewal/talk.lan.karo5.de.conf


Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator standalone, Installer None
Pre-hook command already run, skipping: systemctl stop apache2.service
Simulating renewal of an existing certificate for talk.lan.karo5.de
Performing the following challenges:
http-01 challenge for talk.lan.karo5.de
Waiting for verification...
Challenge failed for domain talk.lan.karo5.de
http-01 challenge for talk.lan.karo5.de
Cleaning up challenges
Failed to renew certificate talk.lan.karo5.de with error: Some challenges have failed.


All simulated renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/nc.lan.karo5.de/fullchain.pem (failure)
/etc/letsencrypt/live/talk.lan.karo5.de/fullchain.pem (failure)


Running post-hook command: systemctl start apache2.service
2 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: nc.lan.karo5.de
    Type: connection
    Detail: Fetching
    http://nc.lan.karo5.de/.well-known/acme-challenge/O0SpaUYmA181kzs_PGOulVMv86yXNdHh79IgxBBu2Sg:
    Error getting validation data

    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.

  • The following errors were reported by the server:

    Domain: talk.lan.karo5.de
    Type: connection
    Detail: Fetching
    http://talk.lan.karo5.de/.well-known/acme-challenge/Cp-2pSAFzeG0QkidS24h_Ll7B1uYtsuMDmecIVRIDUI:
    Error getting validation data

    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):
Server version: Apache/2.4.41 (Ubuntu)
Server built: 2020-08-12T19:46:17

The operating system my web server runs on is (include version):
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal

My hosting provider, if applicable, is:
selfhosted NEXTCLOUD VM from Hansson IT
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.12.0

Port 80/443 are open
Both domains have a valid A record in the DNS zonefile of the service provider that hosts my domain karo5.de. It points to my fixed ip.

However, it's impossible to connect to your host:

osiris@erazer ~ $ curl -LIv http://nc.lan.karo5.de/.well-known/acme-challenge/O0SpaUYmA181kzs_PGOulVMv86yXNdHh79IgxBBu2Sg
*   Trying 85.183.39.11:80...
* connect to 85.183.39.11 port 80 failed: No route to host
* Failed to connect to nc.lan.karo5.de port 80: No route to host
* Closing connection 0
curl: (7) Failed to connect to nc.lan.karo5.de port 80: No route to host
osiris@erazer ~ $ curl -LIv http://talk.lan.karo5.de/.well-known/acme-challenge/Cp-2pSAFzeG0QkidS24h_Ll7B1uYtsuMDmecIVRIDUI
*   Trying 85.183.39.11:80...
* connect to 85.183.39.11 port 80 failed: No route to host
* Failed to connect to talk.lan.karo5.de port 80: No route to host
* Closing connection 0
curl: (7) Failed to connect to talk.lan.karo5.de port 80: No route to host
osiris@erazer ~ $ 

Your own host is sending back "communication administratively prohibited" ICMP packets:

osiris@erazer ~ $ sudo traceroute -T -p 80 85.183.39.11
traceroute to 85.183.39.11 (85.183.39.11), 30 hops max, 60 byte packets
(...)
 5  asd-s8-rou-1041.NL.as286.net (134.222.94.216)  24.467 ms  24.444 ms  25.426 ms
 6  ae16-100-cr6-ams1.ipv4.gtt.net (194.122.122.102)  26.761 ms ae11-100-cr5-ams1.ipv4.gtt.net (194.122.122.98)  11.981 ms  14.645 ms
 7  ae11.cr6-ams1.ip4.gtt.net (213.200.117.178)  12.388 ms * *
 8  * * *
 9  176.52.248.240 (176.52.248.240)  27.911 ms 176.52.248.140 (176.52.248.140)  27.911 ms *
10  176.52.252.29 (176.52.252.29)  29.127 ms  29.104 ms  32.439 ms
11  176.52.252.33 (176.52.252.33)  32.437 ms bundle-ether32.0003.dbrx.02.fra.de.net.telefonica.de (62.53.8.186)  42.851 ms 176.52.252.33 (176.52.252.33)  32.419 ms
12  ae3-0.0001.corx.01.off.de.net.telefonica.de (62.53.28.154)  42.810 ms ae3-0.0002.corx.02.fra.de.net.telefonica.de (62.53.0.208)  30.973 ms ae2-0.0002.corx.02.fra.de.net.telefonica.de (62.53.0.198)  32.305 ms
13  ae10-0.0002.corx.01.ham.de.net.telefonica.de (62.53.0.34)  32.233 ms  33.475 ms ae101-0.0002.corx.02.fra.de.net.telefonica.de (62.53.14.182)  35.844 ms
14  ae10-0.0001.corx.06.ham.de.net.telefonica.de (62.53.0.48)  46.539 ms bundle-ether2.0006.dbrx.01.ham.de.net.telefonica.de (62.53.14.233)  36.431 ms bundle-ether1.0006.dbrx.01.ham.de.net.telefonica.de (62.53.14.27)  39.988 ms
15  eth-trunk2.0003.acln.01.ham.de.net.telefonica.de (62.53.12.23)  38.842 ms  35.827 ms bundle-ether2.0006.dbrx.01.ham.de.net.telefonica.de (62.53.14.233)  33.077 ms
16  85.183.39.11 (85.183.39.11)  40.643 ms !X  65.546 ms !X  64.189 ms !X
osiris@erazer ~ $ 

Perhaps a firewall blocking stuff somewhere?

Also, is there a specific reason for using the standalone plugin? Why not use the webroot plugin?

2 Likes

That's it!

Congratulations, all renewals succeeded:

  • /etc/letsencrypt/live/nc.lan.karo5.de/fullchain.pem (success)*
  • /etc/letsencrypt/live/talk.lan.karo5.de/fullchain.pem (success)*
    I lost the router portforwarding of 80/443 after a router firmware update. Did not notice, because I use my Nextcloud only via LAN and VPN.

Thank you @Osiris!

3 Likes

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