Skip to content
recent Issues connecting to Postgres Database via DATABASE_PUBLIC_URL
eisner-zt-gmbh
OP

22 days ago

As of today I'm having issues connecting to any of my databases from my local pc via the provided public url. I've rerolled and regenerated all parts of the url multiple times and nothing has changed. It seems to be a problem with the proxies? This has never been an issue for the last year, so I'm thinking it's probably related to last week's incident(s)

This is the error django is giving me when I try connecting locally:

django.db.utils.OperationalError: connection to server at "trolley.proxy.rlwy.net" (66.33.22.236), port 59241 failed: server closed the connection unexpectedly

    This probably means the server terminated abnormally

    before or while processing the request.

However, the live version running on railway has no trouble connecting to and using the database, so my conclusion was that the problem must be with the public string..?

Is anyone else having the same issue?

Solved$20 Bounty

Pinned Solution

Try using a different network or a VPN.

Also, just checking, the instance on Railway is using the private URL right?

2 Replies

Status changed to Awaiting Railway Response Railway • 22 days ago


Railway
BOT

22 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 22 days ago


Try using a different network or a VPN.

Also, just checking, the instance on Railway is using the private URL right?


eisner-zt-gmbh
OP

22 days ago

Thanks a lot, the problem was (is) with the local network, probably because our highly competent sysadmin did something to the firewall. :D


Status changed to Solved 0x5b62656e5d • 22 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...