Bad gateway Error code 502
userdeh
HOBBYOP

3 months ago

why this happen?

Solved$10 Bounty

Pinned Solution

userdeh
HOBBYOP

3 months ago

resolved.

8 Replies

userdeh
HOBBYOP

3 months ago

{
  "requestId": "DrKghpOMR5mkQ9qIAax-fw",
  "timestamp": "2025-12-16T09:01:17.070825118Z",
  "method": "GET",
  "path": "/swagger-ui",
  "host": "api.mestra.chat",
  "httpStatus": 502,
  "upstreamProto": "",
  "downstreamProto": "HTTP/2.0",
  "responseDetails": "Retried single replica",
  "totalDuration": 1020,
  "upstreamAddress": "",
  "upstreamRqDuration": 1018,
  "txBytes": 4682,
  "rxBytes": 1476,
  "edgeRegion": "us-east4-eqdc4a",
  "upstreamErrors": "[{\"deploymentInstanceID\":\"5cc5401a-d3af-4d5f-8b60-207f6b4dc156\",\"duration\":90,\"error\":\"connection refused\"},{\"deploymentInstanceID\":\"5cc5401a-d3af-4d5f-8b60-207f6b4dc156\",\"duration\":172,\"error\":\"connection refused\"},{\"deploymentInstanceID\":\"5cc5401a-d3af-4d5f-8b60-207f6b4dc156\",\"duration\":756,\"error\":\"connection refused\"}]"
}
bmask2020
FREE

3 months ago

i still get error code 502

ray-chen
EMPLOYEE

3 months ago

Hey! Are you currently experiencing any issues? I believe this was related to an outage we experienced (https://status.railway.com/cmj89j6z2000qodpsfs4nc2gb) that has since been resolved.

Status changed to Awaiting User Response Railway • 3 months ago

chandrika
EMPLOYEE

3 months ago

Hi there, just checking in to make sure you're all set, please let us know if we can help in any way.

We'll also be sharing a post-mortem for the incident and are very sorry for any inconvenience.

Best,

The Railway Team

Status changed to Awaiting User Response chandrika • 3 months ago

bmask2020
FREE

3 months ago

still get same error 502

https://hotel-app-production-c3a2.up.railway.app

Status changed to Awaiting Railway Response Railway • 3 months ago

fra
HOBBYTop 10% Contributor

3 months ago

Can you check if the port exposed in the app is the same as the one set in Setting->Public Network? Usually Railway uses the port 8080

userdeh
HOBBYOP

3 months ago

resolved.

Status changed to Solved noahd • 3 months ago

chandrika
EMPLOYEE

3 months ago

Hi, we wanted to share an update on this.

We published an incident report for December 16, 2025: https://blog.railway.com/p/incident-report-december-16-2025

Once again, we're deeply sorry for the impact this caused. We're actively working to eliminate the class of issues that contributed to this incident and to make the platform more resilient.

Best,

The Railway Team

Status changed to Awaiting User Response Railway • 3 months ago

Status changed to Solved chandrika • 3 months ago

Loading...