Yeah, it should work either way with the hotfix. The updated code first checks if the ENV vars are present, if not then it tries global.redisClient.options.host and if that is undefined it falls back to global.redisClient.options.socket.host
1 Like
@umadmin, So when deployed using docker, the connections to 127.0.0.1:6379 would fail, as redis is hosted on a different container for it to resolve properly to the container IP for communication over same dokcer network, you would require to use the service name ie ‘redis’ or the container name to be able to connect to redis instance.
So I believe somewhere in the config you have added localhost or 127.0.0.1 which is causing this behavior
I have no idea where I might have done this. I searched the project folder for a reference to 127.0.0.1 and for any references to the external DO hosted redis and no results were returned. I’ll keep digging I guess.
127.0.0.1 is used if the variable containing the Redis server location is undefined, it’s a silent fallback
Since the new update, there was still an issue with ioredis and how Wappler handles the Redis client config. I pushed another fix for V2 of the bull queues extension. The issue led to the usage of 127.0.0.1 for the host in some instances as well.
I’m not sure if you are using V1 or V2 of the bull extension @umadmin, but if you are using V2, then you only need to update the bull extension.
2 Likes
Hi @mebeingken - I’m trying to setup Taskforce, i’m running Redis on my remote server inside the docker container. I cannot find in any documentation how to connect to this Redis instance, all I have is the web server and redis://redis as any connection details but this isn’t what I need .
Can you provide any guidance here as to how to get my connection details? Thanks!
I’ve not used that particular setup, @tbvgl added all the redis ENV code.
Unlisted per @mebeingken’s request.
1 Like
It works on me but I’ve been running into a persistent issue with the job status in my Wappler project’s queue. Instead of completing successfully, all submitted tasks are consistently marked as failed in the job status.
1 Like
