a month ago
Description:
Custom domain portal.wishbox.co.il on service wishbox-portal (custom domain id d7688d68-6b78-4b5c-8b74-4391fece17a0) has a VALID certificate, but every request returns HTTP 404 with header "x-railway-fallback: true" — the hostname→service route was never registered on the edge.
Evidence:
- Certificate status is VALID; the API shows the domain syncStatus: ACTIVE on the same edgeId as the service's Railway subdomain, and TLS completes fine.
- https://portal.wishbox.co.il/ (every path) → HTTP 404 with header "x-railway-fallback: true" (x-railway-edge: ams1).
- The Railway subdomain wishbox-portal-production.up.railway.app → 200 from the same service.
- Verified by --resolving portal.wishbox.co.il to each edge IP (69.46.46.39 and 69.46.46.121) with correct SNI — both return the fallback 404.
- DNS is correct and propagated (CNAME portal → ry83yjqc.up.railway.app).
Already tried (fixed the cert but NOT the routing):
- customDomainIssueCertificate (this made the cert VALID), customDomainUpdate, serviceInstanceRedeploy, and several full redeploys (all SUCCESS).
Ask:
Please force-register / re-sync the edge route for portal.wishbox.co.il so it routes to the wishbox-portal service.
Pinned Solution
a month ago
You need to add a TXT record to _railway-verify.portal.wishbox.co.il. You can get the content for it from the verificationToken property under status.
1 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
You need to add a TXT record to _railway-verify.portal.wishbox.co.il. You can get the content for it from the verificationToken property under status.
Status changed to Solved uxuz • about 1 month ago