production outage — proxy routing broken for entire project
billyaspden-oss
PROOP
a month ago
Project ID: f16cc9f2-827b-4d0c-b137-df4f7a7b4f23
Affected services:
75e534af-9634-41f7-ba7a-21aa80a263a1(Plato)- Gilpin Onboarding (main app)
Started: ~16:00 BST, 21 April 2026
Symptoms:
- Both services show "Online" in dashboard, healthy deploy logs
- Apps listen on port 8080, logs confirm full Flask init
- Postgres is running, queries execute
curlto both services'*.up.railway.appURLs: TLS completes, HTTP request sent, zero bytes received after 10s timeout- HTTP Logs tab empty on both services
- Private networking (
postgres.railway.internal) was intermittently failing — queries executed on Postgres side but responses never reached client apps (Postgres logs: "could not send data to client: Connection timed out", "FATAL: connection to client lost") - Switching
DATABASE_URLto the public proxy URL made apps start cleanly, but proxy routing still not forwarding HTTP requests - Renaming subdomain provided one brief working window, subsequent renames all broken
This is a live hotel staff training app. Please escalate.
1 Replies
Railway
BOT
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
Status changed to Closed brody • about 1 month ago