Fails to connect to redis, when running inside of docker container #763

mishushakov · 2018-12-12T17:26:14Z

Hey, the library works like a charm, thanks a lot. My application is a microservice, which connects to a redis database, which is running inside of docker. However, I can not connect to redis, when my application is running inside of container. I can still connect to redis remotely via cli on other host and it clearly works. I can also run my application outside of docker (directly on my host machine) and it would still connect. But when I build and run the image, it says:

[ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1085:14)

I also tried to provision my application to docker swarm with compose file on the same network as redis

version: "3"
services:
  myapp:
    image: user/app:latest
    deploy:
      restart_policy:
        condition: on-failure
    ports:
      - "5000:5000"
    networks:
      - webnet

  redis:
    image: redis
    ports:
      - "6379:6379"
    volumes:
      - "./data:/data"
    command: redis-server --appendonly yes
    networks:
      - webnet
      
networks:
  webnet:

But it still wouldn't connect

Here is the code, I use in my application:

const redis = require('ioredis')
const appdb = new redis()

module.exports = { db }

Thank you in advance.

The text was updated successfully, but these errors were encountered:

luin · 2018-12-12T17:34:31Z

Have you tried connecting to Redis via host "redis" (see https://docs.docker.com/compose/networking/)?

const redis = require('ioredis')
const appdb = new redis({host: 'redis'})

module.exports = { db }

mishushakov · 2018-12-12T17:38:36Z

Hey, @luin thanks for quick reply, I will try it and comment back in the issue in a second. Thank you

mishushakov · 2018-12-12T17:53:45Z

Still fails, but now with this error:

[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND redis redis:6379
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:57:26)

luin · 2018-12-12T17:59:49Z

Will, that is a network problem and it should not be related to ioredis.

mishushakov · 2018-12-12T18:00:34Z

Ok, then I will try to hack around on my docker machine. Thank you

hendrixroa · 2019-01-03T02:22:45Z

@mishushakov Try delete the networks and replace redis section by:

redis:
    image: redis:latest
    command: ["redis-server", "--bind", "redis", "--port", "6379"]

That works for me.

aiyogg · 2019-09-06T16:22:20Z

Same problem for me, it's still exist I've tried all suggestions above. Who can help me to resolve this, please.

aiyogg · 2019-09-06T17:33:40Z

It's ok after I run docker-compose build then docker-compose up.

portinos · 2019-09-08T09:15:32Z

Hey! How about running redis without docker-compose? I mean, running only the image. I lift the redis container using docker run --name redis.server -d -p 6379:6379 redis:latest but I can't connect from Sails (Node.js) using redis.server as hostname; the response is ENOTFOUND. The docker container is the official: https://hub.docker.com/_/redis/

codebanesr · 2019-11-21T21:58:31Z

You saved me tonight

ravipam · 2019-11-25T04:14:53Z

Unfortunately did not work for me.
I deleted the docker networks. do i need to delete any other network, if any , please guide me.
i still have the error: [ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379

Below is my docker-compose.yml file
version: '3'
services:
redis:
image: 'redis'
command: ["redis-server", "--bind", "redis", "--port", "6379"]
ports:
- "6379:6379"
networks:
- app-tier
apiserver:
build: .
ports:
- "7001:7000"
networks:
- app-tier
depends_on:
- redis
networks:
app-tier:
driver: bridge

below is my app.js
const Redis = require('ioredis');
const redis = new Redis();
I changed the above to const redis = new Redis({host: 'redis'}); but i still get the error

package.json file references to ioredis,
"ioredis": "^4.0.2",

armenr · 2019-12-07T00:23:34Z

I'm having a similar issue, and I've tried it a few different ways as suggested here.

codebanesr · 2019-12-07T09:26:06Z

Try using something like this, i dont see you using the port no to connect
to redis.
redis: new Redis({ port: 6379, host: process.env.REDIS_HOST, password: process.env.REDIS_PASS, })

in place of host you can simply use 'redis'
dont forget to provide the port number

shamim-42 · 2020-05-20T18:16:14Z

After couple of days of stuck today my project is running in your way. Thanks !

mhtsharma948 · 2020-07-21T17:49:50Z

This still doesn't works for me, throwing this error.
redis_1 | 1:M 21 Jul 2020 17:47:13.048 # Could not create server TCP listening socket redis:6380: Name or service not known

saefullohmaslul · 2020-08-11T12:13:01Z

you save my life

cuongndc9 · 2020-09-11T11:02:56Z

The same issue, any solution for this problem? Thanks.

version

"ioredis": "^4.17.3",
"typescript": "^3.8.3"

docker-compose

version: "3"

networks:
  dev_env_network:
    driver: bridge

services:
  redis:
    container_name: redis
    image: redis:6.0-alpine
    restart: always
    ports:
      - 6379:6379
    volumes:
      - redis:/data
    networks:
      - dev_env_network
  auth-service:
    container_name: auth-service
    image: node:12
    working_dir: /app
    env_file: .env
    environment:
      - PG_DB=auth-service
    ports:
      - 50002:50002
    volumes:
      - ../auth-service:/app
      - ../auth-service/node_modules:/app/node_modules
    networks:
      - dev_env_network
    command: yarn start:dev

application

import Redis from 'ioredis';
const redis = new Redis({
    host: 'redis',
    port: 6379,
  });

error

Error: connect ECONNREFUSED 127.0.0.1:6379
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 6379
}

erinoggz · 2020-10-03T12:32:14Z

Solution
const client = redis.createClient({
    host: 'redis-server',
    port: 6379
})

Then rebuild ur docker with => docker-compose up --build

DrPep · 2020-11-22T22:52:39Z

For those who still have an issue here, my docker compose setup is/was configured with a bridged network setup. Adding Redis to the bridged network was required to allow it's network peers to connect:

redis:
  container_name: redis
  image: redis:latest
  command: ["redis-server", "--bind", "redis", "--port", "6379"]
  networks:
    - mynetwork 

networks:
  mynetwork:
    driver: bridge

Then connecting from my docker-hosted Node app with:

import redis from "ioredis"
const appdb = new redis({ host: "redis", port: 6379 })

If you want to then bind from the host machine, add in the requisite docker-compose port binding to the redis config block:

ports:
  - 6379:6379

HTH!

khamphou · 2021-01-30T12:37:46Z

You saved my life too, spent many days to fix this nodejs code, and it looks like it was caused by the docker used in my QNAP container station.

redis:
image: redis:latest
container_name: devredisjs
restart: unless-stopped
environment:
NODE_ENV: development
PORT: 32700
ports:
- "32700:6379"
volumes:
- /share/Smart-Web/cache/redis:/data
command: ["redis-server", "--bind", "redis", "--port", "6379"]

houstondapaz · 2021-02-09T17:48:29Z

I fix this issue changing the redis.conf, by default it use 127.0.0.1, changing to 0.0.0.0 works like a charm
Just create an redis.conf file with this content:

# bind 127.0.0.1
bind 0.0.0.0

and send this file to container, using compose just link this volume

volumes:
  - /path/to/redis.conf:/tmp/redis.conf

AA25 · 2021-04-27T08:01:07Z

For others whose issue wasn't fixed by the above, this stackoverflow answer worked for me https://stackoverflow.com/a/58891367

If you're trying to connect from an app running in a container e.g. node app to redis running in a docker container, then the host string you set in your node app will need to be the name of your redis service name.

sharkdevs · 2021-07-13T22:09:39Z

Solution
const client = redis.createClient({
    host: 'redis-server',
    port: 6379
})

Then rebuild ur docker with => docker-compose up --build

you are a saviour indeed

codeyourwayup · 2022-01-01T16:45:15Z

Solution
const client = redis.createClient({
host: 'redis-server',
port: 6379
})

Then rebuild ur docker with => docker-compose up --build

Works!! thanks

ahmad2smile · 2022-01-09T21:51:17Z

Following seems related: StackExchange/StackExchange.Redis#1002

cindyloo · 2022-02-09T15:15:06Z

inside my docker-compose.yml:

    image: redis:6.2
    restart: always
   
    ports:
      - "6379:6379"

and inside my code:

const redisClient = createClient({
   legacyMode:true
  });

// not sure if I need this or what this should be if we are in legacy mode. use host and port ???
//url: "redis://default:xxx@redis-15574.c17961xxx"

redisClient.on("error", (err) => console.log("Redis Client Error", err));

redisClient.connect();
...
store: new RedisStore({ client: redisClient }),

now I get

2022-02-09T14:57:36.816625+00:00 app[web.1]: Redis Client Error Error: connect ECONNREFUSED 127.0.0.1:6379
2022-02-09T14:57:36.816634+00:00 app[web.1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) {
2022-02-09T14:57:36.816635+00:00 app[web.1]:   errno: -111,
2022-02-09T14:57:36.816636+00:00 app[web.1]:   code: 'ECONNREFUSED',
2022-02-09T14:57:36.816636+00:00 app[web.1]:   syscall: 'connect',
2022-02-09T14:57:36.816637+00:00 app[web.1]:   address: '127.0.0.1',
2022-02-09T14:57:36.816637+00:00 app[web.1]:   port: 6379
2022-02-09T14:57:36.816637+00:00 app[web.1]: }

kmaramr · 2022-06-10T15:30:56Z

@cindyloo Were you able to resolve the connection issue? I have been having the same.

renatoam · 2022-06-17T21:20:50Z

I don't know why, neither if I'm doing something wrong, but what worked for me was put the same name to REDIS_HOST and the container_name, in compose file.

docker-compose.yaml

cache:
    image: redis
    restart: always
    command: redis-server --requirepass ${REDIS_PASSWORD}
    container_name: ${REDIS_HOST} # getting name from .env file

redis.ts

export const redis = new Redis({
  port: Number(process.env.REDIS_PORT) || 6379,
  host: process.env.REDIS_HOST, // getting the same name from .env file
  password: process.env.REDIS_PASSWORD
});

I just could notice that after @luin comment, so thanks fot that!

sbk2k1 · 2023-07-26T16:03:30Z

Update: 26 July 2023

My docker-compose looks like this

redis:
    image: redis:latest
    restart: always
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
    networks:
      - my-network
    ports:
      - 6379:6379

Passing the REDIS url through the Backend like this

environment:
      - ACCESS_TOKEN_SECRET=${ACCESS_TOKEN_SECRET}
      - JWT_SECRET=${JWT_SECRET}
      - PORT=${PORT}
      - MONGO_DB_URL=${MONGO_DB_URL}
      - API_INTERVAL=${API_INTERVAL}
      - REDIS_URL=${REDIS_URL}

.env looks like this

REDIS_URL='redis://redis:6379'

and using it in Node

var client = redis.createClient({url: process.env.REDIS_URL});

myoshi2891 · 2023-09-09T08:02:40Z

#763 (comment)

redis:
    image: redis:latest
    command: ["redis-server", "--bind", "redis", "--port", "6379"]

Thank you so much for sharing your knowledge! You save my day🙏🏻🙏🏻🙏🏻

anushree0809 · 2024-12-06T10:30:46Z

I am getting the same error, but none of the above steps are working, please help!
docker-compose.dev.yaml file

version: "3.8"
services:
mongodb:
image: mongo:latest
ports:
- 27017:27017
volumes:
- mongodb-data:/data/db
networks:
- talawa-network

redis-stack-server:
image: redis/redis-stack-server:latest
ports:
- 6379:6379
volumes:
- redis-data:/data/redis
networks:
- talawa-network

minio:
image: minio/minio
ports:
- "9000:9000"
- "9001:9001"
environment:
- MINIO_ROOT_USER=${MINIO_ROOT_USER}
- MINIO_ROOT_PASSWORD=${MINIO_ROOT_PASSWORD}
command: server /data --console-address ":9001"
volumes:
- minio-data:/data
networks:
- talawa-network

talawa-api-dev:
build:
context: .
dockerfile: Dockerfile.dev
volumes:
- .:/usr/src/app
- /usr/src/app/node_modules
depends_on:
- mongodb
- redis-stack-server
- minio
environment:
- MONGO_DB_URL=mongodb://mongodb:27017
- REDIS_HOST=redis-stack-server
- REDIS_PORT=6379

caddy:
image: caddy/caddy:2.2.1-alpine
container_name: caddy-service
restart: unless-stopped
ports:
- "80:80"
- "443:443"
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile
- ./site:/srv
- caddy_data:/data
- caddy_config:/config

volumes:
mongodb-data:
redis-data:
caddy_data:
caddy_config:
minio-data:

networks:
talawa-network:
driver: bridge
my .env file:
REDIS_HOST=localhost REDIS_PORT=6379 REDIS_PASSWORD=12345678

I am setting up a repository in my local system and followed the steps mentioned.

Malith-Rukshan · 2024-12-19T17:49:20Z

Update redis-stack-server as follows :

redis-stack-server:
    image: redis/redis-stack-server:latest
    command: ["redis-server", "--bind", "redis-stack-server", "--port", "6379"]
    ports:
      - 6379:6379
    volumes:
      - redis-data:/data/redis
    networks:
      - talawa-network

tbm5k · 2025-01-09T16:04:28Z

For anyone still suffering from this, use redis as the IP address in client config.
localhost and 0.0.0.0 didn't work for me, neither did defining a network in my compose file but the IP worked.

Nodejs example:

createClient({url: `redis://redis:6379`});

mishushakov closed this as completed Dec 12, 2018

eric-hc mentioned this issue Dec 10, 2019

ECONNREFUSED Error when adding Job to Queue taskforcesh/bullmq#83

Closed

evandrogrm mentioned this issue Dec 19, 2019

mudar ip de host do redis Rocketseat/adonis-bull#3

Closed

jyeonjyan mentioned this issue Sep 26, 2021

[hotfix] could not connect redis exception themoment-team/K2-server#207

Merged

finnroblin mentioned this issue Feb 5, 2022

Dokku app container failed to start: exec docker-entrypoint.sh failed: Exec format error benawad/lireddit#50

Open

mnlbox mentioned this issue Jun 5, 2023

Cannot use container name for redis cache ardatan/graphql-mesh#5060

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fails to connect to redis, when running inside of docker container #763

Fails to connect to redis, when running inside of docker container #763

mishushakov commented Dec 12, 2018

luin commented Dec 12, 2018

mishushakov commented Dec 12, 2018

mishushakov commented Dec 12, 2018

luin commented Dec 12, 2018

mishushakov commented Dec 12, 2018

hendrixroa commented Jan 3, 2019

aiyogg commented Sep 6, 2019

aiyogg commented Sep 6, 2019

portinos commented Sep 8, 2019

codebanesr commented Nov 21, 2019

ravipam commented Nov 25, 2019

armenr commented Dec 7, 2019

codebanesr commented Dec 7, 2019

shamim-42 commented May 20, 2020 •

edited

Loading

mhtsharma948 commented Jul 21, 2020

saefullohmaslul commented Aug 11, 2020

cuongndc9 commented Sep 11, 2020 •

edited

Loading

erinoggz commented Oct 3, 2020

DrPep commented Nov 22, 2020

khamphou commented Jan 30, 2021

houstondapaz commented Feb 9, 2021

AA25 commented Apr 27, 2021

sharkdevs commented Jul 13, 2021

codeyourwayup commented Jan 1, 2022

ahmad2smile commented Jan 9, 2022

cindyloo commented Feb 9, 2022 •

edited

Loading

kmaramr commented Jun 10, 2022

renatoam commented Jun 17, 2022 •

edited

Loading

sbk2k1 commented Jul 26, 2023

myoshi2891 commented Sep 9, 2023 •

edited

Loading

anushree0809 commented Dec 6, 2024 •

edited

Loading

Malith-Rukshan commented Dec 19, 2024

tbm5k commented Jan 9, 2025

Fails to connect to redis, when running inside of docker container #763

Fails to connect to redis, when running inside of docker container #763

Comments

mishushakov commented Dec 12, 2018

luin commented Dec 12, 2018

mishushakov commented Dec 12, 2018

mishushakov commented Dec 12, 2018

luin commented Dec 12, 2018

mishushakov commented Dec 12, 2018

hendrixroa commented Jan 3, 2019

aiyogg commented Sep 6, 2019

aiyogg commented Sep 6, 2019

portinos commented Sep 8, 2019

codebanesr commented Nov 21, 2019

ravipam commented Nov 25, 2019

armenr commented Dec 7, 2019

codebanesr commented Dec 7, 2019

shamim-42 commented May 20, 2020 • edited Loading

mhtsharma948 commented Jul 21, 2020

saefullohmaslul commented Aug 11, 2020

cuongndc9 commented Sep 11, 2020 • edited Loading

version

docker-compose

application

error

erinoggz commented Oct 3, 2020

DrPep commented Nov 22, 2020

khamphou commented Jan 30, 2021

houstondapaz commented Feb 9, 2021

AA25 commented Apr 27, 2021

sharkdevs commented Jul 13, 2021

codeyourwayup commented Jan 1, 2022

ahmad2smile commented Jan 9, 2022

cindyloo commented Feb 9, 2022 • edited Loading

kmaramr commented Jun 10, 2022

renatoam commented Jun 17, 2022 • edited Loading

sbk2k1 commented Jul 26, 2023

myoshi2891 commented Sep 9, 2023 • edited Loading

anushree0809 commented Dec 6, 2024 • edited Loading

Malith-Rukshan commented Dec 19, 2024

tbm5k commented Jan 9, 2025

shamim-42 commented May 20, 2020 •

edited

Loading

cuongndc9 commented Sep 11, 2020 •

edited

Loading

cindyloo commented Feb 9, 2022 •

edited

Loading

renatoam commented Jun 17, 2022 •

edited

Loading

myoshi2891 commented Sep 9, 2023 •

edited

Loading

anushree0809 commented Dec 6, 2024 •

edited

Loading