I am now deploying a new environment. My domain name and domain name certificate have been prepared, but how do I cancel your built-in ssl certificate function during deployment?
AI-generated summary
The discussion revolves around skipping the built-in SSL certificate setup during Discourse deployment. Guo_SpicyGum asks how to disable Let’s Encrypt during setup, and italo suggests leaving the email field blank. italo advises against this, recommending Let’s Encrypt for ease and reliability, while also linking to a guide on using custom SSL certificates. Guo_SpicyGum inquires about replacing the default certificate with their own and whether this eliminates the need for an external nginx. pfaffman clarifies that Discourse uses its own nginx container and that external nginx is unnecessary, though manual certificate management is possible if desired.
Hi Guo!
I believe you can skip it by leaving the let’s encrypt email blank when asked by the setup script.
ok, i try again.
However it’s very recommended to use let’s encrypt.
See this topic for more information on why and how to setup your own certificate.
I understand, this is the case, my own domain name already has an ssl certificate, or can I replace my own certificate file into the template? In this way, I don’t need to run an nginx in front of the discourse service to do ssl?
I believe you can just put your email on the let’s encrypt prompt and it will work.
Discourse uses nginx in the container that it builds; you do want that nginx. You do not need to have another nginx in front of the discourse container. The standard install will request and maintain a certificate from let’s encrypt.
If you really love your certificate that you have already, and want to spend extra time learning a hard way to manage certificates and are sure that you will remember to manually update your existing certificate, you can follow the guide linked above.