Could not connect to Redis at 127.0.0.1:6379 Connection refused

# Table of Contents

1. Could not connect to Redis at 127.0.0.1:6379 Connection refused
2. Start your Redis server using brew on macOS
3. Start your Redis server on Linux
4. Make sure that the 6379 port is not blocked by your firewall
5. Make sure that your user has the necessary permissions to read and write Redis files

# Could not connect to Redis at 127.0.0.1:6379 Connection refused

The error "Could not connect to Redis at 127.0.0.1:6379: Connection refused" occurs when you try to connect to your Redis server without having started it first.

To resolve the issue, open your terminal and run the redis-server connect to start your Redis server before connecting to it.

Here is the complete error message.

Copied!
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected>

Open your terminal and run the following command to start your Redis server.

Copied!
redis-server

If you are on Windows, you might have to cd into the Redis directory before issuing the redis-server command.

Copied!
cd "C:\Program Files\Redis"

redis-server

If you want to start the Redis server in the background, issue the following command instead.

Copied!
redis-server &

You can also try to run the command with the --daemonize flag if that didn't work.

Copied!
redis-server --daemonize yes

Run the redis-cli command to verify the Redis server has started.

Copied!
redis-cli

set name "bobby hadz"

get name

You can also use the redis-cli ping command to verify that your Redis server is running.

Copied!
redis-cli ping

If you get a PONG response back, then the issue is resolved.

If you get a permissions error when running the redis-server command on macOS or Linux, rerun the command with sudo.

Copied!
sudo redis-server

# or
sudo redis-server --daemonize yes

# Start your Redis server using brew on macOS

Make sure you've installed Redis.

Copied!
brew install redis

If you are on macOS and the issue persists, try using Homebrew to start your Redis server.

Copied!
brew services start redis

1. If the issue persists, check if you have a Redis config file at /usr/local/etc/redis.conf.

Copied!
cat /usr/local/etc/redis.conf

2. If you don't have a config file at /usr/local/etc/redis.conf, then copy the default Redis config file over.

Copied!
cp /usr/local/etc/redis.conf.default /usr/local/etc/redis.conf

3. Run the following command to create the /usr/local/var/db/redis directory on your machine.

Copied!
mkdir -p /usr/local/var/db/redis

4. Run the following command to restart your Redis server.

Copied!
brew services restart redis

# Start your Redis server on Linux

Make sure you have Redis installed.

Copied!
# prerequisite package
sudo apt install lsb-release

# add the repository to the apt index
curl -fsSL https://packages.redis.io/gpg | sudo gpg --dearmor -o /usr/share/keyrings/redis-archive-keyring.gpg

echo "deb [signed-by=/usr/share/keyrings/redis-archive-keyring.gpg] https://packages.redis.io/deb $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/redis.list

# install Redis
sudo apt-get update
sudo apt-get install redis

You can also install Redis from Snapcraft.

Copied!
sudo snap install redis

If you are on Linux, run one of the following commands to start your Redis server.

Copied!
sudo service redis start

# or
sudo service redis-server start

# or
sudo systemctl start redis

# or
sudo systemctl start redis-server.service

You can also try to restart your Redis server.

Copied!
sudo service redis restart

# or
sudo systemctl restart redis

# or
sudo service redis-server restart

# or
sudo systemctl restart redis-server.service

If you get an error when starting your server, issue the following command

Copied!
ps aux | grep redis

The command will return the process ID of Redis.

Run the following command to stop the process.

Copied!
kill -9 <YOUR_PROCESS_ID>

In my case, the process ID is 1014628, so I would issue the following command.

Copied!
kill -9 1014628

After you stop the process, start your Redis server with one of the following commands.

Copied!
sudo service redis start

# or
sudo service redis-server start

# or
sudo systemctl start redis

# or
sudo systemctl start redis-server.service

# Make sure that the 6379 port is not blocked by your firewall

If the issue persists, make sure that the 6379 port is not blocked by your firewall.

Open your terminal and run the following command.

Copied!
sudo ufw allow 6379

# Make sure that your user has the necessary permissions to read and write Redis files

If the issue persists, make sure that your user has the necessary permissions to read, write and execute Redis files.

Your user should have access to the files in the following directories:

• /etc/redis
• /run/redis
• /var/log/redis
• /var/lib/redis

If you need to change the permissions of the directories to the current user, run the following commands.

Copied!
sudo chown -R redis:redis /etc/redis.

sudo chown -R redis:redis /run/redis

sudo chown -R redis:redis /var/log/redis

sudo chown -R redis:redis /var/lib/redis

Try to restart your Redis server after making the change.

Copied!
sudo service redis start

# or
sudo service redis-server start

# or
sudo systemctl start redis

# or
sudo systemctl start redis-server.service

If you get the error MISCONF Redis is configured to save RDB snapshots, click on the link and follow the instructions.