9 days ago
Hello Railway Support,
Our custom domain is returning an intermittent Railway edge fallback 404 ("The train has not arrived at the station") for specific paths, even though DNS, certificate, and the underlying deployment are all healthy.
Project ID: d72cdc37-4802-4de0-8722-48fbf32676f6
Service ID: 5d4207ce-611e-40ad-8db7-9b816cb6c1f1
Environment ID: d36e499f-cc5a-42ab-bd30-5710182ce858
Service: i-d3d-sklep
Custom domains: i-d3d.pl, www.i-d3d.pl (both targetPort 3000)
Working Railway service domain: i-d3d-sklep-production.up.railway.app (fully healthy, confirmed working for the same paths)
Affected paths on the custom domain (intermittent 404, "x-railway-fallback" style edge error page, not reaching our app — confirmed via server logs that these requests never appear in our app's HTTP logs when they fail):
Other paths on the same custom domain (/, /faq, /katalog) work most of the time but have also intermittently failed the same way, so this looks like the routing table for this hostname isn't fully/consistently installed across all edge nodes.
We redeployed the service (new deployment succeeded, status SUCCESS) hoping it would force a re-sync of the edge routes, but the issue persists intermittently after the redeploy.
This is a live production e-commerce site and the affected pages are core conversion pages, so this is urgent. Could you please trigger a routing repair for i-d3d.pl and www.i-d3d.pl similar to what was done in this related case: https://station.railway.com/questions/custom-domains-are-verified-and-propagat-69569c8c
Thank you!
1 Replies
9 days ago
The TXT verification record for i-d3d.pl is missing from your DNS, so that domain is currently unverified and its certificate is stuck in the issuance phase. The edge will not route traffic for an unverified domain, which is what produces the fallback 404. Add a TXT record on the host _railway-verify.i-d3d.pl with the verification value shown on the domain's settings page in the Railway dashboard. Your www.i-d3d.pl domain is already verified with a valid certificate and is routing normally. Once the TXT record propagates, verification and certificate issuance for the apex will complete automatically and edge routing will follow.
Status changed to Awaiting User Response Railway • 9 days ago
2 days 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 • 2 days ago