3 months ago
I'm seeing these errors:
21:30:38: redis connection error redis.railway.internal:6379 TimeoutError Timeout connecting to server, 5 retries remaining...
21:30:40: redis connection error redis.railway.internal:6379 TimeoutError Timeout connecting to server, 4 retries remaining...
21:30:42: redis connection error redis.railway.internal:6379 TimeoutError Timeout connecting to server, 3 retries remaining...
21:30:44: redis connection error redis.railway.internal:6379 TimeoutError Timeout connecting to server, 2 retries remaining...
21:30:46: redis connection error redis.railway.internal:6379 TimeoutError Timeout connecting to server, 1 retries remaining...
I though it was perhaps my code, but rolling back to an older working deploy still produces this redis connection issue.
7 Replies
3 months ago
Same for me, was working fine until couple hours back
3 months ago
I have this on my project also, but it's postgres service not redis. getting that timeout error. But when I changed the connection via public host then It's working (It's not ideal since you'll get egress connection and also way slower). It seems like something from railway, happening to me several hours ago. please help railway team.
I have already tried restarting my postgres service and no luck.
3 months ago
Same here, no service is working right now. I think it maybe an outage. But https://status.railway.com shows that it was resolved an hour ago.
3 months ago
Hi, is there any update on this?
3 months ago
This seems to be resolved now and it's working normally again.
3 months ago
Hi there, apologies for the inconvenience.
This was due to an ongoing incident at the time but is now completely resolved. We share status updates on our https://status.railway.com/ page for users to keep up with any ongoing incidents.
Again, apologies for the inconvenience
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved brody • 3 months ago
3 months ago
This has started to show up once again
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved johnjoubert • 3 months ago