Skip to content
Redis Connection Timeout
johnjoubert
OP

2 years 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.

Solved

7 Replies

rishimohan

2 years ago

Same for me, was working fine until couple hours back


christopherputra

2 years 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.


moizkamran

2 years 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.


christopherputra

2 years ago

Hi, is there any update on this?


johnjoubert
OP

2 years ago

This seems to be resolved now and it's working normally again.


2 years 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 • over 1 year ago


Status changed to Solved brody • over 1 year ago


rishimohan

2 years ago

This has started to show up once again


Status changed to Awaiting Railway Response Railway • over 1 year ago


Status changed to Solved johnjoubert • over 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...