5 days ago
Custom domains (orcagent.fun + www.orcagent.fun) are intermittently returning 502 "Application failed to respond," while the auto-generated .up.railway.app URL for the same service works continuously without issue. DNS is verified (green checkmark in dashboard) for both custom domains. Deploy logs show no crash or restart at the time of the 502s — the app itself appears healthy and the request never seems to reach the container
Server: railway-hikari
X-Railway-Edge: ams1
X-Hikari-Trace: ams1.9qww
Request ID: Pc36wJDySPu-3yXqY53eZw
Remote Address: 69.46.46.10:443
Timestamp: July 2, 2026, 22:18:01 GMT
6 Replies
5 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 5 days ago
5 days ago
Are both domains -the railway generated one, and your custom one- using the same PORT?
4 days ago
is orcagent.fun proxied through cloudflare (orange cloud)? the .up.railway.app staying clean while only the custom domain flaps points straight at the dns layer, not your app. turn the proxy off, set both records to dns-only. railway does its own certs so cloudflare's just adding a hop that drops connections. that's the intermittent 502.
medim
Are both domains -the railway generated one, and your custom one- using the same PORT?
4 days ago
its fixed now the live versions was using the wrong port. its working now thank ser for the tip 😀
4 days ago
I too have this issue, Im proxying through cloudfront because AWS route53 cant put as CNAME as APEX record. Has something changed regarding TLS on railway side because it seems that cloudfront can no longer verify TLS with railway
4 days ago
we have had to mitigate by putting a function to 301 to the www of our domain name that then cnames over to railway