PostgreSQL deployment stuck on "Creating containers" + TCP proxy connection failures (us-east4)
blakeyoder
HOBBYOP

2 months ago

Environment:

- Region: us-east4-eqdc4a

- Service: PostgreSQL

- Proxy endpoint: [redacted].proxy.rlwy.net:[port]

---

Issue Summary:

Production database is inaccessible via both public proxy and internal networking, and the service deployment is stuck.

---

Issue 1: Public Proxy Rejecting Connections

External connections to the TCP proxy fail immediately:

server closed the connection unexpectedly

This probably means the server terminated abnormally before or while processing the request.

- TCP handshake succeeds (port is reachable)

- PostgreSQL terminates connection during authentication

- Occurs with both sslmode=require and sslmode=disable

---

Issue 2: Deployment Stuck

After attempting to restart the database service:

- Deployment stuck on "Deploy › Creating containers..." for 10+ minutes

- Initialization completed in 00:00

- Container creation not progressing

---

Observations:

- Database logs showed normal checkpoint activity before restart

- Repeated warnings: received direct SSL connection request without ALPN protocol negotiation extension

- Web application (same Railway project) timing out on database queries

- Previous deployment showed "Active" status before restart

---

Impact:

Production application at crownvinyl.co is down. All database-dependent features are failing.

---

Solved

2 Replies

blakeyoder
HOBBYOP

2 months ago

This is resolved. It was an infrastructure maintenance window. It was short notice and during east coast business hours. Hopefully the Railway team is able to be more noisey in communication that take an app down for any amount of time.


blakeyoder

This is resolved. It was an infrastructure maintenance window. It was short notice and during east coast business hours. Hopefully the Railway team is able to be more noisey in communication that take an app down for any amount of time.

2 months ago

Acknowledging the feedback here - we're gonna be working on this as a top priority. Apololgies for the inconvenience!

Considering this resolved, please feel free to create a new thread if this happens again.


Status changed to Awaiting User Response Railway about 2 months ago


Status changed to Solved ray-chen about 2 months ago


Loading...