Hi, I'm having an issue with my Postgres service that I haven't been able to

resolve after multiple attempts.

Root cause (identified):

During a session where I was integrating OneSignal, a railway up command was

accidentally sent to the Postgres service while the CLI was linked to it instead

of my backend service. This deployed my React frontend code into the Postgres

container instead of the PostgreSQL image.

Current state:

• Source Image in Settings: correctly shows ghcr.io/railwayapp-templates/postgres-ssl:18

• I've done a full Redeploy (not just Restart) from the Railway dashboard — it

  reported success, but Postgres still doesn't respond

• TCP connections are accepted on port 5432, but the PostgreSQL handshake never

  completes (timeout, not connection refused)

• CPU: 0%, Memory: ~0B in metrics

• Volume: 65MB used / 434MB total, PG_VERSION=18, all pgdata files present —

  data appears fully intact

• Both private network connections (from my backend via postgres.railway.internal)

  and external connections (via acela.proxy.rlwy.net:32995) time out

What I need:

Even though Settings shows the correct image, I believe the running container

still has the wrong code (React frontend). The Redeploy didn't seem to replace

it. Can you force a clean container provision from the configured image

(postgres-ssl:18) on your side, or confirm what is actually running in the

container right now?

Project details:

• Project: ticket agent
• Project ID: fabb2fd6-278a-4750-bf84-984b55ed8a51
• Service: Postgres
• Service ID: 3dc61420-a50d-4974-a3a4-44cda04b422a
• Environment: production

Data integrity is critical — I have users depending on this and my last backup

is from June 12. Thank you.