The discussion revolves around renewing SSL certificates in Discourse without using ./launcher rebuild app, as the user is concerned about potential disruptions to the database and other components. hokod notes that SSL certificates from Let’s Encrypt sometimes fail to renew automatically and seeks an alternative to rebuild. pfaffman explains that a rebuild is typically only necessary if the base image is outdated and lacks updated root certificates, such as those expired in October. While it might be possible to manually upgrade the running container, pfaffman admits past failures and emphasizes that running outdated software is not sustainable. hokod references a previous discussion where pfaffman clarified that a rebuild is only needed if Let’s Encrypt changes, and pfaffman ultimately recommends a rebuild, suggesting testing on a separate server if concerns exist.
renew ssl (in some cases I encountered, SSL’s free of Let’s Encrypt did not automatically renew).
What command can be used to renew ssl without using: ./launcher rebuild app ?
Because rebuild will affect the database, and many other things. So I ask: What command can be used to renew ssl without having to use: ./launcher rebuild app ?
thank you very much
The only reason they I know that you’d need to rebuild to get a new certificate is that your base image is too old and doesn’t have the new root certificate (that expired in October, I think).
I think that you need to rebuild.
It might be possible to contrive to upgrade the running container, but I think that I tried doing that a few times and failed.
And running an old version of Discourse isn’t a sustainable solution anyway.
I saw one of your posts in a topic, and you also asked the author of discourse : rebuild is it possible to update SSL?
The only solution that I would recommend is to rebuild. If you’re concerned that something will break, then you can do a test on another server.