From 537c2bbaf2e058f36f7be6baf63d4cc2e4c9a800 Mon Sep 17 00:00:00 2001 From: hsiegeln <37154749+hsiegeln@users.noreply.github.com> Date: Sun, 5 Apr 2026 00:44:24 +0200 Subject: [PATCH] fix: use LOGTO_PUBLIC_ENDPOINT for Logto ENDPOINT config Logto's ENDPOINT must be the browser-accessible URL (not Docker internal). When .env sets LOGTO_ENDPOINT=http://logto:3001, it was overriding the default and causing Logto to redirect browsers to an unreachable hostname. Co-Authored-By: Claude Opus 4.6 (1M context) --- docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index cf0721d..7c439c0 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -39,7 +39,7 @@ services: entrypoint: ["sh", "-c", "npm run cli db seed -- --swe && npm start"] environment: DB_URL: postgres://${POSTGRES_USER:-cameleer}:${POSTGRES_PASSWORD:-cameleer_dev}@postgres:5432/logto - ENDPOINT: ${LOGTO_ENDPOINT:-http://localhost:3001} + ENDPOINT: ${LOGTO_PUBLIC_ENDPOINT:-http://localhost:3001} ADMIN_ENDPOINT: ${LOGTO_ADMIN_ENDPOINT:-http://localhost:3002} TRUST_PROXY_HEADER: 1 healthcheck: