a day ago
Project: fearless-dream | Service: Marketing-Analytics-Platform | Domain: map-api.onlinejazyky.cz (domain id bbdc48a2-ccaa-46f8-8f94-556bcaf4bc2d)
Timeline: the domain was stuck in VALIDATING_OWNERSHIP for 12+ hours with correct, matching CNAME (points to gfoxmnr9.up.railway.app; dashboard showed currentValue == requiredValue; no CAA record blocking Let's Encrypt). We re-triggered issuance via the customDomainIssueCertificate API mutation - the certificate is now VALID (CN=map-api.onlinejazyky.cz) and targetPort is set to 3000 (the same port the service's *.up.railway.app URL serves correctly).
Problem: the edge still returns 404 "Application not found" for the custom domain - even after a subsequent service deploy, which we understood should activate routing for a newly added domain. The service itself is healthy: the *.up.railway.app URL returns HTTP 200.
Ask: please investigate why edge routing for this custom domain has not activated, and trigger it manually if possible. We deliberately avoided further changes on our side since this is a production service. Thank you!
1 Replies
a day ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 1 day ago
a day ago
You need a TXT record on _railway-verify.map-api.onlinejazyky.cz. You can get the content for it from the verificationToken property under status.