# Http-01 challenge fails **URL:** \ **Category:** Help\ **Created:** [September 13, 2019, 7:10am UTC](https://community.letsencrypt.org/t/http-01-challenge-fails/101927 "2019-09-13T07:10:33Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![AnttiJ](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@AnttiJ](https://community.letsencrypt.org/u/AnttiJ)\ **Post date:** [September 13, 2019, 7:10am UTC](https://community.letsencrypt.org/t/http-01-challenge-fails/101927/1 "2019-09-13T07:10:34Z")
Hello, I have problem to renew certs with one server. This current cert is now renewd by using different host. I change dns and moved files to and back that server. On "spare" server I can do "certbot-auto renew --dry-run" and it works ok. On problematic server "certbot-auto renew --dry-run" still fails. I do not have idea, what's wrong. My domain is: [lintulehti.testi.birdlife.fi](http://lintulehti.testi.birdlife.fi) I ran this command: ./certbot-auto renew --dry-run It produced this output: > [root@mongodb letsencrypt]# ./certbot-auto renew --dry-run > Saving debug log to /var/log/letsencrypt/letsencrypt.log > > * * * > > Processing /etc/letsencrypt/renewal/lintulehti.testi.birdlife.fi.conf > > * * * > > Cert not due for renewal, but simulating renewal for dry run > Plugins selected: Authenticator standalone, Installer None > Renewing an existing certificate > Performing the following challenges: > http-01 challenge for [lintulehti.testi.birdlife.fi](http://lintulehti.testi.birdlife.fi) > Waiting for verification... > Challenge failed for domain [lintulehti.testi.birdlife.fi](http://lintulehti.testi.birdlife.fi) > http-01 challenge for [lintulehti.testi.birdlife.fi](http://lintulehti.testi.birdlife.fi) > Cleaning up challenges > Attempting to renew cert ([lintulehti.testi.birdlife.fi](http://lintulehti.testi.birdlife.fi)) from /etc/letsencrypt/renewal/lintulehti.testi.birdlife.fi.conf produced an unexpected error: Some challenges have failed.. Skipping. > > * * * > > All renewal attempts failed. The following certs could not be renewed: > /etc/letsencrypt/live/lintulehti.testi.birdlife.fi/fullchain.pem (failure) > \*\* DRY RUN: simulating 'certbot renew' close to cert expiry > \*\* (The test certificates above have not been saved.) > > * * * > > 1 renew failure(s), 0 parse failure(s) > > IMPORTANT NOTES: > > - The following errors were reported by the server: The operating system my web server runs on is (include version): CentOS Linux release 7.6.1810 (Core I can login to a root shell on my machine (yes or no, or I don't know): yes The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): certbot 0.38.0 ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [September 13, 2019, 7:37am UTC](https://community.letsencrypt.org/t/http-01-challenge-fails/101927/2 "2019-09-13T07:37:37Z")
Hi @AnttiJ > [@AnttiJ](#): > > Plugins selected: Authenticator standalone, Installer None standalone is hard to debug, that starts an own webserver. Your domain is invisible - [https://check-your-website.server-daten.de/?q=lintulehti.testi.birdlife.fi](https://check-your-website.server-daten.de/?q=lintulehti.testi.birdlife.fi) | Domainname | Http-Status | redirect | Sec. | G | | --- | --- | --- | --- | --- | | • [http://lintulehti.testi.birdlife.fi/](http://lintulehti.testi.birdlife.fi/) | | | | | | 195.60.204.41 | -14 | | 10.044 | T | | Timeout - The operation has timed out | | | | | | | | | | | | • [https://lintulehti.testi.birdlife.fi/](https://lintulehti.testi.birdlife.fi/) | | | | | | 195.60.204.41 | -14 | | 10.030 | T | | Timeout - The operation has timed out | | | | | | | | | | | | • [http://lintulehti.testi.birdlife.fi/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://lintulehti.testi.birdlife.fi/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | | | 195.60.204.41 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0 | -14 | | 10.030 | T | | Timeout - The operation has timed out | | | | | But if there is no running webserver, that's normal. Blocking firewall? There is a new certificate: | Issuer | not before | not after | Domain names | LE-Duplicate | next LE | | --- | --- | --- | --- | --- | --- | | Let's Encrypt Authority X3 | 2019-09-11 | 2019-12-10 | [lintulehti.testi.birdlife.fi](http://lintulehti.testi.birdlife.fi) - 1 entries | duplicate nr. 1 | | | Let's Encrypt Authority X3 | 2019-06-19 | 2019-09-17 | [lintulehti.testi.birdlife.fi](http://lintulehti.testi.birdlife.fi) - 1 entries | | | What did you change after creating that certificate? ---
**Author:** ![AnttiJ](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@AnttiJ](https://community.letsencrypt.org/u/AnttiJ)\ **Post date:** [September 13, 2019, 8:16am UTC](https://community.letsencrypt.org/t/http-01-challenge-fails/101927/3 "2019-09-13T08:16:36Z")
Yeps there is no webserver and it's standalone cert. On port 8080 there is service, listening returns on blue screen, but cert seems to be ok. [https://lintulehti.testi.birdlife.fi:8080/](https://lintulehti.testi.birdlife.fi:8080/) > What did you change after creating that certificate? I did copy accounts, archieve and renewal from "spare"-server to /etc/letsencrypt-dir and manually create symbolic links to live/lintulehti.testi.birdlife.fi/ -dir And also change dns to that host ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [September 13, 2019, 8:54am UTC](https://community.letsencrypt.org/t/http-01-challenge-fails/101927/4 "2019-09-13T08:54:08Z")
The test of “check-your-website” has a port check, there is port 8080 (Speedport) checked. But there was no answer, now port 8080 is open. Perhaps you have blocked port 80 too. ---
**Author:** ![AnttiJ](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@AnttiJ](https://community.letsencrypt.org/u/AnttiJ)\ **Post date:** [September 13, 2019, 9:00am UTC](https://community.letsencrypt.org/t/http-01-challenge-fails/101927/5 "2019-09-13T09:00:22Z")
No, ports 80 & 443 are open, there is no listener is those. I tested them with small node.js prog. There where no listener on port 8080 before I started it. No changes on fw. ---
**Author:** ![AnttiJ](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@AnttiJ](https://community.letsencrypt.org/u/AnttiJ)\ **Post date:** [September 16, 2019, 7:36am UTC](https://community.letsencrypt.org/t/http-01-challenge-fails/101927/6 "2019-09-16T07:36:13Z")
Hello, I moved everything from this host to another, services and certs. Renewing certificates there is no problem and all works now ok. Original reason cannot been solved. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [October 16, 2019, 7:43am UTC](https://community.letsencrypt.org/t/http-01-challenge-fails/101927/7 "2019-10-16T07:43:18Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.