From a67fcf4f2a629a17b4736317f8d800c3b92a6387 Mon Sep 17 00:00:00 2001 From: Adam Reif Date: Thu, 26 Mar 2026 19:03:20 -0500 Subject: [PATCH] fix: use auto-populated DSTACK_GATEWAY_DOMAIN instead of hardcoded value (CPL-152) GATEWAY_DOMAIN was hardcoded to _.dstack-base-prod5.phala.network which may not match the actual gateway. DSTACK_GATEWAY_DOMAIN is auto-injected by Phala Cloud into the CVM environment per their networking specs. Co-Authored-By: Claude Opus 4.6 (1M context) --- docker-compose.phala.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docker-compose.phala.yml b/docker-compose.phala.yml index 5a6d858c..70d6694a 100644 --- a/docker-compose.phala.yml +++ b/docker-compose.phala.yml @@ -109,7 +109,9 @@ services: # Route 53 provider docs (env vars, optional role assumption): # https://github.com/Dstack-TEE/dstack-examples/blob/main/custom-domain/dstack-ingress/DNS_PROVIDERS.md DOMAIN: "${CERTBOT_DOMAIN}" - GATEWAY_DOMAIN: "_.dstack-base-prod5.phala.network" + # DSTACK_GATEWAY_DOMAIN is auto-populated by Phala Cloud into the CVM. + # https://docs.phala.com/phala-cloud/networking/specifications + GATEWAY_DOMAIN: "_.${DSTACK_GATEWAY_DOMAIN}" DNS_PROVIDER: "route53" TARGET_ENDPOINT: "http://lit-api-server:8000" CERTBOT_EMAIL: "admin@litprotocol.com"