I use ispconfig 3.1-dev with letsencrypt support. It works on all domains well, except on one and I do not understand where the problem occurs. The name server entries pointing to the specific ip for the domain. There should not be a problem at all. The problems occurs with the ip for the domain as well as when I chance the ip to the domain of the server itself. It is always the same problem. And it only ONLY comes with this one domain.
Domain: kulturmaschinen.com
To fix these errors, please make sure that your domain name was entered correctly and the DNS A record(s) for that domain contain(s) the right IP address. 2016-09-15 18:38:06,442:INFO:certbot.auth_handler:Cleaning up challenges 2016-09-15 18:38:06,442:DEBUG:certbot.plugins.webroot:Removing /usr/local/ispconfig/interface/acme/.well-known/acme-challenge/Lzd56GGU0ZOqn9IgsRrrQYmClAC2PNwY2wmsT8Vt7PQ 2016-09-15 18:38:06,443:DEBUG:certbot.plugins.webroot:Removing /usr/local/ispconfig/interface/acme/.well-known/acme-challenge/d6y7-HXcGo–ACz2Q7iNwi58TfB_umNwGy_2IhSq1mA 2016-09-15 18:38:06,443:DEBUG:certbot.plugins.webroot:All challenges cleaned up, removing /usr/local/ispconfig/interface/acme/.well-known/acme-challenge 2016-09-15 18:38:06,444:DEBUG:certbot.main:Exiting abnormally: Traceback (most recent call last):
_ File “/root/.local/share/letsencrypt/bin/letsencrypt”, line 11, in _
_ sys.exit(main())_
_ File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/main.py”, line 744, in main_
_ return config.func(config, plugins)_
_ File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/main.py”, line 555, in obtain_cert_
_ , action = auth_from_domains(le_client, config, domains, lineage)
_ File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/main.py”, line 94, in auth_from_domains
_ lineage = le_client.obtain_and_enroll_certificate(domains)
_ File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/client.py”, line 276, in obtain_and_enroll_certificate_
_ certr, chain, key, _ = self.obtain_certificate(domains)_
_ File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/client.py”, line 247, in obtain_certificate_
_ self.config.allow_subset_of_names)_
_ File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/auth_handler.py”, line 74, in get_authorizations_
_ self.respond(resp, best_effort)
_ File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/auth_handler.py”, line 131, in respond
_ self.poll_challenges(chall_update, best_effort)
_ File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/auth_handler.py”, line 195, in poll_challenges
_ raise errors.FailedChallenges(all_failed_achalls)_ FailedChallenges: Failed authorization procedure. www.kulturmaschinen.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.kulturmaschinen.com/.well-known/acme-chall$
_ “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>_ <ht", kulturmaschinen.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://kulturmaschinen.com/.well-known/acme-challenge/Lzd56GGU0ZOqn9IgsRrrQYmClAC2PNwY2wmsT8Vt7PQ: "<$
_ “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>_
I really have not the tiniest idea, what might blocking the generation of the certs. If it is not something on the servers of letsencrypt, than there might be a problem with ispconfig and I should ask there …
No, I can’t. But then ispconfig seems to locate acme in /usr/local/ispconfig/acme/ … And there is no link from the vhost to the folder. Maybe it is generated only while processing. After I cannot not reach the folder with those domains which already has got certificates (so it worked there), it might be something like that.
I’m guessing ispconfig has done something with redirects / .htaccess if you can’t reach any files in those folders. I’d agree with your view above - time to ask on the ispconfig forums.
The log doesn’t seem to have records related to the attempt to retrieve verification file. This is what needs to be found basically, because by the look of it you were getting a HTML page instead of that file. I see that logs mention Phusion Passenger, so you might try checking its logs too.