"is not reachable" error on a few domains (but not all) in DirectAdmin

Hello, good day!

I’ve a problem with a few domains and I’m searching for a solution for days now. Hope you can help me out.

I’ve a CentOS 7 VPS with DirectAdmin. Everything is latest version.
I enabled SNI and the LetsEncrypt plugin.

It’s working fine except for 3 domains…
They keep giving me an error:

Cannot Execute Your Request

Details

Getting challenge for domain.com from acme-server…
Error: http://domain.com/.well-known/acme-challenge/letsencrypt_1498124509 is not reachable. Aborting the script.
dig output for domain.com:
x.x.x.x
Please make sure /.well-known alias is setup in WWW server.

The .well-known alias has been setup and is working. Like 15 other domains on this machine have certificates and didn’t give any errors. Also the test file is working fine, even on the three domains which are giving this error:
http://domain.com/.well-known/acme-challenge/test.txt it gives a reply as you can see.

I noticed one weird thing. If I use CLI to CURL the test file it gives a 404 error.

/usr/bin/curl -I -L -k -X GET http://www.domain.com/.well-known/acme-challenge/test.txt

HTTP/1.1 200 OK
Date: Thu, 22 Jun 2017 09:38:54 GMT
Server: Apache/2
Last-Modified: Thu, 22 Jun 2017 08:34:59 GMT
ETag: "5-552885c342c41"
Accept-Ranges: bytes
Content-Length: 5
Vary: User-Agent
Content-Type: text/plain

Can you tell me what I can try or do to solve these issues?
Appreciate the help!

Kind regards,

Roy

The test.txt reply may be a false positive; because it isn’t guaranteed to be served from the domain you are connecting to.
Try putting an individualized test.txt file.
Either use a specific file name or specific content per vhost.
“test” is non-specific.
Show exactly which file/folder is being accessed by:
http://bekendvandetv.com/.well-known/acme-challenge/test.txt
http://www.bekendvandetv.com/.well-known/acme-challenge/test.txt

Thanks, I’m going to try that.

But what could be wrong with these 3 domains?
Why would I get the not reachable error?

Not reachable is that it can’t find the content it’s looking for - not necessarily that the entire site is unreachable.

That answer may be found when comparing the various vhost files.

just compared the vhost files of a working domain with a non-working domain, they are identical, there are no differences.

maybe a second set of eyes can find something overlooked…
can you post the configs?

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