How To Install and Secure Memcached on Ubuntu 18.04

How To Install and Secure Memcached on Ubuntu 18.04


Memory object caching systems like Memcached can optimize back-end database performance by temporarily storing information in memory, retaining frequently or recently requested records. In this way, they reduce the number of direct requests to your databases.

Because systems like Memcached can contribute to denial of service attacks if improperly configured, it is important to secure your Memcached servers. In this guide, we will cover how to protect your Memcached server by binding your installation to a local or private network interface and creating an authorized user for your Memcached instance.


This tutorial assumes that you have a server set up with a non-root sudo user and a basic firewall. If that is not the case, set up the following:

With these prerequisites in place, you will be ready to install and secure your Memcached server.

Step 1 — Installing Memcached from the Official Repositories

If you don’t already have Memcached installed on your server, you can install it from the official Ubuntu repositories. First, make sure that your local package index is updated:

  1. sudo apt update

Next, install the official package as follows:

  1. sudo apt install memcached

We can also install libmemcached-tools, a library that provides several tools to work with your Memcached server:

  1. sudo apt install libmemcached-tools

Memcached should now be installed as a service on your server, along with tools that will allow you to test its connectivity. We can now move on to securing its configuration settings.

Step 2 — Securing Memcached Configuration Settings

To ensure that our Memcached instance is listening on the local interface, we will check the default setting in the configuration file located at /etc/memcached.conf. The current version of Memcached that ships with Ubuntu and Debian has the -l parameter set to the local interface, which prevents denial of service attacks from the network. We can inspect this setting to ensure that it is set correctly.

You can open /etc/memcached.conf with nano:

  1. sudo nano /etc/memcached.conf

To inspect the interface setting, find the following line in the file:

. . .
. . .

If you see the default setting of -l then there is no need to modify this line. If you do modify this setting to be more open, then it is also a good idea to also disable UDP, as it is more likely to be exploited in denial of service attacks. To disable UDP (while leaving TCP unaffected), add the following option to the bottom of this file:

. . .
-U 0

Save and close the file when you are done.

Restart your Memcached service to apply your changes:

  1. sudo systemctl restart memcached

Verify that Memcached is currently bound to the local interface and listening only for TCP connections by typing:

  1. sudo netstat -plunt

You should see the following output:

Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name . . . tcp 0 0* LISTEN 2279/memcached . . .

This confirms that memcached is bound to the address using only TCP.

Step 3 — Adding Authorized Users

To add authenticated users to your Memcached service, it is possible to use Simple Authentication and Security Layer (SASL), a framework that de-couples authentication procedures from application protocols. We will enable SASL within our Memcached configuration file and then move on to adding a user with authentication credentials.

Configuring SASL Support

We can first test the connectivity of our Memcached instance with the memcstat command. This will help us establish that SASL and user authentication are enabled after we make changes to our configuration files.

To check that Memcached is up and running, type the following:

  1. memcstat --servers=""

You should see output like the following:

Server: (11211) pid: 2279 uptime: 65 time: 1546620611 version: 1.5.6 . . .

Now we can move on to enabling SASL. First, we will add the -S parameter to /etc/memcached.conf. Open the file again:

  1. sudo nano /etc/memcached.conf

At the bottom of the file, add the following:

. . .

Next, find and uncomment the -vv option, which will provide verbose output to /var/log/memcached. The uncommented line should look like this:

. . .

Save and close the file.

Restart the Memcached service:

  1. sudo systemctl restart memcached

Next, we can take a look at the logs to be sure that SASL support has been enabled:

  1. sudo journalctl -u memcached

You should see the following line, indicating that SASL support has been initialized:

. . . Jan 04 16:51:12 memcached systemd-memcached-wrapper[2310]: Initialized SASL. . . .

We can check the connectivity again, but because SASL has been initialized, this command should fail without authentication:

  1. memcstat --servers=""

This command should not produce output. We can type the following to check its status:

  1. echo $?

$? will always return the exit code of the last command that exited. Typically, anything besides 0 indicates process failure. In this case, we should see an exit status of 1, which tells us that the memcstat command failed.

Adding an Authenticated User

Now we can download sasl2-bin, a package that contains administrative programs for the SASL user database. This will allow us to create our authenticated user:

  1. sudo apt install sasl2-bin

Next, we will create the directory and file that Memcached will check for its SASL configuration settings:

  1. sudo mkdir /etc/sasl2
  2. sudo nano /etc/sasl2/memcached.conf

Add the following to the SASL configuration file:

