a month ago
Service: basehelm-saas (Project: BASEHELM OS)
Domain: app.basehelm.in
Domain object ID: b3e8870e-c18a-4707-aa40-a0fa4a4a665a
Certificate status shows Valid/Verified (railway domain status confirms), DNS CNAME correctly resolves to bfsi8l7s.up.railway.app, but every request to the domain returns 502 Bad Gateway with header x-railway-fallback: true. Tried: removing/re-adding the domain, forcing a redeploy, removing a stale conflicting domain object on the same service. Default *.up.railway.app URL for this service works fine (200 OK), so this is isolated to custom domain edge routing.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your domain's DNS, certificate, and verification are all correct, but the edge routes were not installed, which is why you're seeing the 502 fallback. We've started a routing repair for the domain, which should resolve within a few minutes.
Status changed to Awaiting User Response sam-a • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago