2 months ago
Hey - my grist service is not able to connect to either redis service or minio bucket service after I issued a redeployment. I am not sure what will fix this. Tried with both public & private endpoints. Receiving timeout error.
The service is completely down and am totally blocked in production!!
We have about 50 users daily work dependent on this service!!
5 Replies
2 months ago
2 months ago
```2026-01-20 18:56:39.136 - warn: DocWorkerMap: redisClient connection closed
Error: connect ETIMEDOUT fd12:24e4:6259:0:9000:43:1f02:d486:9000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: 'fd12:24e4:6259:0:9000:43:1f02:d486',
port: 9000
}```
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 2 months ago
2 months ago
Is this not a networking issue on the railway platform side?
2 months ago
somehow it started working when I tried the redeployment multiple times. There was a service restart scheduled for minio service every 1hr though - not sure if that would result into this!
Also, I am not able to use the internal domain of the redis, it is working only with public domain
```
2026-01-20 19:11:21.692 - error: PubSubManagerRedis: redisPub connection error: Error: getaddrinfo ENOTFOUND redis
```
2 months ago
Your logs show a connection attempt to fd12:24e4:6259:0:9000:43:1f02:d486 on port 9000. This is an IPv6 address.
If your internal network routing is not configured for IPv6, the application resolves the DNS to an IPv6 address, tries to connect, and hangs until it times out. So, I would recommend you check if your application environment correctly handles IPv6.