Forum

I am encountering a 502 Bad Gateway error with my service deployed on Zeabur.

Error Details

• Status Code: 502 Bad Gateway
• Request ID: tpe1::d70027960fc11d90a9b611e1829d3f08
• URL: https://carpenterliu.zeabur.app/

Potential Causes

1. The service is not listening on the correct port—you can check the port your service is listening on in the "Networking" tab of the Zeabur dashboard.
2. The service crashed or stopped responding—you can check the "Logs" tab to troubleshoot the cause of the error.

Please help me troubleshoot this 502 error based on the information above. Using the AI agent did not resolve the issue.

Hi luke.liu,

I checked the n8n service for your undolated project on tpe1 from the backend, and it has returned to normal operation (the latest logs show that it successfully started and executed workflows after 05:30 UTC). Please check https://carpenterliu.zeabur.app to confirm.

It appears that n8n was connecting to the DB slowly during startup, causing it to exceed the startup probe tolerance time, leading to it being killed and restarted. After a few cycles, it recovered on its own; this was not a cluster or network issue. I reviewed the k8s events from the past two months, and all startup probe failure records for this service are concentrated on today; it has not occurred previously.

I would like to confirm: did you only encounter this issue today, or have you experienced similar situations before? If it's convenient, please let me know the approximate frequency so we can evaluate whether further adjustments are needed.