Problem with port forwarding
See original GitHub issueI have a BullMQ + redis instance in k8s that I am trying to connect to
First I port forward:
kubectl port-forward --namespace default svc/redis-master 54321:6379 &
Then with bull-repl@next:
BULL-REPL> connect -r redis://localhost:54321 my-queue Handling connection for 54321 connect ECONNREFUSED 127.0.0.1:6379 BULL-REPL> (node:812) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:6379 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1117:14) (node:812) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:812) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. [ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1117:14)
I can connect ok with rdcli
~$ rdcli -p 54321 127.0.0.1:54321> Handling connection for 54321
127.0.0.1:54321>
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top GitHub Comments
The thread seems to suggest using
bind 0.0.0.0
in the redis config. I use the bitnami helm chart which already does this.I tried testing with a simple ioredis@4.16.0 setup using the port forwarding from above (
rdcli
does not use ioredis):output was
If I do bull-repl connect -r 127.0.0.1:54321 myqueue, it connects, but it is my local macOS redis instance, not the one port forwarded on k8s.
Are you on @latest or @next?