The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A

[cesare]

My domain is:
lumen.gwmholding.com

I ran this command:
certbot --apache --text

It produced this output:
Failed authorization procedure. lumen.gmwholding.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for lumen.gmwholding.com

IMPORTANT NOTES:

• The following errors were reported by the server:

  Domain: lumen.gmwholding.com
  Type: connection
  Detail: DNS problem: NXDOMAIN looking up A for lumen.gmwholding.com

  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 httpd 2.4.6

The operating system my web server runs on is (include version):
CentOs 7 64Bit

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

Port 443 and 80 is reachable on server. There is no record TXT associated, I have no clue why it is doing this.
Record A is correctly inserted.

[sahsanu]

Hi @cesare,

@cesare

I have no clue why it is doing this.

Record A is correctly inserted.

gmwholding.com is not registered so it is impossible you own it. Maybe your domain is gwmholding.com (switched m and w letters) ?.

Cheers,
sahsanu

[cesare]

a stupid typo message, of course it’s gwm, thanks a lot!

[cesare]

I correct the type, but still I have this issue:
Failed authorization procedure. lumen.gwmholding.com (tls-sni-01): urn:acme:error:malformed :: The request message was malformed :: Server only speaks HTTP, not TLS

IMPORTANT NOTES:

• The following errors were reported by the server:

  Domain: lumen.gwmholding.com
  Type: malformed
  Detail: Server only speaks HTTP, not TLS

  To fix these errors, please make sure that you did not provide any
  invalid information to the client, and try running Certbot again.

And I don’t get what’s wrong, here my virtual host conf:
<Directory “/var/www”>
AllowOverride None
# Allow open access:
Require all granted

Further relax access to the default document root:

ServerName lumen.gwmholding.com DocumentRoot /var/www/html Options Indexes FollowSymLinks AllowOverride None Require all granted

RequestHeader set X-Forwarded-Proto https
RequestHeader set X-Forwarded-Port 443
RewriteEngine on
RewriteCond %{SERVER_NAME} =lumen.gwmholding.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

I have enalbed also the ssl.conf file, but I did not change it.

[bytecamp]

@cesare

Server only speaks HTTP, not TLS

Your Webserver (Apache) is listening on port 443, but does not offer SSL/TLS there. You can test that with the openssl tools:

$ openssl s_client -connect lumen.gwmholding.com:443
CONNECTED(00000003)
140660299179680:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:795:

no peer certificate available

You have to enable TLS via SSLEngine On in the virtualhost which serves port 443, or use http-01 instead of tls-sni-01 to authorize for your domain.

[cesare]

thanks! I create a self signed certificate, so that HTTPS works, and then lunching the command everything went fine!