Hi Railway team,

My app service starts successfully, but both public HTTPS domains fail before the app can return any response.

Service:

• perpetual-contentment

Domains tested:

• https://quiltpro.up.railway.app/health
• https://perpetual-contentment-production-3569.up.railway.app/health

Observed behavior:

• Chrome shows ERR_CONNECTION_RESET / ERR_CONNECTION_CLOSED
• Safari says it cannot establish a secure connection
• Browser network panel shows no response headers

What I’ve verified:

• app starts successfully
• Prisma generates successfully
• DB connection succeeds
• migrations are applied
• server listens on 0.0.0.0:8080
• issue reproduces across browsers/devices

Relevant runtime log sequence:

• No pending migrations to apply.
• Quilt Judge Pro API listening on port 8080
• SSL error: unexpected eof while reading
• could not receive data from client: Connection reset by peer
• Stopping Container

This sequence repeats after public connection attempts. It appears the service starts correctly, but inbound HTTPS traffic is being reset before /health can respond, and the container is then stopped.

Could you please check:

1. public domain attachment/provisioning
2. TLS/HTTPS health for both domains
3. whether traffic is reaching the running container
4. why the container is being stopped after inbound connection attempts

Thanks.