I have a fly app that connects to an upstash redis (200M plan) multi-region (iad, ams) that works perfectly for some while and then all the sudden it doesn’t connect anymore, I’m using ioredis with family: 6 option, the internal ip6. Worth mention is that the staging has its own isolated environment and separate upstash instance (free plan multi-region) and the connection issue happens at the same time even do it’s two separate apps.
Are there any known issues with upstash? I’m out of ideas on my side.
Hey, can you post more details about the exceptions you see? Long-lived idle connections will time out after some time, but active connections should not, and new connections should be made without issue.
So I don’t have any logs on the application level that I can see, but when I deploy the application again it starts working again for some while. So it feels like you say something to do with long-lived connections etc.
I just added to ioredesdb: 0 and currently deploying again. otherwise, I don’t have much to go on unfortunately.
I have now connected to the VM and run redis-cli against the upstash URL, while the app is still unreachable the VM can connect successfully, the main difference is that I use the upstash URL and not the internal ipv6 address. Could this be a proxy issue? I can see that there are other similar issues here: upstash redis timeouts - #35 by jsierles
OK, yeah. So that error is different from what you might see if making the connection failed. That error means an existing connection was closed by our proxy because your client was not sending or receiving data.
The issue you linked suggests that node-redis may not handle disconnects too well, though the latest version has some fixes in place. Which version are you on?