New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ETIMEDOUT error trying to connect to a Digitalocean managed Redis instance #1464
Comments
Bull uses https://github.com/luin/ioredis#readme for connecting to Redis, so you should try a simple ioredis example and if does not work you can open an issue on ioredis repo instead. |
For those looking for a solution with DO managed Redis, this worked for me: #1366 (comment) Basically remember to have |
@ronalddddd do you have a sample of how to make it work? I'm still not getting it right :/ |
@BrunoQuaresma are you getting issues connecting with Bull or also with plain ioredis? I would recommend you to first try to connect using ioredis directly, you can pass this connection to Bull for example. If it does not work with ioredis then please fill an issue in that repo instead. |
Thanks! I was able to get it working after reading the ioredis docs: new Queue(
"video",
"rediss://default:<password>@<host>:25061",
{
redis: {
tls: {},
connectTimeout: 30000,
}
}
); |
Description
Trying to connect to a remote Redis instance, hosted on Digital Ocean fails with the following error:
Code to reproduce
I tried instantiating my queue both using a connection string and separated parameters:
Bull version
Bull version: v3.10.0
Redis server version: 5.0.4
Additional information
I was working with a local dockerized Redis server before, and the connection was working fine.
Please note that Digital Ocean requires me to whitelist trusted sources of connection, which include my computer's IP address and another Linux instance hosted on DO in the same region. I tried my code on both environments and it failed in the same way.
Also, Digital Ocean only accepts connection over SSL for Redis instances, which is the reason behind the prefix
rediss://...
Also worth noting that I can connect to the Redis instance, from both my computer and the DO droplet, using redli:
I am not very Redis-savy, but I can provide further information about the Redis server since I have CLI access.
Questions
UnhandledPromiseRejectionWarning
happening inside of BullJS? If so, how can I get more details?rediss://...
prefix enough for BullJS to perform the connection over SSL, as required by DO?The text was updated successfully, but these errors were encountered: