a month ago
Hello Railway team,
I need help with a persistent 502 on my public domain.
Project: carefree-simplicity
Service: espace-partenaires-
Environment: production
Public URL: https://espace-partenaires-production.up.railway.app
Issue:
- Public domain returns 502 "Application failed to respond"
- In deployment/runtime logs, container starts correctly
- Railway internal healthcheck to /healthz returns HTTP 200
Latest deployment:
- ee0e43dd-7c60-4c79-bffa-2705f4794d4f
Recent request IDs:
- 7QfVDlr2RryljeDL2JZdWA
- Q1zOMef9RA-EXY5rWVMv1w
- Cb9QIsavSQG7cqvEs_GTAg
What was already tried:
- multiple redeploys
- restart attempts
- healthcheck path configured to /healthz
- Apache/port/container startup fixed and stable in logs
Can you please check edge routing / public domain attachment for this service?
It looks like the app is healthy internally but edge still responds 502.
Thanks.
1 Replies
a month ago
Your workspace is currently in an inactive state on the trial plan with $3.46 in remaining credits. An inactive workspace means services are not running, which is why the public domain returns a 502 even though the last deployment built successfully. To restore service, you would need to upgrade to the Hobby plan to reactivate your workspace.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago