How To Install Wordpress with nginx on Ubuntu 12.04

I am getting this error while making databse user ERROR 1819 (HY000): Your password does not satisfy the current policy requirements I am logged in using the password i set earlier.

I followed all steps but my css and javascript aren’t loading here is the console log

 Uncaught SyntaxError: Unexpected token <
install.php:114 Uncaught ReferenceError: jQuery is not defined

Thanks for the guide - works nicely. I ave a problem similar to one mentioned before with permalinks - for some reason Nginx is only showing the root and the admin panel - anything else gets the 404… Instaling nginx helper plugin did not resolve this

Thanks, Shai

I have followed Step 5 “to allow future automatic updating of Wordpress plugins” with

cd /var/www sudo chown www-data:www-data * -R sudo usermod -a -G www-data myusername

but I still get the “To perform the requested action, connection information is required” error message when I click the Update button from within Wordpress. I then tried

sudo chmod -R g+w *

to attempt to give myusername group write permission. But that failed. I temporarily had to

sudo chmod -R go+w

which finally allowed the automatic update to occur without error.

But I don’t want to expose the Wordpress files to be world writable just to permit automatic updating. What am I missing?

You failed to mention to install php5-gd. WordPress depends on either the GD library or imagemagick to do photo editing and manipulation. You should include this in the tutorial.

We can modify the permissions of /var/www to allow future automatic updating of Wordpress plugins and file editing with SFTP

This is exactly what I want. But does it have to be in /var/www/? My understanding is that for multi-site hosting on Debian, so presumably Ubuntu too, the default directory for web site files and directories is /srv/.

I would like to retain the ability to host non-WP sites on the same droplet, besides which any WP sites I host are likely to be so different as to make a multi-site WP installation impractical. Is this tutorial for single site droplets or do we simply treat WP sites differently?

So can I set a WP site up in the standard way, e.g. /srv/mydomain.tld/public/ where htdocs is the name of the WP installation and the permissions there will affect whether or not updates will be automatic?

Alternatively, can simlinks be used to create the same effect? i.e. put the site in /srv and simlink to it from /var/www

Thank you for sharing this information. I have a question. i purchased a theme but there is no style sheet. Now, there is a any way to fix this problem.

Hi,

I was trying to set-up 3 separate WordPress instances on a Single VPS (Not to get confused with MultiSite)

Each Instance will have their own domain name.

After following all the steps in this tutorial (I didn’t receive any error message) and successfully completed them, now when I try to navigate to my server i.e. http://128.199.143.37/

I see "Welcome to nginx ! " page, instead of WordPress Install Page.

Below are the steps which I have performed. Please do let me know what I have done wrong or is anything missing.

Appreciate all your help !

Thanks in Advance !

==================================================================================

wget http://wordpress.org/latest.tar.gz tar xzvf latest.tar.gz

==================================================================================

mysql -u root -p

CREATE DATABASE FirstSite; CREATE DATABASE SecondSite; CREATE DATABASE ThirdSite;

CREATE USER firstadmin@localhost; CREATE USER secondadmin@localhost; CREATE USER thirdadmin@localhost;

SET PASSWORD FOR firstadmin@localhost= PASSWORD(“password”); SET PASSWORD FOR secondadmin@localhost= PASSWORD(“password”); SET PASSWORD FOR thirdadmin@localhost= PASSWORD(“password”);

GRANT ALL PRIVILEGES ON FirstSite.* TO firstadmin@localhost IDENTIFIED BY ‘password’; GRANT ALL PRIVILEGES ON SecondSite.* TO secondadmin@localhost IDENTIFIED BY ‘password’; GRANT ALL PRIVILEGES ON ThirdSite.* TO thirdadmin@localhost IDENTIFIED BY ‘password’;

FLUSH PRIVILEGES;

exit

==================================================================================

sudo mkdir -p /var/www cd /var/www

sudo mkdir FirstSite sudo mkdir SecondSite sudo mkdir ThirdSite

cp ~/wordpress/wp-config-sample.php ~/wordpress/wp-config.php

