Hello Railway Support,

My application is Online and responds successfully inside its container, but the Railway-provided public domain consistently returns an edge fallback 404. Could you please inspect the domain-to-deployment routing association?

Project: wig-bangladesh-ai-sales-agent

Project ID: a4a4f538-4929-49cc-9115-adf90bb3bcf4

Environment: production

Environment ID: 574a4897-62cb-46dc-adb9-734e399eba65

Service: app

Service ID: 578a98c9-8899-4685-ae86-e0893460e77e

Active deployment ID: 209d305b-ea64-46f8-93ba-6f3585b5c0a9

Domain: https://app-production-c611.up.railway.app

Domain ID: 3d7d47e4-9cdf-406a-a030-916c098baf33

Target port: 8080

Domain sync status: ACTIVE

Service region: iad

Verified diagnostics:

The deployment is Active and deployment logs show a successful startup.

All six Prisma migrations applied successfully.

PORT is 8080.

GET http://127.0.0.1:8080/ returns HTTP 200.

GET http://10.186.140.51:8080/ returns HTTP 200.

Public HTTPS GET and HEAD requests return HTTP 404 with x-railway-fallback: true.

The deployment's Network Logs show no HTTP entries at this time.

A previous CLI log query timed out contacting backboard.railway.com, so it did not establish whether matching logs exist.

Most recent failed request:

Request ID: VgTERyFbTyG1qy22H4GxDA

Time: 2026-09-07 09:46:21 GMT

Edge: sin1

Upstream zone: railway/us-east4-eqdc4a

Trace: sin1.98a6

Please check whether the public domain is correctly associated with the active deployment and whether the edge routing configuration is healthy. I would like to preserve the existing service, domain, deployment, and persistent volume. Please advise before any resource recreation is necessary.

Thank you.