Hello,
We have checked the status of your onj-n8n service, and the service is now fully restored:
- The n8n pod is running and has successfully loaded your two workflows: "抓最新收盤價-v1.02" and "【AI飆股雷達分析器】-進化版-V5.01".
- Your
https://onj.zeabur.app is currently accessible (HTTP 200).
- PostgreSQL has also returned to normal operation.
Root Cause
Your PostgreSQL pod entered an Error state about 32 days ago and remained there, preventing n8n from connecting to the database and causing it to crash and restart repeatedly. During our investigation, we triggered a redeployment of PostgreSQL. Once the new pod came online, it successfully performed an automatic recovery from WAL. n8n was then able to connect to the database and start up smoothly.
Suggested Adjustment
We noticed a non-fatal warning in the n8n startup logs:
The 'X-Forwarded-For' header is set but the Express 'trust proxy' setting is false
This is because n8n is not aware of the Zeabur reverse proxy in front of it. We recommend adding the following to your service's Variables:
N8N_PROXY_HOPS = 1
After adding this and redeploying, the warning will disappear, and rate-limiting as well as request IPs will be correctly identified.
If you have any further questions, please feel free to reply. Thank you!
Forum