# Letsencrypt issued on every build?
**URL:** https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611
**Category:** 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:** 8
**Page:** 1
### Author:  [@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
---
### Author:  [@Benjamin\_D](https://meta.discourse.org/u/Benjamin_D)
#### Post date: [February 28, 2022, 6:50pm UTC](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611/2 "2022-02-28T18:50:32Z")
It is working on http isn’t it ? 🤔
`http://vapingcommunity.co.uk/finish-installation/register`
---
### Author:  [@Vaping\_Community](https://meta.discourse.org/u/Vaping_Community)
#### Post date: [February 28, 2022, 6:56pm UTC](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611/3 "2022-02-28T18:56:09Z")
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?
---
### Author:  [@Benjamin\_D](https://meta.discourse.org/u/Benjamin_D)
#### Post date: [February 28, 2022, 7:12pm UTC](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611/4 "2022-02-28T19:12:59Z")
Indeed you might run into a let’s encrypt quota / rate limit soon (if not already)
> [@Connection Timeout/Security Issue](https://meta.discourse.org/t/connection-timeout-security-issue/209652/4):
>
> Let’s Encrypt provides you with a free certificate, which is how your site would be accessible via HTTPS after installation.
>
> It’s possible that your re-installations have used up your 7 day issuance quota for `skuvault.social` . If that’s the case your only options would be:
>
> - Run without HTTPS (bad, don’t do this)
> - Wait a week
> - Use a different domain for setup (this will create headaches down the line)
> - Purchase a certificate (don’t do this)
---
### Author:  [@Vaping\_Community](https://meta.discourse.org/u/Vaping_Community)
#### Post date: [February 28, 2022, 7:14pm UTC](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611/5 "2022-02-28T19:14:07Z")
Looks like I have to wait a week, will it be ok to go ahead and get a backup uploaded on the new install over http?
---
### Author:  [@Benjamin\_D](https://meta.discourse.org/u/Benjamin_D)
#### Post date: [February 28, 2022, 7:30pm UTC](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611/6 "2022-02-28T19:30:42Z")
I think so, with the little caveat of the force\_https parameter (that you will probably have to set to false in the rails console)
ps. [standard install](https://meta.discourse.org/t/142537?silent=true), this is the way… 😉
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [February 28, 2022, 7:41pm UTC](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611/7 "2022-02-28T19:41:39Z")
> [@Vaping\_Community](#):
>
> Looks like I have to wait a week,
A “cheat” is to [Setting up Let’s Encrypt with Multiple Domains](https://meta.discourse.org/t/setting-up-let-s-encrypt-with-multiple-domains/56685) and add some other subdomain (like an extra www).
> [@Vaping\_Community](#):
>
> will it be ok to go ahead and get a backup uploaded on the new install over http?
The uploader might not work on http.
---
### Author:  [@Vaping\_Community](https://meta.discourse.org/u/Vaping_Community)
#### Post date: [February 28, 2022, 7:51pm UTC](https://meta.discourse.org/t/letsencrypt-issued-on-every-build/219611/8 "2022-02-28T19:51:16Z")
Well, I finally got my email to work! 🎉
Now the site is just borked…
I guess I’ll just wait and try again each day until it works