--- title: "Lets Encrypt Error: The server could not connect to the client to verify the domain :: Failed to connect to host for DVSNI challenge" description: "

Are you using Lets Encrypt? (If not, you should go ahead and use it to generate SSL certificates to ALL of your web servers).

If you want to run it on EC2 or GCE using the –standalone argument (./letsencrypt-auto certonly –standalone -d example.com) make sure port 443 (for SSL) is open on that server.

Otherwise you’ll get the infamous:

`Are you using Lets Encrypt? (If not, you should go ahead and use it to generate SSL certificates to ALL of your web servers).

" doc_version: "1" last_updated: "2017-06-02" date: 2015-12-31 tags: [aws, EC2, gce, gcp, letsencrypt, Privacy, ssl] canonical: "https://eran.sandler.co.il/2015/12/31/lets-encrypt-error-the-server-could-not-connect-to-the-client-to-verify-the-domain-failed-to-connect-to-host-for-dvsni-challenge/" --- ## Sitemap - [Home](https://eran.sandler.co.il/) Are you using [Lets Encrypt][1]? (If not, you should go ahead and use it to generate SSL certificates to ALL of your web servers). If you want to run it on EC2 or GCE using the –standalone argument (./letsencrypt-auto certonly –standalone -d example.com) **make sure port 443 (for SSL) is open** on that server. Otherwise you’ll get the infamous: `Are you using [Lets Encrypt][1]? (If not, you should go ahead and use it to generate SSL certificates to ALL of your web servers). If you want to run it on EC2 or GCE using the –standalone argument (./letsencrypt-auto certonly –standalone -d example.com) **make sure port 443 (for SSL) is open** on that server. Otherwise you’ll get the infamous: ` Go ahead. Install it. Today. [1]: https://letsencrypt.org/