# NGINX is Broken?

**URL:** <https://meta.discourse.org/t/nginx-is-broken/134493>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [November 27, 2019, 2:25am UTC](https://meta.discourse.org/t/nginx-is-broken/134493 "2019-11-27T02:25:40Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [November 28, 2019, 6:32am UTC](https://meta.discourse.org/t/nginx-is-broken/134493/32 "2019-11-28T06:32:37Z")

</div>

Here’s a suggestion.

Go sign up for the $5 droplet at DigitalOcean. Follow the install guide to the letter, no copying of additional certificates or anything else.

DO droplets are prorated, if you follow the guide (which takes 30 minutes or less) the cost of proving the install is $0.02. If you don’t want the instance afterwards just hit the destroy button.

If it still fails then there’s something we can begin to troubleshoot.

If it works then it proves this isn’t a discourse issue. If you choose to use a more complicated environment you unfortunately also accept responsibility for the extra challenges it presents. The [standard install](https://meta.discourse.org/t/142537?silent=true) has been proven on the Ubuntu image at DO and their Network policy doesn’t cause issues with Lets Encrypt (but does occasionally need moderate remediation to send email).

Note that if you’ve been requesting and re-requesting the same certificate name it’s possible that Let’s Encrypt has put that particular FQDN on cooldown.

---

_[View the full topic](https://meta.discourse.org/t/nginx-is-broken/134493)._
