Select Page


Redis is an in-memory, NoSQL, key-value cache and retailer that may also be persevered to disk. It used to be designed to be used by way of relied on shoppers in a relied on setting, without a powerful safety features of its personal. To underscore that time, here is a quote from the official Redis website:

Redis is designed to be accessed by way of relied on shoppers inside of relied on environments. Which means in most cases it isn’t a good suggestion to reveal the Redis example at once to the web or, basically, to an atmosphere the place untrusted shoppers can at once get entry to the Redis TCP port or UNIX socket.

. . .

Normally, Redis isn’t optimized for optimum safety however for optimum efficiency and straightforwardness.

Regardless of this, Redis does have a couple of fundamental safety features constructed into it. Those come with the facility to create a unencrypted password and the liberty to rename and disable instructions. Significantly, it lacks a real get entry to keep an eye on gadget.

Those options can’t, on their very own, make sure that the protection of your Redis Set up. On the other hand, configuring them continues to be a large step up from leaving your database totally unsecured.

On this instructional, you’ll be able to learn configure the few safety features Redis has, and make a couple of adjustments in your gadget’s configuration which can spice up the protection posture of a standalone Redis set up on an Ubuntu server.

Notice that this information does no longer deal with eventualities the place the Redis server and the customer programs are on other hosts or in numerous information facilities. Installations the place Redis visitors has to traverse an insecure or untrusted community require a completely other set of configurations, corresponding to putting in an SSL proxy or a VPN between the Redis machines, along with those given right here.

Must haves

For this instructional, you’ll be able to want:

Step 1 — Verifying that Redis is Operating

First, SSH in in your server along with your non-root person.

To test that Redis is operating, open up a Redis command line with the redis-cli command:

Notice: If you happen to already set a password for Redis, it’s a must to authenticate with the auth command after connecting:



In case you have no longer set a password for Redis, you’ll learn how to take action in Step Four of this instructional.

Check the relationship with the ping command:

If Redis is operating accurately, you are going to see the next:



Following this, go out the Redis command line:

Now that you simply’ve showed that Redis is operating and dealing accurately, you’ll transfer directly to a very powerful step for reinforcing your server’s safety: configuring a firewall.

Step 2 — Securing the Server with UFW

Redis is simply an software that is operating for your server. As it has just a few basic safety features of its personal, step one to really securing it’s to protected the server it’s operating on. In relation to a public-facing server like your Ubuntu 18.04 server, configuring a firewall as described within the Initial Server Setup Guide for Ubuntu 18.04 is that first step. Practice that hyperlink and arrange your firewall now should you haven’t already executed so.

If you happen to aren’t positive whether or not you place up a firewall or if it’s energetic, you’ll take a look at this by way of operating the next:

If you happen to adopted the Preliminary Server Setup Information for Ubuntu 18.04, you are going to see the next output:


Standing: energetic To Motion From -- ------ ---- OpenSSH ALLOW Any place OpenSSH (v6) ALLOW Any place (v6)

If you happen to’ve carried out the firewall laws utilizing that information, then you do not want so as to add an additional rule for Redis as a result of, by way of default, UFW drops all incoming visitors until it’s explicitly allowed. Since a default standalone set up of the Redis server is listening simplest at the loopback interface (, or localhost), there will have to be no worry for incoming visitors on its default port.

For more info on upload laws, please see this guide on common UFW rules and commands.

Step 3 — Binding to localhost

By means of default, Redis is simplest obtainable from localhost. On the other hand, should you adopted a distinct instructional to configure Redis than the only given in the necessities phase, you could have up to date the configuration record to permit connections from anyplace. This isn’t as protected as binding to localhost.

Open the Redis configuration record for enhancing:

  • sudo nano /and so on/redis/redis.conf

