3 Replies
a month ago
Your deployment has no runtime logs, which typically means the application is crashing on startup or not listening on the correct host and port. A 502 means our proxy cannot reach your application - ensure your app binds to 0.0.0.0 on the port from the PORT environment variable, as described in our troubleshooting guide.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your environment is a legacy environment that uses IPv6-only private networking, and the error shows a TypeError: fetch failed when requesting scoringbackend.railway.internal:8080. The Scoring_Backend service appears to be running, so the fetch failure is likely related to IPv6 connectivity. In legacy environments, both the calling service and the target service must support IPv6. See our private networking docs for details on configuring services to listen on :: in legacy environments.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved co-fa • about 1 month ago