Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.

This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public. The thread closes, since this isn't something Railway support can take further.

You could change the start command on the Postgres service to this:

/usr/local/bin/docker-entrypoint.sh "$@" 2>&1

That causes it to crash (on the "$@"). Doesn't that skip the entire wrapper?

try removing that part and trying again; that part simply passes all arguments that are passed to the invocation of the start command to the wrapper.

That starts the database but that skips the entire wrapper right? It also makes it impossible to connect to the database from Python.

"Is the server running on that host and accepting TCP/IP connections?"

This change broke our monitoring too. Having all the postgres output sent to stderr is very annoying.