From cedac956f6b41ba091dedbe4ad7b05baad8728fc Mon Sep 17 00:00:00 2001 From: Ashley <8253488+mrjones-plip@users.noreply.github.com> Date: Mon, 7 Aug 2023 15:49:41 -0700 Subject: [PATCH] fix(#1105): certbot only works on CHT 4.2, instruct to use own domain * Denote certbot only works on CHT 4.2 or later * specify static ip, specify need to change domain in .env file --- .../apps/guides/hosting/4.x/adding-tls-certificates.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/content/en/apps/guides/hosting/4.x/adding-tls-certificates.md b/content/en/apps/guides/hosting/4.x/adding-tls-certificates.md index 265e2fff2..e461748ab 100644 --- a/content/en/apps/guides/hosting/4.x/adding-tls-certificates.md +++ b/content/en/apps/guides/hosting/4.x/adding-tls-certificates.md @@ -54,9 +54,12 @@ Your certificates are now safely stored in the native docker volume. Restart you ## Certbot certificate -_The Certbot integration requires CHT 4.2.0 or later_ +_This Feature available on CHT 4.2.0 or later_ + +If you have a deployment with a static, public IP and a domain name pointing to that IP, you can have Certbot automatically create free TLS certificates by using [their Docker image](https://hub.docker.com/r/certbot/certbot/). + +Assuming your CHT instance is running with the default self signed cert. Be sure to change `cht.example.com` to your domain first though: -If you have a deployment with a publicly accessible domain name, you can have Certbot automatically create free TLS certificates by using [their Docker image](https://hub.docker.com/r/certbot/certbot/). Assuming your CHT instance is **already running with the default self-signed cert**: @@ -94,7 +97,7 @@ Assuming your CHT instance is **already running with the default self-signed cer EOF cat > .env << EOF - DOMAIN=deleteme2-certbot-nginx-cht.plip.com + DOMAIN=cht.example.com STAGING= CHT_SSL_VOLUME=cht_cht-ssl TZ=America/Whitehorse