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 and the thread closes.

Try selecting the database, press Cmd/Ctrl + K, and redeploy source image.

Hi, thanks I had tried that for a couple of days without success.

I am now getting a new error message so will see if I dig a little deeper.

Thanks

Are there any errors in the logs of the Postgres service?

deploy log on the DB

Does the dashboard connect to the database correctly after a hard refresh (Cmd/Ctrl + Shift + R) or in an incognito window?

Sorry, just checked and updating some things related to the SSH message. Will see if it works.