Find this line and ensure it’s uncommented (take away the # if it exists):

/and so on/redis/redis.conf


Save and shut the record when completed (press CTRL + X, Y, then ENTER).

Then, restart the provider to make sure that systemd reads your adjustments:

  • sudo systemctl restart redis

To test that this transformation has long past into impact, run the next netstat command:

  • sudo netstat -lnp | grep redis


tcp 0 0* LISTEN 2855/redis-server 1

This output displays that the redis-server program is sure to localhost (, reflecting the exchange you simply made to the configuration record. If you happen to see every other IP deal with in that column (, as an example), then you definately will have to double take a look at that you simply uncommented the right kind line and restart the Redis provider once more.

Now that your Redis set up is simplest listening in on localhost, it is going to be tougher for malicious actors to make requests or achieve get entry to in your server. On the other hand, Redis isn’t recently set to require customers to authenticate themselves prior to making adjustments to its configuration or the knowledge it holds. To treatment this, Redis lets you require customers to authenticate with a password prior to making adjustments by the use of the Redis consumer (redis-cli).

Step 4 — Configuring a Redis Password

Configuring a Redis password allows one among its two integrated safety features — the auth command, which calls for shoppers to authenticate to get entry to the database. The password is configured at once in Redis’s configuration record, /and so on/redis/redis.conf, so open that record once more along with your most well-liked editor:

  • sudo nano /and so on/redis/redis.conf

Scroll to the SECURITY phase and search for a commented directive that reads:

/and so on/redis/redis.conf

# requirepass foobared

Uncomment it by way of eliminating the #, and alter foobared to a protected password.

Notice: Above the requirepass directive within the redis.conf record, there’s a commented caution:

/and so on/redis/redis.conf

# Caution: since Redis is beautiful speedy an outdoor person can take a look at as much as
# 150ok passwords in keeping with 2nd in opposition to a excellent field. Which means you will have to
# use an overly robust password another way it is going to be really easy to damage.

Thus, it’s essential that you simply specify an overly robust and really lengthy price as your password. Moderately than make up a password your self, you’ll use the openssl command to generate a random one, as within the following instance. The pipe to the second one openssl command will take away any line breaks which might be output by way of the primary command:

  • openssl rand 60 | openssl base64 -A

Your output will have to glance one thing like:



After copying and pasting the output of that command as the brand new price for requirepass, it will have to learn:

/and so on/redis/redis.conf

requirepass RBOJ9cCNoGCKhlEBwQLHri1g+atWgn4Xn4HwNUbtzoVxAYxkiYBi7aufl4MILv1nxBqR4L6NNzI0X6cE

After atmosphere the password, save the record, and restart Redis:

  • sudo systemctl restart redis.provider

To check that the password works, get entry to the Redis command line:

The next displays a series of instructions used to check whether or not the Redis password works. The primary command tries to set a key to a price prior to authentication:

That may not paintings since you didn’t authenticate, so Redis returns an error:


(error) NOAUTH Authentication required.

The following command authenticates with the password specified within the Redis configuration record:

Redis recognizes:



After that, operating the former command once more will be triumphant:



get key1 queries Redis for the worth of the brand new key.



After confirming that you simply’re ready to run instructions within the Redis consumer after authenticating, you’ll go out the redis-cli:

Subsequent, we’re going to have a look at renaming Redis instructions which, if entered by way of mistake or by way of a malicious actor, may motive critical harm in your device.

Step 5 — Renaming Unhealthy Instructions

The opposite safety function constructed into Redis comes to renaming or totally disabling positive instructions which might be thought to be bad.

When run by way of mistake or by way of unauthorized customers, such instructions can be utilized to reconfigure, smash, or another way wipe your information. Just like the authentication password, renaming or disabling instructions is configured in the similar SECURITY phase of the /and so on/redis/redis.conf record.

One of the vital instructions which might be thought to be bad come with: FLUSHDB, FLUSHALL, KEYS, PEXPIRE, DEL, CONFIG, SHUTDOWN, BGREWRITEAOF, BGSAVE, SAVE, SPOP, SREM, RENAME, and DEBUG. This isn’t a complete listing, however renaming or disabling all the instructions in that listing is a great place to begin for reinforcing your Redis server’s safety.

Whether or not you will have to disable or rename a command depends upon your particular wishes or the ones of your web site. If you already know you are going to by no means use a command which may be abused, then you might disable it. Differently, it might be to your highest pastime to rename it.

To allow or disable Redis instructions, open the configuration record another time:

  • sudo nano /and so on/redis/redis.conf

Caution: The next steps appearing disable and rename instructions are examples. You will have to simplest select to disable or rename the instructions that make sense for you. You’ll assessment the entire listing of instructions for your self and decide how they could be misused at

To disable a command, merely rename it to an empty string (signified by way of a couple of citation marks without a different characters between them), as proven beneath:

/and so on/redis/redis.conf

. . .
# It's also imaginable to fully kill a command by way of renaming it into
# an empty string:
rename-command FLUSHDB ""
rename-command FLUSHALL ""
rename-command DEBUG ""
. . .

To rename a command, give it every other identify as proven within the examples beneath. Renamed instructions will have to be tough for others to bet, however simple for you to bear in mind:

/and so on/redis/redis.conf

. . .
rename-command CONFIG ""
rename-command CONFIG ASC12_CONFIG
. . .

Save your adjustments and shut the record.

After renaming a command, observe the exchange by way of restarting Redis:

  • sudo systemctl restart redis.provider

To check the brand new command, input the Redis command line:

Subsequent, authenticate:



Let’s think that you simply renamed the CONFIG command to ASC12_CONFIG, as within the previous instance. First, take a look at utilizing the unique CONFIG command. It will have to fail, since you’ve renamed it:


(error) ERR unknown command 'config'

Calling the renamed command, on the other hand, can be a hit. It isn’t case-sensitive:

  • asc12_config get requirepass


1) "requirepass" 2) "your_redis_password"

