a year ago
My deployment was working fine for the past month until I pushed something just now which triggered a deployment. The deployment status is successful but whenever I try to access the app it returns a 502 error, while the logs states that it can't seem to connect to the db.
I can connect to the db via the public url so might be due to the internal network. Also tried hooking into my local environment with the public database url and it works fine as well.
There were no big changes in the code for the past few hours that could cause infra issues. I did change DBs 7 hours ago but didn't do that to our staging environment which faces the same issue.
5 Replies
10 months ago
Hey grdmnt, hmmm, try redeploying your Postgres, I think you might have added a public TCP Proxy and that needs a redeploy.
Else you can always railway ssh to check out logs and look at why Postgres isn't available on that port.
Status changed to Awaiting User Response Railway • 11 months ago
10 months ago
Isnt that odd since my staging environment has the same issue. Didnt change anything on that end though. I tried changing the link for the DB url to the public one for our staging and now it works, but now it's slower.
Status changed to Awaiting Railway Response Railway • 11 months ago
10 months ago
I changed to using ${{Postgres.DATABASE_URL}} into copy pasting the database URL value directly and everything works now. Would love to be able to go back to just calling the variable though. Was there an error on how I was using it despite it working before and without any var changes it just didnt work? Thanks!
10 months ago
Hello,
Please go back to using a reference variable so we can assess the situation further, unfortunately we are unable to look into any issues when you aren't experiencing any at this moment.
Best,
Brody
Status changed to Awaiting User Response Railway • 11 months ago
10 months ago
Hi Brody,
I've updated our staging environment back to the way it was before and it seems to be working now. Will resolve the thread and will just open another one if it happens again (hopefully not)
Status changed to Awaiting Railway Response Railway • 11 months ago
Status changed to Solved grdmnt • 11 months ago