Hi Railway Support,

My service RealEnhance (realenhance-production.up.railway.app) is returning Railway’s error page for public requests while the container itself is healthy and reachable by Railway’s healthcheck.

What I’ve observed:

- Deploy logs show the Node process starts and is listening:

server.address() = { address: '0.0.0.0', port: 8080 }

- Railway healthcheck connects to the container and succeeds (I can see TCP + RAW request lines in Deploy logs for host=healthcheck.railway.app).

- Public requests to https://realenhance-production.up.railway.app/ and /favicon.ico return Railway’s “Application failed to respond” / 502 page. The HTTP logs show 502 / Not Found entries (see attached).

- Crucially: for the timestamps of the public 502s, the Deploy logs do NOT show any corresponding TCP/RAW/INCOMING request lines — the healthcheck hits the container, but public requests do not appear to reach it.

What I tried already:

- Removed any custom PORT variable from service Variables.

- Set Healthcheck Path to /healthz-raw.

- Scaled the service to 0 then back to 1 (fresh replica) and restarted several times.

- Confirmed healthcheck hits container and succeeds; container prints listening address and port.

Attached logs (screenshots):

- Deploy logs showing server.address() + healthcheck TCP/RAW request.

- HTTP logs showing 502 / Not Found entries and their timestamps.

Request:

Please investigate the edge → replica routing for this service/environment. It looks like the public domain edge is not forwarding traffic to the healthy replica (or is returning an edge-level 502 before connecting). I can provide exact timestamps for the failing requests if that helps.

Thank you,

Shaun Abrahams / project owner