After all, you’ll go out from redis-cli:

Notice that if you are already utilizing the Redis command line after which restart Redis, you’ll be able to want to re-authenticate. Differently, you’ll be able to get this mistake should you kind a command:


NOAUTH Authentication required.

In regards to the observe of renaming instructions, there is a cautionary observation on the finish of the SECURITY phase in /and so on/redis/redis.conf which reads:

Please be aware that converting the identify of instructions which might be logged into the AOF record or transmitted to slaves would possibly motive issues.

Notice: The Redis undertaking chooses to make use of the phrases “master” and “slave,” whilst DigitalOcean normally prefers the choices “primary” and “secondary.” In an effort to steer clear of confusion we’ve selected to make use of the phrases used within the Redis documentation right here.

That implies if the renamed command isn’t within the AOF record, or whether it is however the AOF record has no longer been transmitted to slaves, then there will have to be no drawback.

So, stay that during thoughts if you find yourself looking to rename instructions. The most productive time to rename a command is if you find yourself no longer utilizing AOF patience, or proper after set up, this is, prior to your Redis-using software has been deployed.

If you find yourself utilizing AOF and coping with a master-slave set up, believe this answer from the project’s GitHub issue page. The next is a respond to the creator’s query:

The instructions are logged to the AOF and replicated to the slave the similar means they’re despatched, so should you attempt to replay the AOF on an example that does not have the similar renaming, you might face inconsistencies because the command can’t be performed (identical for slaves).

Thus, one of the best ways to take care of renaming in circumstances like this is to ensure that renamed instructions are implemented to all circumstances in master-slave installations.


Remember that as soon as any person is logged in in your server, it is really easy to bypass the Redis-specific safety features now we have installed position. Due to this fact, a very powerful safety function is your firewall, which makes it extraordinarily tough for malicious actors to leap that fence.

If you are making an attempt to protected Redis conversation throughout an untrusted community you will have to make use of an SSL proxy, as advisable by way of Redis builders within the official Redis security guide.