# Discourse Failing to Work

**URL:** <https://meta.discourse.org/t/discourse-failing-to-work/229714>\
**Category:** Self-hosting\
**Created:** [June 12, 2022, 12:55pm UTC](https://meta.discourse.org/t/discourse-failing-to-work/229714 "2022-06-12T12:55:29Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)\
**Post date:** [June 12, 2022, 1:59pm UTC](https://meta.discourse.org/t/discourse-failing-to-work/229714/6 "2022-06-12T13:59:35Z")

</div>

When I try and access the address it’s showing up as a ‘connection not secure’, so I’m thinking it could be a letsencrypt issue. If you’ve rebuilt a lot to fix/tweak things during the setup process it can trigger the letsencrypt rate limit. There is a cheeky workaround if you don’t want to wait a week for it to reset (or install on a new subdomain). If you add a second subdomain to your `app.yml` (like below) letsencrypt will treat it like a new certificate request, which should allow you to sidestep the rate limit:

> [@Set up Let’s Encrypt with multiple domains / redirects](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains-redirects/56685/1):
>
> ## Step 1 - letsencrypt
> 
> It’s pretty simple really, add something like the following to your `app.yml` hooks section:
> 
> ```plaintext
> after_ssl:
> - replace:
> filename: "/etc/runit/1.d/letsencrypt"
> from: /--keylength/
> to: "-d second-domain.com -d www.second-domain.com -d other-domain.com -d www.other-domain.com --keylength"
> 
> ```

---

_[View the full topic](https://meta.discourse.org/t/discourse-failing-to-work/229714)._