The server could not connect to the client to verify the domain

Help
1

I am getting this error when trying to generate a certificate using default process.

Can anyone please help me in creating that certificate.

2

Difficult without a bit more information

The problem is, as stated in your title. The server couldn’t connect connect and verify the domain name.

Is the domain reachable by the general public ? can you give us the domain name ? can you give us the log or any more information from the script ?

3

I am getting this below error

Failed authorization procedure. webtechnologycodes.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to host for DVSNI challenge, www.webtechnologycodes.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to host for DVSNI challenge

IMPORTANT NOTES:

1 Like
4

It's on CloudFlare, so DVSNI challenge won't work.
See

5

Just a min, let me change my dns

6

I have changed my domain to my ip. Now it is not on cloudflare.

7

Now again when I tried I am getting the same error.

Failed authorization procedure. webtechnologycodes.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to host for DVSNI challenge, www.webtechnologycodes.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to host for DVSNI challenge

IMPORTANT NOTES:

8

Now you should wait until DNS cache expires on the LE side. It still connects to CloudFlare.

1 Like
9

OK, Thanks. I will let you know when cache are expires.

10

You can search the forums for other solutions to cloudflare which may help.

11

Try https://developers.google.com/speed/public-dns/cache LE use google dns :smile:

2 Likes
12

[quote=“BregnedalSystems, post:11, topic:7365”]
Try https://developers.google.com/speed/public-dns/cache LE use google dns :smile:
[/quote] you sure… i thought LE used Akamai’s DNS ?

13

I did every thing but always getting the same result. cloudflare is disabled.

Failed authorization procedure. webtechnologycodes.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to host for DVSNI challenge, www.webtechnologycodes.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to host for DVSNI challenge

IMPORTANT NOTES:

14

Which command did you run? You wrote “trying to generate a certificate using default process” — but what’s that?
Is it e.g. ./letsencrypt-auto certonly --test-cert --standalone
or is it ./letsencrypt-auto --apache ...
or … not nginx?

I’m wondering if when the lets-encrypt server attempted to contact your server at www.webtechnologycodes.com, then your server wasn’t up and running, for some reason. Perhaps you had a firewall that blocked incoming traffic? Or perhaps there’s some other earlier letsencrypt error message that tells you that letsencrypt failed to (re)start the letsencrypt stuff on your own server? So there was nothing listening on port 443? port 80?

Apparently your server is up-and-running right now anyway on port 80.

(I’m a letsencrypt newbie; all this might be wrong)

15

I had this same error, and fixed it by replacing the top line in my apache config from

<VirtualHost mydomain.com>
to
<VirtualHost mydomain.com:80>

16

I’m having this issue as well, the solution posted by @px43 fixed the problem for my primary domain however this doesn’t seem to work for any subdomains I have setup.

17

Having the same error, but none of the aboves work:

The fellowing question:

To repeat the certification with ./letsencrypt-auto --apache, can it be helpful to empty the directory /etc/letsencrypt/ ?

18

can it be helpful to empty the directory /etc/letsencrypt/ ?

Generally, No, that nearly always messes things up - and that also contains your existing certs, keys etc.

19

I tried a bunch of stuff before I realised that I had to port forward the port 443 to my server :smiley: Now it works like a charm!

1 Like
20

I had a similar issue. In my case my domain *.mydomain.com was redirecting to https. I had to disable the SSL site and disable the http --> https redirect in my virtual host that served http. Then my domain verification worked and letsencrypt automatically enabled the SSL for my site when the cert was issued.