# The server could not connect to the client to verify the domain **URL:** \ **Category:** Help\ **Created:** [December 19, 2015, 6:16pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365 "2015-12-19T18:16:32Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Vinaysikarwar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/vinaysikarwar/32/3456_2.png) [@Vinaysikarwar](https://community.letsencrypt.org/u/Vinaysikarwar)\ **Post date:** [December 19, 2015, 6:16pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/1 "2015-12-19T18:16:32Z")
I am getting this error when trying to generate a certificate using default process. Can anyone please help me in creating that certificate. ---
**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\ **Post date:** [December 19, 2015, 6:27pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/2 "2015-12-19T18:27:15Z")
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 ? ---
**Author:** ![Vinaysikarwar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/vinaysikarwar/32/3456_2.png) [@Vinaysikarwar](https://community.letsencrypt.org/u/Vinaysikarwar)\ **Post date:** [December 20, 2015, 4:07am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/3 "2015-12-20T04:07:43Z")
I am getting this below error Failed authorization procedure. [webtechnologycodes.com](http://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](http://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: - The following ‘urn:acme:error:connection’ errors were reported by the server: ---
**Author:** ![selecadm](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/selecadm/32/5114_2.png) [@selecadm](https://community.letsencrypt.org/u/selecadm)\ **Post date:** [December 20, 2015, 4:10am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/4 "2015-12-20T04:10:37Z")
It's on CloudFlare, so DVSNI challenge won't work. See > [@How to get a Let's Encrypt certificate while using CloudFlare](https://community.letsencrypt.org/t/how-to-get-a-lets-encrypt-certificate-while-using-cloudflare/6338): > > [… ---
**Author:** ![Vinaysikarwar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/vinaysikarwar/32/3456_2.png) [@Vinaysikarwar](https://community.letsencrypt.org/u/Vinaysikarwar)\ **Post date:** [December 20, 2015, 4:12am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/5 "2015-12-20T04:12:58Z")
Just a min, let me change my dns ---
**Author:** ![Vinaysikarwar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/vinaysikarwar/32/3456_2.png) [@Vinaysikarwar](https://community.letsencrypt.org/u/Vinaysikarwar)\ **Post date:** [December 20, 2015, 4:16am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/6 "2015-12-20T04:16:48Z")
I have changed my domain to my ip. Now it is not on cloudflare. ---
**Author:** ![Vinaysikarwar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/vinaysikarwar/32/3456_2.png) [@Vinaysikarwar](https://community.letsencrypt.org/u/Vinaysikarwar)\ **Post date:** [December 20, 2015, 4:18am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/7 "2015-12-20T04:18:58Z")
Now again when I tried I am getting the same error. Failed authorization procedure. [webtechnologycodes.com](http://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](http://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: - The following ‘urn:acme:error:connection’ errors were reported by the server: ---
**Author:** ![selecadm](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/selecadm/32/5114_2.png) [@selecadm](https://community.letsencrypt.org/u/selecadm)\ **Post date:** [December 20, 2015, 4:21am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/8 "2015-12-20T04:21:05Z")
Now you should wait until DNS cache expires on the LE side. It still connects to CloudFlare. ---
**Author:** ![Vinaysikarwar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/vinaysikarwar/32/3456_2.png) [@Vinaysikarwar](https://community.letsencrypt.org/u/Vinaysikarwar)\ **Post date:** [December 20, 2015, 4:22am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/9 "2015-12-20T04:22:49Z")
OK, Thanks. I will let you know when cache are expires. ---
**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\ **Post date:** [December 20, 2015, 7:47am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/10 "2015-12-20T07:47:15Z")
You can search the forums for other solutions to [cloudflare](https://community.letsencrypt.org/search?q=cloudflare) which may help. ---
**Author:** ![BregnedalSystems](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bregnedalsystems/32/4313_2.png) [@BregnedalSystems](https://community.letsencrypt.org/u/BregnedalSystems)\ **Post date:** [December 20, 2015, 1:42pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/11 "2015-12-20T13:42:53Z")
Try [https://developers.google.com/speed/public-dns/cache](https://developers.google.com/speed/public-dns/cache) LE use google dns 😄 ---
**Author:** ![eva2000](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/eva2000/32/289_2.png) [@eva2000](https://community.letsencrypt.org/u/eva2000)\ **Post date:** [December 20, 2015, 2:56pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/12 "2015-12-20T14:56:14Z")
[quote=“BregnedalSystems, post:11, topic:7365”] Try [https://developers.google.com/speed/public-dns/cache](https://developers.google.com/speed/public-dns/cache) LE use google dns 😄 [/quote] you sure… i thought LE used Akamai’s DNS ? ---
**Author:** ![Vinaysikarwar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/vinaysikarwar/32/3456_2.png) [@Vinaysikarwar](https://community.letsencrypt.org/u/Vinaysikarwar)\ **Post date:** [December 20, 2015, 3:24pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/13 "2015-12-20T15:24:36Z")
I did every thing but always getting the same result. cloudflare is disabled. Failed authorization procedure. [webtechnologycodes.com](http://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](http://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: - The following ‘urn:acme:error:connection’ errors were reported by the server: ---
**Author:** ![KajMagnus](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kajmagnus/32/1764_2.png) [@KajMagnus](https://community.letsencrypt.org/u/KajMagnus)\ **Post date:** [December 28, 2015, 6:09pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/14 "2015-12-28T18:09:16Z")
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](http://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) ---
**Author:** ![px43](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/px43/32/3792_2.png) [@px43](https://community.letsencrypt.org/u/px43)\ **Post date:** [December 30, 2015, 8:29am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/15 "2015-12-30T08:29:55Z")
I had this same error, and fixed it by replacing the top line in my apache config from `` to `` ---
**Author:** ![Renari](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/renari/32/3992_2.png) [@Renari](https://community.letsencrypt.org/u/Renari)\ **Post date:** [January 6, 2016, 5:05am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/16 "2016-01-06T05:05:19Z")
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. ---
**Author:** ![wbswbs](https://avatars.discourse-cdn.com/v4/letter/w/bbe5ce/32.png) [@wbswbs](https://community.letsencrypt.org/u/wbswbs)\ **Post date:** [March 22, 2016, 10:19am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/17 "2016-03-22T10:19:35Z")
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/ ? ---
**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\ **Post date:** [March 22, 2016, 2:06pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/18 "2016-03-22T14:06:14Z")
> 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. ---
**Author:** ![http](https://avatars.discourse-cdn.com/v4/letter/h/6a8cbe/32.png) [@http](https://community.letsencrypt.org/u/http)\ **Post date:** [April 14, 2016, 6:05pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/19 "2016-04-14T18:05:46Z")
I tried a bunch of stuff before I realised that I had to port forward the port 443 to my server 😃 Now it works like a charm! ---
**Author:** ![ashish](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ashish/32/3895_2.png) [@ashish](https://community.letsencrypt.org/u/ashish)\ **Post date:** [December 27, 2016, 5:35am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365/20 "2016-12-27T05:35:10Z")
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. [Next page](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain/7365.md?page=2)