a month ago
Custom domain returns 404 "Application not found" with `x-railway-fallback: true` despite every control-plane signal healthy. Your AI support concluded this needs ops to inspect Fastly edge.
State (verified):
- Custom domain id: 48a0a708-16d6-4e6f-bb3a-8302ed6c7b2c (app.bizbrain.pro)
- Service: bizbrain-v2 (032e34db-ed8f-42b6-9622-6316d503d011)
- Project: 7983f168-e07d-44da-9075-8e61d267d152
- syncStatus: ACTIVE, targetPort: 8080 (matches Railway-injected PORT)
- DNS: app.bizbrain.pro -> ghbp4gtv.up.railway.app, propagated + currentValue == requiredValue
- TLS cert: valid Let's Encrypt, SAN includes app.bizbrain.pro
- Latest deployment: 72a4c699-2d2a-4005-a876-83bed9596ecc -> CONFIGURE_NETWORK completed with targetPort: 8080
- bizbrain-v2-production.up.railway.app/api/health -> HTTP 200
- app.bizbrain.pro/api/health -> HTTP 404 + x-railway-fallback: true
Already tried (with AI support help):
- customDomainUpdate: targetPort null -> 3000 -> 8080
- Delete + recreate domain (was orphaned from service networking; AI support re-attached)
- Multiple redeploys + deploymentRestart
- DNS re-pointed to new CNAME target after recreate
AI support's conclusion: "Fastly edge cache not invalidating or control-plane -> edge propagation failure. Requires Railway ops access."
Please verify Fastly routing entry for app.bizbrain.pro -> bizbrain-v2:8080 and force re-sync/cache invalidation.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Nothing to do with Fastly. You haven't finished setting up your custom domain correctly; missing TXT record.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Open Railway • about 1 month ago
a month ago
Your content of your TXT record is incorrect. Make sure you have copy-pasted the correct value.
Status changed to Solved osniortiga • about 1 month ago