2 months ago
Service starts correctly (logs show "Kyndl server running on port 8080") but all HTTP requests time out with 0 bytes received. Network Flow Logs show zero inbound TCP connections to the container despite the edge accepting TLS connections. Started after migrating from europe-west4 to us-east4 today.
Service ID: a9a236a2-06ed-4513-babb-f6ec300f6864 Project ID: adf2eebd-20f6-488c-b099-0aa12ac0c852 Deployment ID: 2d3d82e2
|Tried: multiple redeploys, port refresh (8080→8081→8080), RAILWAY_BETA_ENABLE_RUNTIME_V2=false, region rollback. Nothing fixed it.
2 Replies
Status changed to Open Railway • about 2 months ago
2 months ago
More context - Network Flow Logs show inbound TCP to container port 8080 (status OK) but Railway's edge proxy at 151.101.2.15 is not forwarding HTTP/2 requests through. TLS terminates at the edge but 0 bytes are returned. Started after migrating from europe-west4 to us-east4 today.
a month ago
Changed region to US-West vs US-East avoiding bad edge entirely (may be a known bad state on Railway's US-East edge proxy that affects services that have been migrated (previously was Europe). Forced a fresh redeploy which also could have helped.
Status changed to Solved msemensi • about 1 month ago