2 months ago
One of my applications, the container queue, fails when trying to connect to Redis. I've been having this problem for 10 hours.Attachments
1 Replies
2 months ago
Your esalao-queue service is crashing with repeated connection timeouts to redis.railway.internal:6379 via Predis, while your Redis service in the same project is running normally. If your environment was created before October 16, 2025, private networking is IPv6-only, and Predis using tcp:// may default to IPv4 resolution, which would fail. You can verify this by temporarily switching to the public Redis URL (REDIS_PUBLIC_URL), and if that works, you'll need to configure Predis to connect over IPv6 or use the public URL. See our private networking docs for details on legacy environments.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 2 months ago