2 months ago
I just get "Service Unavailable". The cause is that I accidentally pushed a bad django migration. The solution will be to delete some old rows from the postgres database and then re-attempt the deploy, but I can't access anything right now to do that.
6 Replies
2 months ago
Your Postgres service is showing as running successfully, so you can connect to it directly to fix the data. You can use the Railway CLI's railway connect command to open a psql shell to your database, or connect externally using the TCP proxy connection string found in your Postgres service's variables tab.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
I think Railway is down. It's down for me too, and I hadn't pushed anything today.
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
We can see your "origami" service is currently in a crashed state, while your Postgres service is running successfully. If you're also unable to access the Railway dashboard itself, we are aware of some users experiencing issues with dashboard login right now. For your database fix, you can still connect to Postgres using the Railway CLI (railway connect) or via the TCP proxy connection string in your service variables to clean up the bad migration data.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
i see this when i try to access the dashboard, and I believe my last deployment didn't go through.
Attachments
Status changed to Awaiting Railway Response Railway • about 2 months ago
gp1n3d4
i see this when i try to access the dashboard, and I believe my last deployment didn't go through.
2 months ago
working now for me
2 months ago
I'm back in now!
Status changed to Solved ameya-taliz • about 2 months ago