a month ago
Custom domain www.labdigital.mx on service claude-master never gets edge routing
installed, while all status indicators are green.
- Project: 96256fc7-f014-4b32-ab13-fc3768c6f2bf
- Service: d6d78beb-9e48-4539-9c1c-7b8311c9490b (environment: production)
- Current customDomain id: 574c72f4-a326-4a7f-850d-846e3e66faae (created via dashboard)
Symptoms: HTTPS requests to https://www.labdigital.mx return the Railway edge error
{"status":"error","code":404,"message":"Application not found"}. TLS handshake
succeeds (certificate was issued). The API reports certificateStatus:
CERTIFICATE_STATUS_TYPE_VALID and dnsRecords[0].status: DNS_RECORD_STATUS_PROPAGATED
(currentValue matches requiredValue 9h2a9nmr.up.railway.app), and targetPort: 8080
matches the working service domain (claude-master-production.up.railway.app, which
serves the app correctly).
Already tried: creating the domain 3 times (twice via GraphQL API, once via
dashboard); setting targetPort explicitly; customDomainIssueCertificate mutations;
multiple redeploys both before and after domain creation; DNS verified directly
against the authoritative nameservers (GoDaddy). The service domain routes fine —
only custom domains never get routed.
Could you resync/inspect the edge routing config for this service? It looks like the
host mapping never propagates to the edge proxy despite the green status.
Pinned Solution
a month ago
You need to add a TXT record for _railway-verify.www.labdigital.mx. You can find it in verificationToken under status.
4 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Check if your app is binding to 0.0.0.0 and not 127.0.0.1/localhost.
I also don't see the needed TXT records on your domain.
a month ago
verify that the application's internal port settings align with the configured target port of 8080.
Validate the host mapping through a domain refresh to see if that helps trigger the edge routing propagation.
Also it may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
a month ago
You need to add a TXT record for _railway-verify.www.labdigital.mx. You can find it in verificationToken under status.
a month ago
SOLVED — thank you all! 🎉
darseen nailed it: the domain was missing the ownership-verification TXT record.
I queried the API and found status.verified was false, with a verificationToken
that the dashboard never surfaces. Added the TXT record at
_railway-verify.www with the token value, and within minutes verified flipped
to true and the edge started routing — https://www.labdigital.mx is now live
with a valid certificate.
For anyone hitting the same wall: if your custom domain shows a valid cert and
propagated DNS but the edge keeps returning "Application not found", check
customDomain.status.verified / verificationToken via the API and add that TXT
record. It would be great if the dashboard displayed this requirement — it
currently shows all green while the domain is actually unverified.
Thanks again medim, h701h and especially darseen! 🙏
Status changed to Solved medim • about 1 month ago