2 months ago
There was a thread here https://station.railway.com/questions/redis-invalid-database-url-b9d9bb77
I was having issues with postgres and redis where I had to change my ENV vars from the local network to public url. The issue happened a few minutes ago for my redis instance and maybe an hour ago or so for my postgres. After updating from local -> public it started working. For some reason this only affected my sandbox environment (and not production).
I am attaching the project "api-sandbox" but it also affected "sidekiq-sandbox" for redis.
The other thread was marked as solved but I'm still seeing the issue as of a few mins ago.
Edit: just tried redeploying my sidekiq instance and it crashed for "the scheme postgresql does not accept registry part: postgres:...."
4 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
2 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
2 months ago
Hey there!
We had a caching issue with private networking. Really sorry about this. Your network has been restored.
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved echohack • 3 months ago
2 months ago
✅ The ticket Database Connection Issue has been marked as completed.