Hello,
I've been using node-red-contrib-redis for years with no problems in a Docker environment (on a Synology Diskstation NAS).
Node-red in a Docker image (previously sourced from nodered/node-red-docker since node-red v1 from nodered/node-red).
Redis running in a separate Docker image on the same machine. Both docker images using default ports.
Since I upgraded to latest version of node-red-contrib-redis (v1.3.1), I keep getting massive error messages (several per second, flooding the node-red container log file):
[ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
Even tested with fresh, plain docker images of redis and node-red (latest): As soon as node-red-contrib-redis is installed and the config node for "local" is deployed, the error messages start to appear.
Any hints or ideas what could cause these kind of connection errors?
Hello, I've been using node-red-contrib-redis for years with no problems in a Docker environment (on a Synology Diskstation NAS). Node-red in a Docker image (previously sourced from nodered/node-red-docker since node-red v1 from nodered/node-red). Redis running in a separate Docker image on the same machine. Both docker images using default ports. Since I upgraded to latest version of node-red-contrib-redis (v1.3.1), I keep getting massive error messages (several per second, flooding the node-red container log file): [ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
Even tested with fresh, plain docker images of redis and node-red (latest): As soon as node-red-contrib-redis is installed and the config node for "local" is deployed, the error messages start to appear. Any hints or ideas what could cause these kind of connection errors?