# Letsencrypt issued on every build? **URL:** \ **Category:** Product Support\ **Created:** [February 28, 2022, 6:31pm UTC](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611 "2022-02-28T18:31:02Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![Vaping\_Community](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vaping_community/32/89248_2.png) [@Vaping\_Community](https://meta.discourse.org/u/Vaping_Community)\ **Post date:** [February 28, 2022, 6:31pm UTC](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611/1 "2022-02-28T18:31:02Z")
I recently expanded storage on my DO droplet using this guide - [Move Uploads and Backups to DigitalOcean Block Storage](https://meta.discourse.org/t/moving-uploads-and-backups-to-digitalocean-block-storage/89274) As a result, I broke my instance of Discourse so had to re-install using the guide found here - [https://www.digitalocean.com/community/tutorials/how-to-install-discourse-on-ubuntu-14-04](https://www.digitalocean.com/community/tutorials/how-to-install-discourse-on-ubuntu-14-04) I did the steps needed to install Letsencrypt here - [Set up HTTPS support with Let's Encrypt](https://meta.discourse.org/t/setting-up-https-support-with-lets-encrypt/40709) 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` My site is - [https://vapingcommunity.co.uk](https://vapingcommunity.co.uk) Thanks in advance --- _[View the full topic](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611)._