After upgrading I noticed that my preloader would not resolve. I thought this may have been due to testing an externally hosted redis db, but am seeing it in Docker-hosted redis environments as well. The site seems to function properly in general but this error appears constantly in the web server logs.

[ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)

Any ideas?

I am also getting redis and socket connection errors in 5.8.0. Perhaps these are related to the error you are getting. There are no errors in the dev console except in the web server logs and the web page is not rendering any content.

guptast:

I am also getting redis and socket connection errors in 5.8.0. Perhaps these are related to the error you are getting. There are no errors in the dev console except in the web server logs and the web page is not rendering any content.

It seems that the client got a timeout when trying to connect to the redis server. Do you use redis in a docker container, was it perhaps not yet started while the node server started. Try restarting the node server.

Concerning the server where this particular error occurs, where is Redis server running? Is it running as a Docker container? Or have you installed it by yourself on the server?

It’s trying to connect to 127.0.0.1, which is incorrect if it’s running inside a Docker container

umadmin:

Thanks Tobias. I’m still hitting the above error after updating the package. However, I’m unsure why it’s attempting to connect to 127.0.0.1. I’ll keep investigating.

I had the same issue when I upgraded the redis client to version 4, it is the default host where it is connecting to. In our case it was that the options for the client changed, in version 3 it was new Redis("redis://redis") and in version 4 it became new Redis({ url: "redis://redis" }) . So it looks that in your case also the options for the redis client is probably incorrect.

I found the issue. It was still the bull extension, and the issue lies in operator precedence. I applied a fix to V2 and will push that to GitHub. I won’t have time to update V1.

The new Wappler update handles the config a little differently. I guess that was done so that it works with the new Redis client, but it breaks Ioredis connections:

Right now I receive the [idredis] error just about every second in all of my project environments. I don’t think at this point that I have any configuration or customizations that I’ve made. I updated the wappler-bull-queues extension via npm. It’s possible that I didn’t perform the upgrade from v1 to v2 of wappler-bull-queues correctly but things look ok when comparing files.

I find references to config.redis in two files: config.js and redis.js my config.js looks the same as Tobias’s screen shot. However redis.js still has the old syntax

I manually updated it to match the config.js and it didn’t make a difference, but I’m not sure whether this is indicative of other issues with the project.