sudo rsync -avP ~/wordpress/ /var/www/FirstSite/ sudo rsync -avP ~/wordpress/ /var/www/SecondSite/ sudo rsync -avP ~/wordpress/ /var/www/ThirdSite/

sudo chown www-data:www-data * -R sudo usermod -a -G www-data admin

==================================================================================

cd /var/www/FirstSite

sudo nano wp-config.php

// ** MySQL settings - You can get this info from your web host ** // /** The name of the database for WordPress */ define(‘DB_NAME’, ‘FirstSite’);

/** MySQL database username */ define(‘DB_USER’, ‘firstadmin’);

/** MySQL database password */ define(‘DB_PASSWORD’, ‘password’);

==================================================================================

cd /var/www/SecondSite

sudo nano wp-config.php

// ** MySQL settings - You can get this info from your web host ** // /** The name of the database for WordPress */ define(‘DB_NAME’, ‘SecondSite’);

/** MySQL database username */ define(‘DB_USER’, ‘secondadmin’);

/** MySQL database password */ define(‘DB_PASSWORD’, ‘password’);

==================================================================================

cd /var/www/ThirdSite

sudo nano wp-config.php

// ** MySQL settings - You can get this info from your web host ** // /** The name of the database for WordPress */ define(‘DB_NAME’, ‘ThirdSite’);

/** MySQL database username */ define(‘DB_USER’, ‘thirdadmin’);

/** MySQL database password */ define(‘DB_PASSWORD’, ‘password’);

==================================================================================

sudo cd /etc/nginx/sites-available

sudo cp default FirstSite sudo cp default SecondSite sudo cp default ThirdSite

edit each of the above file and change the following information as listed below

Change the root to /var/www/ Add index.php to the index line. Change the server_name from local host to your domain name or IP address. Change the “try_files $uri $uri/ /index.html;” line to “try_files $uri $uri/ /index.php?q=$uri&$args;” to enable Wordpress Permalinks with nginx. Uncomment the correct lines in “location ~ .php$ {“ section.

Save and Exit that file.

sudo nano /etc/nginx/sites-available/FirstSite

server { listen 80;

    root /var/www;
    index index.php index.html index.htm;

    server_name 128.199.143.37;

    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;
             }

}

sudo nano /etc/nginx/sites-available/SecondSite

server { listen 80;

    root /var/www;
    index index.php index.html index.htm;

    server_name 128.199.143.37;

    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;
             }

}

sudo nano /etc/nginx/sites-available/ThirdSite

server { listen 80;

    root /var/www;
    index index.php index.html index.htm;

    server_name 128.199.143.37;

    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;
             }

}

==================================================================================

sudo ln -s /etc/nginx/sites-available/FirstSite /etc/nginx/sites-enabled/FirstSite sudo ln -s /etc/nginx/sites-available/SecondSite /etc/nginx/sites-enabled/SecondSite sudo ln -s /etc/nginx/sites-available/ThirdSite /etc/nginx/sites-enabled/ThirdSite

sudo mv /etc/nginx/sites-enabled/default /etc/nginx/sites-enabled/default.bak

sudo apt-get install php5-mysql

sudo service nginx restart

sudo service php5-fpm restart

==================================================================================

http://128.199.143.37

BACKGROUND So I’ve spent the better part of the past few weeks creating and destroying and creating and destroying droplets trying to follow DO’s LEMP tutorials in hopes that changing servers from a managed wordpress one to this one would get rid of a Bad Request error my client’s website has been getting.

THE PROBLEM I’ve gotten Wordpress installed on the new LEMP droplet according to the files list (ls) but trying to go to any wordpress pages give a 404. I went back and installed PHPMyAdmin and it shows that there’s a database called ‘wordpress’ and it says “No tables found in database”. Help?

I’ve tried restarting php5-fpm and nginx. Going to the IP address (which is what I’ve put instead of www.example.com in the config files) alone gives me the “Welcome to nginx” page. phpinfo finally works and gives me a bunch of info but I’m not sure how helpful that is.

Any help would be greatly appreciated! I really need to get this working… Thanks!

@mattlucas: You need to run it as root:

sudo visudo