3 hours ago
Hi, my custom domain www.sonosabrina.it is not being routed to my service,
even though everything appears correctly configured:
- Project: 1cdf4de7-9fe8-4951-b022-3dda2d61d12d
- Environment: production (ba8af62c-e31f-47a8-9cac-6aac81f9c45a)
- Service: 0856d30b-a657-4a0b-9533-775416ecebf1
- Custom domain ID: 63bebe9d-5199-47c0-a552-cf3a6ccc3dda (www.sonosabrina.it)
Symptoms:
-
Certificate status: VALID (TLS handshake works, cert issued for the domain)
-
DNS: CNAME www -> ebaeeuk1.up.railway.app, propagated on all public
resolvers (8.8.8.8, 1.1.1.1, 9.9.9.9) and on the authoritative nameservers
-
Requests return 404 {"message":"Application not found"} with
x-railway-fallback: true (edge: zrh1)
-
Sample request IDs: BhCg26JiRQOqAFyo2h0iww, U9w0jBmgTbKWnlu_jq4OvQ
-
The service domain agente-appuntamento-production.up.railway.app works
perfectly at the same time
Already tried, without success:
-
Deleted and recreated the custom domain (old target was
p00ky3tu.up.railway.app, new one is ebaeeuk1.up.railway.app, DNS updated)
-
Set targetPort to 3000 (the port the app listens on; also tried unset)
-
Forced certificate issuance via API (customDomainIssueCertificate) — worked
-
Redeployed the service twice (serviceInstanceRedeploy)
-
Removed a second custom domain that was stuck in validation
It looks like the edge routing table is not being provisioned for this
domain. Could you take a look? Thanks!
1 Replies
3 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 3 hours ago
3 hours ago
You need to add a TXT record for _railway-verify.www.sonosabrina.it. If you are using the API to add your custom domain, you can find it in verificationToken under status.