# Error at LetsEncrypt validation **URL:** \ **Category:** Product Support\ **Created:** [April 11, 2022, 3:45pm UTC](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921 "2022-04-11T15:45:58Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![MihaVuk](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@MihaVuk](https://meta.discourse.org/u/MihaVuk)\ **Post date:** [April 11, 2022, 3:45pm UTC](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921/1 "2022-04-11T15:45:58Z")
I have setup the self-hosted Docker environment and enabled HTTPS using Let’s Encrypt following the tutorial. > [@Set up HTTPS support with Let's Encrypt](https://meta.discourse.org/t/setting-up-https-support-with-lets-encrypt/40709): > > bookmark This is a guide for enabling HTTPS on an existing Discourse installation using Let’s Encrypt. It assumes prior installation without HTTPS enabled. person_raising_hand Required user level: System Administrator exclamation This guide is only for existing installs where HTTPS is not enabled. Following the [official setup guide](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md) automatically enables HTTPS by default. So you’d like to add https to your Discourse absolutely free, courtesy of our friends at [Let’s Encrypt?](https://letsencrypt.org/)bell I… It always fails on the step below. Setup without HTTPS works fine and the forum is publicly available on HTTP. root@discoursetest3-app:/shared/letsencrypt# cat acme.sh.log … [Mon 11 Apr 2022 02:56:35 PM UTC] [discourse-test3.docentric.com](http://discourse-test3.docentric.com):Verify error:Fetching [http://discourse-test3.docentric.com/.well-known/acme-challenge/iEFjgyseuVL1IzIrTjmfhwv0HqV7EgUmQUVhy1nmnCE:](http://discourse-test3.docentric.com/.well-known/acme-challenge/iEFjgyseuVL1IzIrTjmfhwv0HqV7EgUmQUVhy1nmnCE:) **Timeout after connect (your server may be slow or overloaded)** It seems that ACME challenge is not accessible. --- _[View the full topic](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921)._