Hi Railway Support,

My Rexholo service is healthy internally but unreachable through its public Railway domain.

Project: striking-perception

Service: Rexolo

Environment: production

Deployment: 8766bae9-a79c-4424-9baf-68506a6a5a8b

Region: iad

Domain: rexolo-production.up.railway.app

Target port: 8788

The container starts successfully. Railway’s internal healthcheck returns HTTP 200:

GET /ready → 200

But the public endpoint returns:

GET https://rexolo-production.up.railway.app/ready → 502

Response headers include:

x-railway-fallback: true

x-railway-edge: cdg1

Server: railway-hikari

Response body:

{"status":"error","code":502,"message":"Application failed to respond","request_id":"JyxoqGjEQ3Odn0ifg4a9AQ"}

I verified that:

• The domain is attached to Rexolo.
• The domain status is ACTIVE.
• The target port is 8788.
• The application listens on port 8788.
• Prisma and the database are healthy.
• The Docker image builds successfully.
• Restarting the service did not fix the issue.
• Reasserting the domain port did not fix the issue.
• Removing the Dockerfile-level HEALTHCHECK did not fix the issue.
• A fresh successful deployment still returns the same public 502.

Please investigate and repair the Railway edge-to-instance routing association for this active domain and healthy iad deployment. Please do not change my domain, code, database, or secrets.

Thank you.