From 949cce10978b874204d9ba0fcc274e6ddd06679d Mon Sep 17 00:00:00 2001 From: Xidik Date: Sun, 22 Mar 2026 22:02:13 +0700 Subject: [PATCH] fix(service): allow overriding GOTRUE_SITE_URL in Supabase template The Supabase template hardcoded GOTRUE_SITE_URL to the internal Supabase Kong URL, which caused OAuth redirects to go to the Supabase API domain instead of the user's frontend domain. This broke Google OAuth, magic links, and other redirect-based auth flows. Allow users to set GOTRUE_SITE_URL in the Coolify UI to their frontend domain while keeping the Supabase URL as a sensible default. Fixes #5581 --- templates/compose/supabase.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/compose/supabase.yaml b/templates/compose/supabase.yaml index fad059a08..496bade26 100644 --- a/templates/compose/supabase.yaml +++ b/templates/compose/supabase.yaml @@ -975,7 +975,7 @@ services: - GOTRUE_DB_DRIVER=postgres - GOTRUE_DB_DATABASE_URL=postgres://supabase_auth_admin:${SERVICE_PASSWORD_POSTGRES}@${POSTGRES_HOSTNAME:-supabase-db}:${POSTGRES_PORT:-5432}/${POSTGRES_DB:-postgres} # The base URL your site is located at. Currently used in combination with other settings to construct URLs used in emails. - - GOTRUE_SITE_URL=${SERVICE_URL_SUPABASEKONG} + - GOTRUE_SITE_URL=${GOTRUE_SITE_URL:-${SERVICE_URL_SUPABASEKONG}} # A comma separated list of URIs (e.g. "https://foo.example.com,https://*.foo.example.com,https://bar.example.com") which are permitted as valid redirect_to destinations. - GOTRUE_URI_ALLOW_LIST=${ADDITIONAL_REDIRECT_URLS} - GOTRUE_DISABLE_SIGNUP=${DISABLE_SIGNUP:-false}