mech_list: plain
log_level: 5
sasldb_path: /etc/sasl2/memcached-sasldb2

In addition to specifying our logging level, we will set mech_list to plain, which tells Memcached that it should use its own password file and verify a plaintext password. We will also specify the path to the user database file that we will create next. Save and close the file when you are finished.

Now we will create a SASL database with our user credentials. We will use the saslpasswd2 command to make a new entry for our user in our database using the -c option. Our user will be sammy here, but you can replace this name with your own user. Using the -f option, we will specify the path to our database, which will be the path we set in /etc/sasl2/memcached.conf:

  1. sudo saslpasswd2 -a memcached -c -f /etc/sasl2/memcached-sasldb2 sammy

You will be asked to type and re-verify a password of your choosing.

Finally, we will give the memcache user ownership over the SASL database:

  1. sudo chown memcache:memcache /etc/sasl2/memcached-sasldb2

Restart the Memcached service:

  1. sudo systemctl restart memcached

Running memcstat again will confirm whether or not our authentication process worked. This time we will run it with our authentication credentials:

  1. memcstat --servers="" --username=sammy --password=your_password

You should see output like the following:

Server: (11211) pid: 2772 uptime: 31 time: 1546621072 version: 1.5.6 Ubuntu . . .

Our Memcached service is now successfully running with SASL support and user authentication.

Step 4 — Allowing Access Over the Private Network (Optional)

We have covered how to configure Memcached to listen on the local interface, which can prevent denial of service attacks by protecting the Memcached interface from exposure to outside parties. There may be instances where you will need to allow access from other servers, however. In this case, you can adjust your configuration settings to bind Memcached to the private network interface.

Note: We will cover how to configure firewall settings using UFW in this section, but it is also possible to use DigitalOcean Cloud Firewalls to create these settings. For more information on setting up DigitalOcean Cloud Firewalls, see our Introduction to DigitalOcean Cloud Firewalls. To learn more about how to limit incoming traffic to particular machines, check out the section of this tutorial on applying firewall rules using tags and server names and our discussion of firewall tags.

Limiting IP Access With Firewalls

Before you adjust your configuration settings, it is a good idea to set up firewall rules to limit the machines that can connect to your Memcached server. You will need to know the client server’s private IP address to configure your firewall rules. For more information about private networking on DigitalOcean, please see this overview of DigitalOcean private networking.

If you are using the UFW firewall, you can limit access to your Memcached instance by typing the following:

  1. sudo ufw allow from client_server_private_IP/32 to any port 11211

You can find out more about UFW firewalls by reading our ufw essentials guide.

With these changes in place, you can adjust the Memcached service to bind to your server’s private networking interface.

Binding Memcached to the Private Network Interface

Now that your firewall is in place, you can adjust the Memcached configuration to bind to your server’s private networking interface instead of

We can open the /etc/memcached.conf file again by typing:

  1. sudo nano /etc/memcached.conf

Inside, find the -l line that you checked or modified earlier, and change the address to match your server’s private networking interface:

. . .
-l memcached_server_private_IP
. . .

Save and close the file when you are finished.

Next, restart the Memcached service:

  1. sudo systemctl restart memcached

Check your new settings with netstat to confirm the change:

  1. sudo netstat -plunt
Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name . . . tcp 0 0 memcached_server_private_IP:11211* LISTEN 2912/memcached . . .

Test connectivity from your external client to ensure that you can still reach the service. It is a good idea to also check access from a non-authorized client to ensure that your firewall rules are effective.


In this tutorial, we have covered how to secure your Memcached server by configuring it to bind to your local or private network interface and by enabling SASL authentication.

To learn more about Memcached, check out the project documentation. For more information about how to work with Memcached, see our tutorial on How To Install and Use Memcache on Ubuntu 14.04.

Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.

Learn more about our products

About the authors

Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Hi. The identification process seems to be a bit ineffective, since, after creating an account after the sudo saslpasswd2 -a memcached -c -f /etc/sasl2/memcached-sasldb2 sammy (of course, i’ve changed the id), this is not taken into account and the memcstat --servers="" --username=sammy --password=your_password line stills don’t give an output.

Where is the mistake ?

If using -vv, you need to show how to use logrotate, or set a size limit for memcached.log.

Thanks for a great article. I was able to set up Memcached but I am not able to see it in my phpinfo(). Is there something I have to do to have Apache see that it’s available? Or am I missing something? T.i.a.


Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Join the Tech Talk
Success! Thank you! Please check your email for further details.

Please complete your information!

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel