a year ago
I'm trying to set up a redis proxy to be http(s) compatible, and I've decided to use this docker image: serverless-redis-http
The configuration is pretty straight forward where you must only enter a couple of environment variables but it just does not work on railway's private network.
I know that railway private networks are IPv6, therefore I've set a corresponding service variable of the image to be compatible: SRH_IPV6=true
Additionally, in the SRH_CONNECTION_STRING I've set the URL to actually match the private network. After setting everything up, it responds with an error that it can't connect to redis database. Both services are on the same project.
However, when I change the URL to a public network (which I don't want to do because of egress fees) it works without any issues, so it must be related to railway.
I'm using redis-stack instead of normal redis, but this shouldn't cause any issues because as mentioned it worked on a public network. I've also tried to build the serverless-redis-http from scratch with some minor changes to enforce IPv6 but this didn't get me any results.
I've also tried to change the 'bind' redis setting to be more flexible - without results.
How can I fix it?
Thanks.
4 Replies
Status changed to Awaiting User Response Railway • 11 months ago
a year ago
Because my app heavily relies on RediSearch which is only available in redis stack
Status changed to Awaiting Railway Response Railway • 11 months ago
a year ago
And as for the redis HTTP proxy it is because I use redis on serverless environments where TCP/redis protocol may cause issues. Additionally, HTTP is generally faster for this use case.
a year ago
Fixed by moving to another platform.
Status changed to Solved itsrems • 11 months ago