Application Hangs (Gateway Timeout) with Traefik, but Responds to Internal curl

[NextStep248]

📜 Description

The latest Postiz Docker Compose application becomes completely unresponsive and causes a 504 Gateway Timeout when accessed through a Traefik reverse proxy. The application's internal logs show a successful startup but no new log entries appear when a request is made, indicating the application is hanging silently.

👟 Reproduction steps

My Setup:

Hostinger KVM 2 VPS (2 vCPU, 8GB RAM) running Ubuntu.

Traefik reverse proxy running in its own docker-compose.yml on a network named root_default.

Postiz running from the official docker-compose.yml, with its main postiz service correctly connected to both its internal postiz-network and the external root_default network.

Crucial Diagnostic Finding: We have definitively proven that all networking layers are correct and the Postiz application is the source of the hang.

Test 1 (Browser Request): Accessing https://postiz.mydomain.cloud results in a 504 Gateway Timeout from Traefik. The Postiz application logs (via pm2 logs) show no new entries during this request.

Test 2 (Internal curl Request): Running curl -v http://postiz:5000 from inside the Traefik container SUCCEEDS. It immediately returns a HTTP/1.1 307 Temporary Redirect to /auth.

Conclusion: The Postiz application is running and responsive to direct requests on its internal network. However, when it receives a request that has been processed and forwarded by Traefik (likely including X-Forwarded-* headers), its internal proxy or application logic hangs silently and fails to produce a response. This is an application-level bug related to reverse proxy compatibility.

👍 Expected behavior

It should load the postiz homepage.

👎 Actual Behavior with Screenshots

Gateway Timeout

💻 Operating system

Linux

🤖 Node Version

v20.18.1

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

Are you willing to submit PR?

None

[FrankieBruno]

Based on my analysis, I've identified the root cause of the issue. The problem is that NestJS is not configured to trust the reverse proxy headers (X-Forwarded-* headers). When Traefik forwards requests with these headers, NestJS doesn't recognize them, which can cause issues with CORS validation and request processing.