From e6f7ede9a704188a0977d0a0257d79383027a425 Mon Sep 17 00:00:00 2001 From: Mauricio Siu Date: Wed, 8 Jul 2026 02:16:26 -0600 Subject: [PATCH] fix: don't force SSL by default so Chatwoot works on http domains FORCE_SSL=true + FRONTEND_URL=https:// made Rails 301-redirect every request to https, which Traefik answered with a sustained 404 because Dokploy-generated template domains are http-only. Default to FORCE_SSL=false and FRONTEND_URL=http://${main_domain} (matching the repo convention); users who terminate TLS can flip these afterwards. Verified on a Dokploy instance: fresh deploy of chatwoot/chatwoot:v4.12.1 migrates and answers HTTP 200 with the onboarding page. Co-Authored-By: Claude Fable 5 --- blueprints/chatwoot/template.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blueprints/chatwoot/template.toml b/blueprints/chatwoot/template.toml index 5947211a..4c238742 100644 --- a/blueprints/chatwoot/template.toml +++ b/blueprints/chatwoot/template.toml @@ -6,9 +6,9 @@ redis_password = "${password}" [config] env = [ - "FRONTEND_URL=https://${main_domain}", + "FRONTEND_URL=http://${main_domain}", "SECRET_KEY_BASE=${secret_key_base}", - "FORCE_SSL=true", + "FORCE_SSL=false", "RAILS_ENV=production", "NODE_ENV=production", "INSTALLATION_ENV=docker",