# Turned on Lets Encrypt and requests are timing out

**URL:** <https://meta.discourse.org/t/turned-on-lets-encrypt-and-requests-are-timing-out/82319>\
**Category:** Product Support\
**Created:** [March 6, 2018, 3:57pm UTC](https://meta.discourse.org/t/turned-on-lets-encrypt-and-requests-are-timing-out/82319 "2018-03-06T15:57:20Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![David\_fs](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david_fs/32/88716_2.png) [@David\_fs](https://meta.discourse.org/u/David_fs)\
**Post date:** [March 6, 2018, 3:57pm UTC](https://meta.discourse.org/t/turned-on-lets-encrypt-and-requests-are-timing-out/82319/1 "2018-03-06T15:57:20Z")

</div>

The only thing I can see in the access logs is:

```
217.138.11.237 - - [06/Mar/2018:15:09:04 +0000] "POST /message-bus/c2a0f3d9a16a490eb6be56bc668d6c81/poll?dlp=t HTTP/1.1" 301 185 "http://marketdiscuss.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"

```

this is a standard Digital Ocean setup droplet setup.

Config details match the instructions, I can see the .key and .cert files just fine in

```
shared/ssl/*{key, cert}

```

Ran `discourse-setup` and says everything ran successfully, rebuilds and the docker container is live.  
I just can’t seem to hit the server by loading the page in my browser. Had this working perfectly, with people signing up and everything. But wanted the ssl for better seo I guess.

Any help would be awesome: Chrome seems to acknowledge the the cert is valid:

 ![10](https://global.discourse-cdn.com/meta/original/3X/c/c/ccea2cc0973b6981c2adfcb98254960638c4902f.png)

I am able to enter the container just fine and view logs live etc.. everything seems like it’s OK, but it’s in reality 😕

---

_[View the full topic](https://meta.discourse.org/t/turned-on-lets-encrypt-and-requests-are-timing-out/82319)._
