Avoiding the Letsencrypt limit

Product Support Self-hosting

AI-generated summary

The discussion revolves around avoiding the Let’s Encrypt certificate limit during a Discourse rebuild. Vaping_Community is concerned about hitting the limit when rebuilding after moving uploads and backups to a new storage drive. pfaffman clarifies that a rebuild isn’t necessary—simply destroying and restarting the app with ./launcher destroy app; ./launcher start app suffices, even after modifying app.yml. Vaping_Community confirms this approach worked, successfully moving the data and using a temporary domain for SSL until the limit resets.

1

Having already hit the limit and having to wait, I know the frustration so I need to know.

  • Does a rebuild ask for a certificate every time?
  • can I comment out the letsencrypt part in app.yml after getting a certificate, will this break something?
  • Is there a way to rebuild without asking for a certificate?

I’ll need to rebuild when I copy uploads and backups to new the storage drive, if it doesn’t work I’ll need to revert changes and rebuild again, I don’t want to hit the limit again and have to wait another week.

Thanks in advance

2

No you don’t. Just

 ./launcher destroy app; ./launcher start app
3

Thank you I’ll try that out and let you know

4

@pfaffman In app.yml it states

After making changes to this file, you MUST rebuild

I’ll be making changes to that file per this tutorial - Move Uploads and Backups to DigitalOcean Block Storage for the new storage

5

Well, that’s only mostly true. I’m pretty sure that a destroy/start is all you need.

EDIT: And I just confirmed moving the location of postgres, editing data.yml and destroy/start worked just fine.

6

@pfaffman thanks for all your help, I finally got everything to work and I’m using a temp domain for SSL until next week.

Followed the tutorial exact and used your suggestions to get it all up and running, thanks again :beers: