Problem Description
My n8n service is deployed on Zeabur, but I receive a 502 Bad Gateway error when accessing it.
Service Information
- Service Name: n8n-dic
- Service ID: 699c29fc3750f5862fd5556e
- Project ID: 694a7a765768a3c5a1bb3a43
- Environment ID: 694a7a764947dd57c4fd3003
- Domain: https://ibet-news.zeabur.app/
Symptoms
Receiving a 502 Bad Gateway error when accessing https://ibet-news.zeabur.app/
- Status Code: 502 Bad Gateway
- Request ID: cgk1::3886e55368ed474279a2e55a332767dc
Confirmed Facts
✅ Service Status: RUNNING ✅ n8n has started normally, logs show: "Editor is now accessible via: https://ibet-news.zeabur.app" ✅ n8n is listening on: 0.0.0.0:5678
Root Cause
Zeabur's health check keeps timing out, causing the service to be marked as unhealthy.
Logs show:
[Zeabur] Pod/service-699c29fc3750f5862fd5556e-7c5c4c5466-5k6zw - Unhealthy: Startup probe failed: Get "http://10.83.203.57:5678/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Attempted Solutions
- ❌ Added environment variable
N8N_LISTEN_ADDRESS=0.0.0.0- No effect - ❌ Added environment variable
N8N_STARTUP_TIMEOUT=120- No effect - ❌ Restarted the service multiple times - No effect
Current Environment Variable Configuration
- N8N_LISTEN_ADDRESS=0.0.0.0
- N8N_HOST=${ZEABUR_WEB_DOMAIN}
- DB_TYPE=sqlite
- NODE_ENV=production
- Other default configurations
Question
Although the n8n application is running normally, Zeabur's health check cannot correctly verify the service status, leading to the 502 error. Is this a platform issue or a configuration issue? Are there any solutions?