Discourse Failing to Work

[JammyDodger]

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:

@brahn

Step 1 - letsencrypt

It’s pretty simple really, add something like the following to your app.yml hooks section:

  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"