2 months ago
All of a sudden, my services cannot conntect to my redis.
26 Replies
[2026-06-16 07:44:29,360] [PID 4] [Thread-8] [dramatiq.worker.ConsumerThread(test_import.DQ)] [CRITICAL] Consumer encountered a connection error: Error 111 connecting to redis-qmjg.railway.internal:6379. Connection refused.
2 months ago
Please do not ping team members.
2 months ago
Is your Redis online and healthy? (No errors present in logs)
@pepper sorry for a ping. But my services are down. it was working and all of a suddon it doesn't work
If I just move there, no problem. But my main production services is deployed on Railway
2 months ago
I assume manually triggering a redeploy again doesn't do anything?
2 months ago
Same goes for Redis.
Didn't work. I wave redeployed redis and my other services multiple times.
It has been an hour. It doesn't work. I don't know what to do. I am loosing money.
2 months ago
Not 100% sure... It could've been a one-off thing. I'll check with the team if they're free.
2 months ago
Glad it came back. That was a transient host-side networking issue; your Redis stayed healthy but the path to it dropped briefly, which is why it recovered on its own. Nothing wrong on your end. We're working to make this recover automatically. If Railway is your main production, run an HA setup so a single node blip can't take you down. — Angelo