Hi Railway team,

Please repair/check the Railway edge route for two custom domains that are attached and validated but still return Railway fallback 404 / Application not found.

Account / workspace:

• Central Station user: alexgrama-dev, PRO
• Railway account email: alexgrama8085@gmail.com
• Workspace: Alex Grama's Projects (6ab1af7a-1014-4186-bd9b-0644be4109ac)

Project / service:

• Project: leonehub-platform (2e80883a-9ea3-4400-9703-1a1c8410678e)
• Environment: production (51b0c073-bfa8-47ba-98c4-2bbb32a1f247)
• Service: leone-media-hub (dede872c-c43b-4f5f-aa91-37cb8ef2564c)
• Latest deployment: e7be4744-6f5a-46e8-a228-21670c1f2919, SUCCESS
• App listens on PORT=4847

Custom domains:

• leone-media-hub.com, custom domain id dcc3e952-6df8-4c93-a852-0d8bb48d9279
• www.leone-media-hub.com, custom domain id 99c631d4-99b2-484b-948a-eea6d7d5589e
• Railway currently reports certificateStatus CERTIFICATE_STATUS_TYPE_VALID for both.
• Railway currently reports DNS_RECORD_STATUS_PROPAGATED for both.
• targetPort is set to 4847 for both.

DNS currently set at Spaceship from Railway-provided records:

• @ CNAME dreyy4t0.up.railway.app (authoritative flattened A observed as 69.46.46.94)
• www CNAME 5zs1tafu.up.railway.app (A observed as 69.46.46.24)

Expected:

• https://leone-media-hub.com/api/health and https://www.leone-media-hub.com/api/health route to the same app as the Railway-provided domain.

Actual:

• https://leone-media-hub-production.up.railway.app/api/health returns HTTP 200 with {"status":"ok","service":"api"}.
• https://www.leone-media-hub.com/api/health returns HTTP 404 from Railway edge with x-railway-fallback: true and body {"status":"error","code":404,"message":"Application not found"}.
• Forced SNI checks directly to the Railway target edge IPs also return the same Railway fallback 404:
  • --resolve www.leone-media-hub.com:443:69.46.46.24
  • --resolve leone-media-hub.com:443:69.46.46.94
• App runtime logs only show requests for leone-media-hub-production.up.railway.app; requests to the custom hosts never reach the app.

Already tried:

• Removed stale old/source custom-domain bindings for apex and www.
• Recreated both custom domains on the target service.
• Re-issued certificates.
• Waited for DNS propagation until Railway readback showed propagated/valid.
• Tried targetPort null, then targetPort 4847.
• Restarted the service.
• Redeployed the current deployment artifact; redeploy e7be4744 succeeded.
• Polled for route activation after redeploy; custom domains remained Railway fallback 404.

Can you clear/repair the edge route binding for these two hostnames so they route to service dede872c-c43b-4f5f-aa91-37cb8ef2564c in production?