The user Vaping_Community is experiencing issues with Let’s Encrypt certificate issuance after reinstalling Discourse on a DigitalOcean droplet. Each rebuild seems to trigger a new certificate request, potentially exhausting the Let’s Encrypt rate limit for their domain, vapingcommunity.co.uk. This has led to an inaccessible site, with HTTPS errors and a broken registration flow. Benjamin_D and pfaffman explain that the 7-day issuance limit may have been hit, and suggest workarounds like using a different subdomain temporarily or waiting a week. The user notes that email functionality was eventually restored, but the site remains broken, and they plan to wait before attempting further fixes. pfaffman also warns that the backup upload may not work over HTTP.
While having some issues getting an email to send, I had to edit the app.yml file and rebuild, it seems this has caused Letsencrypt to issue a new cert each time, should I have commented out the lines in app.yml after the first re-build or is there something else I’ve missed here?
My site is now completely inaccessible on mobile, Non secure server and shows the register screen on laptop but won’t allow me to go any further than this page https://vapingcommunity.co.uk/finish-installation/register giving the error - This site can’t be reached
Seems to be working when I force http or use the IP but then it quickly wants to go back to https and use the domain, the email is still not being sent.
I guess what I need to know is, if I am going to be rebuilding while trying to fix the email issue, should I not have Letsencrypt in the app.yml?
