This article covers a version of Ubuntu that is no longer supported. If you are currently operate a server running Ubuntu 12.04, we highly recommend upgrading or migrating to a supported version of Ubuntu:
Reason: Ubuntu 12.04 reached end of life (EOL) on April 28, 2017 and no longer receives security patches or updates. This guide is no longer maintained.
See Instead:
This guide might still be useful as a reference, but may not work on other Ubuntu releases. If available, we strongly recommend using a guide written for the version of Ubuntu you are using. You can use the search functionality at the top of the page to find a more recent version.
Wordpress is a free and open source website and blogging tool that uses php and MySQL. It was created in 2003 and has since then expanded to manage 22% of all the new websites created and has over 20,000 plugins to customize its functionality.
This tutorial covers installing Wordpress. Before you go through it, make sure your server is ready for Wordpress. You need root privileges (check out steps 3 and 4 for details): Initial Server Setup
You need to have nginx, MySQL, and PHP-FPM installed on your server: LEMP tutorial
Only once you have the user and required software should you proceed to install wordpress!
We can download Wordpress straight from their website:
wget http://wordpress.org/latest.tar.gz
This command will download the zipped wordpress package straight to your user's home directory. You can unzip it the the next line:
tar -xzvf latest.tar.gz
After we unzip the wordpress files, they will be in a directory called wordpress in the home directory on the virtual private server.
Now we need to switch gears for a moment and create a new MySQL directory for wordpress.
Go ahead and log into the MySQL Shell:
mysql -u root -p
Login using your MySQL root password, and then we need to create a wordpress database, a user in that database, and give that user a new password. Keep in mind that all MySQL commands must end with semi-colon.
First, let's make the database (I'm calling mine wordpress for simplicity's sake; feel free to give it whatever name you choose):
CREATE DATABASE wordpress; Query OK, 1 row affected (0.00 sec)
Then we need to create the new user. You can replace the database, name, and password, with whatever you prefer:
CREATE USER wordpressuser@localhost; Query OK, 0 rows affected (0.00 sec)
Set the password for your new user:
SET PASSWORD FOR wordpressuser@localhost= PASSWORD("password"); Query OK, 0 rows affected (0.00 sec)
Finish up by granting all privileges to the new user. Without this command, the wordpress installer will not be able to start up:
GRANT ALL PRIVILEGES ON wordpress.* TO wordpressuser@localhost IDENTIFIED BY 'password'; Query OK, 0 rows affected (0.00 sec)
Then refresh MySQL:
FLUSH PRIVILEGES; Query OK, 0 rows affected (0.00 sec)
Exit out of the MySQL shell:
exit
The first step to is to copy the sample WordPress configuration file, located in the WordPress directory, into a new file which we will edit, creating a new usable WordPress config:
cp ~/wordpress/wp-config-sample.php ~/wordpress/wp-config.php
Then open the wordpress config:
sudo nano ~/wordpress/wp-config.php
Find the section that contains the field below and substitute in the correct name for your database, username, and password:
// ** MySQL settings - You can get this info from your web host ** // /** The name of the database for WordPress */ define('DB_NAME', 'wordpress'); /** MySQL database username */ define('DB_USER', 'wordpressuser'); /** MySQL database password */ define('DB_PASSWORD', 'password');
Save and Exit.
We are almost done uploading Wordpress to the server. We need to create the directory where we will keep the wordpress files:
sudo mkdir -p /var/www
Transfer the unzipped WordPress files to the website's root directory.
sudo cp -r ~/wordpress/* /var/www
We can modify the permissions of /var/www to allow future automatic updating of Wordpress plugins and file editing with SFTP. If these steps aren't taken, you may get a "To perform the requested action, connection information is required" error message when attempting either task.
First, switch in to the web directory:
cd /var/www/
Give ownership of the directory to the nginx user, replacing the "username" with the name of your server user.
sudo chown www-data:www-data * -R sudo usermod -a -G www-data username
Now we need to set up the WordPress virtual host.
Create a new file for the for WordPress host, copying the format from the default configuration:
sudo cp /etc/nginx/sites-available/default /etc/nginx/sites-available/wordpress
Open the WordPress virtual host:
sudo nano /etc/nginx/sites-available/wordpress
The configuration should include the changes below (the details of the changes are under the config information):
server { listen 80; root /var/www; index index.php index.html index.htm; server_name 192.34.59.214; location / { try_files $uri $uri/ /index.php?q=$uri&$args; } error_page 404 /404.html; error_page 500 502 503 504 /50x.html; location = /50x.html { root /usr/share/nginx/www; } # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 location ~ \.php$ { try_files $uri =404; #fastcgi_pass 127.0.0.1:9000; # With php5-fpm: fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include fastcgi_params; } }
Here are the details of the changes:
Save and Exit that file.
Although all the configuration for worpress has been completed, we still need to activate the server block by creating a symbolic link:
sudo ln -s /etc/nginx/sites-available/wordpress /etc/nginx/sites-enabled/wordpress
Additionally, delete the default nginx server block.
sudo rm /etc/nginx/sites-enabled/default
Install php5-mysql:
sudo apt-get install php5-mysql
Then, as always, restart nginx and php-fpm:
sudo service nginx restart
sudo service php5-fpm restart
Once that is all done, the wordpress online installation page is up and waiting for you:
Access the page by visiting your site's domain or IP address (eg. example.com/wp-admin/install.php) and fill out the short online form (it should look like this).
Once Wordpress is installed, you have a strong base for building your site.
If you want to encrypt the information on your site, you can Install an SSL Certificate
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
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, I followed all steps, but when i do sudo service nginx restart, warn conflicting server name xxx.xxx.xx.xx on 0.0.0.0:80 ignored nginx. I am not able to access wordpress by keying in IP address on my browser. Any ideas?
This is because you have two server {} blocks that are both listening on the same IP and port.
In your case I’m guessing its either 0.0.0.0 and port 80 or you used the same servername twice which was your public facing IP.
If you remove one server block it will work.
Or if you want both active make sure they have different servernames and/or different ports.
After following these steps, I see “unable to connect to database” when viewing my WordPress site index. Could this be a permissions issue? (I installed WordPress not as root but as another super user.)
The error unable to connect to database indicates that a connection can not be established to the MySQL server which means it has not yet even had a chance to check if the provided credentials, user, pass, and db are valid.
The most common causes of this error are that MySQL is in fact not running, or there is a misconfiguration between the IP address you provided to wordpress to connect to and what IP/port MySQL is actually listening on.
By default MySQL will listen on all IPs and port 3306 so connecting to localhost and the default port in the wordpress configuration should be enough.
You can check to see if MySQL is runnning by either doing:
ps auxw | grep -i mysql
Or
telnet localhost 3306
The telnet command will attempt to connect to the IP and port that MySQL should be listening on. If the connection is established then its working, if it doesn’t then MySQL is most likely not started.
Thanks, raiyu. That’s been very helpful. I’ve rebooted the server and all’s well now. Very impressed with Digital Ocean and will be signing up.
I also had to tweak the permissions of /var/www in order to get WordPress automatic updates and plugin installs to work, using this line:
sudo chown -R www-data:www-data /var/www
Secondly, I’ve made this change to allow editing of files directly via SFTP if required:
sudo usermod -a -G www-data myusername sudo chmod -R g+rw /var/www
Are these worthwhile additions to the tutorial, or are there likely to be any problems caused by these changes?
Both changes are more or less ok, in terms of security you want to avoid having too many directories that are writeable by the user that the web server runs as because wordpress has had exploits in the past which would allow users to upload files directly to your system.
Keeping wordpress running on the latest version avoids the majority of those issues, however it is still something to keep in mind.
I’m going to have Etel run through this tutorial and see about getting the specified changes added to allow for automatic updates and plugin installs - its a good suggestion and should be noted.
We do go back through the tutorials as we get comments on them to make updates, so keep them coming!
Thanks
The only other tweak I’d suggest is to change this line in the location{} block of the virtual host file:
try_files $uri $uri/ /index.html;
to this instead, which enables WordPress’ pretty permalinks under Nginx:
try_files $uri $uri/ /index.php?q=$uri&$args;
You then just need to set the Permalink Settings in the WordPress dashboard to use the “Custom Structure” (the last option), with the relevant tags, for example:
/%postname%/
Thank you for the suggestion!
The configuration has been changed to facilitate Permalinks. :)
At Step Six i have this error: Sudo: In: command not found
Is it possible that you typed in In with “i” as the first letter of the command?
The command is actually ln with “L” as the first letter.
Let me know if the issue continues.