Can't connect to REDIS


I’m trying to connect to a fresh Redis database created using the fly launch command. I get the correct URL but I cannot connect to the database. Trying with both the actual deployed container and from my computer. Both yield no results.

I’m using Node:

[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND

  let client = new Redis(REDIS_URL);

  client.get(key, (err, result) => {
    if (err) {
      res.send(err, 500)
    } else {
      console.log(result); // Prints "value"

Hi @julienlucca

If you are using ioredis library try the following:

const Redis = require("ioredis");

let client = new Redis("redis://:********");
client.set('foo', 'bar');

Hope that helps,
Sergio Turpín

Hey @sturpin!

Thanks for replying! I’ve also followed the instructions when using link to “Visit the Upstash dashboard”, that contains this snippet you just shared.

It didn’t worked either. I also can’t connect to it using a client like redis-cli.

Hey, does flyctl redis connect work for you?

Connecting with ioredis and similar requires specifying the IPv6 family like:

new Redis({
  host: "",
  family: 6,
  password: "yourpass"

Hey, does flyctl redis connect work for you?

It does!

Tried the snippet and it doesn’t work either… Really not sure why.

I’ve tried spinning up a new fresh redis database using Upstash directly and it works just fine. The thing that I noticed is that on Upstash I get SSL support (or at least the option to make it work) and it connect with no problems, local or deployed on

Are you connecting from within the same Fly organization as your Redis deployment? You wouldn’t be able to connect from your local machine because your database is only available from within the same Fly org.

yes. I’ve tried both scenarios, both yield the same results, sadly. I’ve also double checked if the machine and the database are in the same organization and it is. I’ve created both using fly launch on the same prompt btw.

For now I’m using a separate instance on Upstash. It would be good to use the managed one, since I could simply use the provided ENV var.

OK - can you leave the Redis instance running for debugging?

Sure, I can also share the password if needed, lmk

I wasn’t able to detect any issues connecting to this instance. If you could share a test case, runnable with nodejs, that would help.