Connection fails if HOST is not 127.0.0.1 using direct connect
See original GitHub issueHi!
thank you for your tool! I was trying it, and figured out there is an error with slightly different use cases:
$ bull-repl connect --host $REDIS_HOST myqueue
BULL-REPL>
connect ECONNREFUSED 127.0.0.1:6379
BULL-REPL> (node:322) UnhandledPromiseRejectionWarning: connect ECONNREFUSED 127.0.0.1:6379
(Use `node --trace-warnings ...` to show where the warning was created)
...
$ bull-repl
BULL-REPL> connect --host 10.170.165.172 myqueue
Connected to 10.170.165.172:6379, prefix: bull, queue: myqueue
BULL-REPL | bull.myqueue>
Do you have a clue on this? Thank you,
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Localhost Refused to Connect Error: 5 Confirmed Ways to Fix It
Localhost refused to connect error can be caused by an incorrectly configured port, insufficient permissions, or an inoperative web server.
Read more >can't establish a connection to the server at 127.0.0.1
It happens on a computer running Windows 10 and one running Vista. I can't tell if it is a problem with the website...
Read more >Cannot connect to 127.0.0.1, localhost, or linux IP address
When I create a new Virtual Host on Apache2, with a different tld like test.tld , it works from inside WSL2, but not...
Read more >cannot connect to SQL Server using local 127.0.0.1 address ...
i am able to establish the connection using the local (with sysadmin role) login from inside the container without issue. however, when using...
Read more >Error: couldn't connect to server 127.0.0.1:27017 - MongoDB
0.1 : 27017 ” is a general error message indicating that your client/driver cannot connect to a server on the specified hostname/IP and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This now works, thank you very much!
Try
0.26.3
or1.7.3
, should be fixed