Wordpress repeatedly gives "Error establishing database connection" inspite of having JetPack enabled


I have recently installed Wordpress, and as per the instructions here have installed jetpack.

In the “Enter the IPv4 or IPv6 addresses that you want to white list and click the Save button to update the Protect white list.” i have added the droplet IP and clicked on save. Is that correct? After this, i have restarted apache as well as restarted the droplet just to be sure.

But something seems amiss, since the “Error establishing database connection” keeps recurring.

My droplet config: 1 GB Memory / 30 GB Disk / NYC3 - Ubuntu WordPress on 14.04

Please help.

Submit an answer

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!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hello, all

This crash is most likely due to your system running out of memory. I’d suggest that you add a swap file to give yourself a bit more of a buffer. Check out this tutorial:

How To Add Swap on Ubuntu

You will most definitely need to upgrade your droplet as you’re running out of memory and your application/website needs more resources in order to continue to operate.

What you can also do is to use the MySQLTuner script.

The MySQLTuner is a script written in Perl and allows you to quickly test your MySQL configuration and it gives you suggestions for adjustments to increase performance and stability.

According to the official GitHub page, it supports 300 indicators for MySQL/MariaDB/Percona Server in this last version.

To run the script you could do the following:

  • SSH to your Droplet
  • Download the script:
wget -O
  • Then execute it:

The script would run multiple checks against your MySQL instance, all checks done by MySQLTuner are documented here.

Also as stated in the official documentation, it is still extremely important for you to fully understand each change you make to a MySQL database server. If you don’t understand portions of the script’s output, or if you don’t understand the recommendations, you should consult a knowledgeable DBA or system administrator that you trust.

As a good practice make sure to always test your changes on staging environments before implementing them on your production database.

On the same note, if you want to have a worry-free MySQL hosting and focus on your application, I would recommend trying out the DigitalOcean Managed Databases:

This was mini tutorial was posted from bobbyiliev in this question in our community:

You can also create a simple bash script to check if MySQL is running and if not to restart it.


# Check if MySQL is running
sudo service mysql status > /dev/null 2>&1

# Restart the MySQL service if it's not running.
if [ $? != 0 ]; then
    sudo service mysql restart

Run this script every 5 minutes using a cron job like this one:

 */5 * * * * /home/user/scripts/ > /dev/null 2>&1

Hope that this helps! Regards, Alex

Jetpack doesn’t block XML-RPC traffic as it uses XML-RPC itself. The protect module of Jetpack detects brute force attacks from the common XML-RPC attack vector. Jetpack will then prevent 90% of the database queries and reduce the load on MySQL. However, it’s still possible for enough XML-RPC attack traffic to exhaust MySQL’s resources.

If you are not using Jetpack for anything else, I would recommend using the other methods mentioned in the link from your question. If Jetpack is essential for you, I have seen WordPress plugins that place a hard block on XML-RPC traffic, but whitelist Automattic’s IP ranges so Jetpack continues to function.

I hope this helps!