6 days ago
Custom domain www.stroke.gg returns x-railway-fallback: true ("Application not found") and intermittently "The train has not arrived at the station." Cert is VALID, DNS is correct/propagated, app is healthy on port 8080, and the Railway-provided domain on the same service works perfectly.
The binding appears present on some lax1 edge workers but not others as consecutive requests hit different x-hikari-trace workers (lax1.ez9k vs lax1.v9kt) with different results, which looks like partial/incomplete edge propagation.
Project: f10f15c5-897b-460c-9e6b-246eb9c17471
Service: stroke (43ab2d04-9897-48bc-b1f1-c7a8eda3e1b3)
Environment: production (6528a45d-0851-48ae-aba6-1c000a16b29a)
Custom domain: www.stroke.gg (c84fc0ad-62bc-4788-a068-8a146aa72a4e), port 8080
Active deployment: 16382ef3-7fee-46ca-a62b-ecbe5c6b3e9e
App listens on 0.0.0.0:8080 (Railway-injected PORT); logs show Started server: http://0.0.0.0:8080
Recent request IDs: i43RPCuoTgGAC4M_LPU1MQ, 4rzECin6Tpub3oDV0_TJvA
I've already tried: redeploys, cert re-issue, port toggles (8080/auto), delete + re-add, and a support agent re-bound the domain and even then the routing still won't fully propagate. What else can be done?
2 Replies
6 days ago
You need to add a TXT record to _railway-verify.www.stroke.gg.
Status changed to Solved 0x5b62656e5d • 5 days ago