a month ago
- Custom domain: app.loveinabigworld.com
- Service: lbw-backend-us
- Issue: x-railway-fallback: true on all requests despite domain showing green in dashboard
- Request ID from the header: KB9115KmRCa7yadOBT7zVQ
still getting a 502 even though the cert process completed and everything looks green. have waited a long time so it doesn't seem like a propagation delay
3 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
removing and re-adding got me further the last time I did it (I've tried this several times now...working with Claude who ran out of options so told me to go to support) which is when I saw the cert being issued which I hadn't seen before...progress but not success yet. this is what he says:
Confirmed — the server binds to 0.0.0.0 and reads process.env.PORT:
▎ const port = Number(process.env.PORT ?? 3000)
▎ serve({ fetch: app.fetch, port, hostname: '0.0.0.0' })
▎ Not the issue. The x-railway-fallback: true header on every request suggests the Fastly routing rule for
app.loveinabigworld.com was never provisioned to point at the backend service, even though the domain shows green in the
dashboard.
i tried to go direct to support but the bot put me in the forum with a bounty. appreciate you trying to help. how can i get someone from the Railway team to look?
a month ago
Your domain seems to be linked to a Vercel deployment...? Make sure you don't have any conflicting DNS records.
a month ago
yes...moved the functionality to Vercel because I wasn't getting the right support. am closing the thread.
Status changed to Open brody • about 1 month ago
Status changed to Solved brody • about 1 month ago