{"id":1446,"date":"2011-08-21T22:03:04","date_gmt":"2011-08-21T21:03:04","guid":{"rendered":"http:\/\/www.haydnwilliams.com\/blog\/?p=1446"},"modified":"2022-04-11T21:34:01","modified_gmt":"2022-04-11T20:34:01","slug":"uhs5-lamp-web-server-wordpress","status":"publish","type":"post","link":"https:\/\/www.haydnwilliams.com\/blog\/uhs5-lamp-web-server-wordpress\/","title":{"rendered":"UHS5 – LAMP web server + WordPress"},"content":{"rendered":"

The process is covered in quite a lot of good detail<\/a> in the Ubuntu Documentation, but I’ve summarised the main steps below for those who just want to get up and running with the basics.<\/p>\n

Apache<\/h2>\n

We can again use apt-get, this time to install Apache HTTP server<\/a>. It’s version 2 which is available now, hence the command is:<\/p>\n

sudo apt-get install apache2<\/pre>\n
The marvellous apt-get takes care of installing all dependancies too, so anything else we might need to run apache just gets added without us having to worry about it. Once the install process is finished, navigate to http:\/\/localhost<\/a> and make sure that you can see the default Apache page.<\/p>\n
To make the pages visible from other machines on the local network, you’ll need to edit \/etc\/apache2\/sites-available\/default<\/strong>.\u00a0Find the line:<\/p>\n
Allow from 127.0.0.0\/255.0.0.0 ::1\/128<\/pre>\n
and add the IP addresses of other local machines onto the end. Although all our PCs have static IP addresses, I used a wildcard so that things like my iPhone and visiting friend’s PCs can also access the server. I therefore changed the line from the above to:<\/p>\n
Allow from 127.0.0.0\/255.0.0.0 ::1\/128 192.168.1.*<\/pre>\n
The pages served by default, in my case at least, were stored in \/var\/www<\/strong>. If you want to run more than one website through Apache, a guide on zaphu.com<\/a> describes how to add a new site and activate it.<\/p>\n
PHP<\/h2>\n
PHP<\/a> is pretty easy to install:<\/p>\n
sudo apt-get install php5<\/pre>\n
That’s it! The system will probably re-start Apache for you at the appropriate places, but if you want to check whether it’s successfully integrated PHP5 support into Apache, then running the following will give you an answer as to whether or not the relevant module has been enabled:<\/p>\n
>sudo\u00a0a2enmod\u00a0php5<\/pre>\n
MySQL<\/h2>\n
To install MySQL<\/a>, just run:<\/p>\n
sudo apt-get install mysql-client mysql-server<\/pre>\n
During the setup procedure, you’ll be asked to choose a password for the ‘root’ account. Once that’s installed, ensure you’ve got support for MySQL in PHP:<\/p>\n
sudo apt-get install php5-mysql<\/pre>\n
And finally, if you want a GUI admin tool, then MySQL Administrator does a fine job (although it seems to have been replaced by MySQL Workbench<\/a> now, but I couldn’t find that using apt-get), or you can use PHPMyAdmin<\/a> to do it in your browser:<\/p>\n
sudo apt-get install mysql-admin sudo apt-get install phpmyadmin<\/pre>\n
If you want to check the server’s working OK, log in to it using the root account we set up during installation:<\/p>\n
mysql -u root -p<\/pre>\n
Obviously the next thing you’ll do is set about creating a new user account and locking down the ‘root’ account, right? Good, I thought so.<\/p>\n
WordPress<\/strong><\/h2>\n
You can > Download” href=”http:\/\/wordpress.org\/download\/” target=”_blank”>download<\/a> the WordPress<\/a> installation files and manually unpack them if you want, but I chose to install by checking out the latest stable version from the WordPress repository using Subversion. This will make it very easy to upgrade in future, by just ‘switching’ to the newest tag release. Note that this assumes you’ve already installed Subversion on your system – if not, please see my post detailing this first. Installing WordPress in this manner is something else that’s incredibly easy – just one command. Make sure you run this command from whatever directory you want WordPress to be installed into – apache2 sets the default web directory to be \/var\/www<\/strong>, so I’d suggest starting there. The command to checkout (“co”) a specific version of WordPress (3.1.3 in this case) is:<\/p>\n
sudo svn co http:\/\/core.svn.wordpress.org\/tags\/3.1.3 .<\/pre>\n
Note the trailing full-stop, which specifies that the files should be checked out to the current directory. This whole process is discussed in more depth in the relevant page<\/a> of the official WordPress.org documentation. Once you’ve installed the actual files, you’ll need to set up a database for WordPress to use. I’d include the command here but unfortunately each time I type it in, my WordPress installation thinks I’m trying a SQL injection attack and I get locked out of my own domain! There’s plenty of documentation out and about which covers this though. Set up a user for the blog too, which has the necessary permissions to work with the database you’ve created. Finally, copy wp-config-sample.php<\/strong> to a new file called wp-config.php<\/strong> and set up the values as required. You can view the site by navigating to http:\/\/localhost<\/a> and answering a couple of questions to complete the installation, but don’t forget to change the “WordPress URL” in the settings screen to something like “http:\/\/myshinynewserver”, otherwise you may find that the site is served up with references to “localhost” in, instead of your server. After that, you should be good to go. Except, that is, if you’re afflicted by…<\/p>\n
The WordPress Blank Screen of Death<\/span><\/h3>\n
I carried out all the steps above, but when I tried to view my shiny new blog, all I got was a blank page. The HTML source for the page was blank too. There are hundreds of different<\/a> explanations<\/a>, articles<\/a> and blog<\/a> posts<\/a> which offer advice on how to rectify it. None of them worked for me. I did however, find that in my case there was a very simple solution. I enabled debugging in WordPress by adding the following line to wp-config.php<\/strong>:<\/p>\n
define('WP_DEBUG', true);<\/pre>\n
This gave me the following message when I checked the subsequent output in \/var\/log\/apache2\/error.log<\/strong>:<\/p>\n
 [error] [client 127.0.0.1] PHP Parse error:\u00a0 syntax error, unexpected ':' in \/var\/www\/wp-config.php on line 25<\/pre>\n
Line 25 is the line which contains the password for the relevant MySQL database. All of my passwords are generated by the GRC Ultra High Security Password Generator<\/a>, and include symbols. This didn’t pose any problems when I set up the user account with MySQL Administrator, but it did include a colon which was enough to completely confuse PHP. This was preventing the system connecting to the database and causing the blank screen of death. I amended the password so it didn’t contain a colon any more, and suddenly everything instantly worked again. Once you’ve found your error, don’t forget to turn debugging off again.<\/p>\n","protected":false},"excerpt":{"rendered":"
The process is covered in quite a lot of good...<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[606,607,605,164,608,647,646,249,645,644,651,652,653,649,648,650,654],"class_list":["post-1446","post","type-post","status-publish","format-standard","hentry","category-it","tag-apache","tag-apache2","tag-home-server","tag-lamp","tag-mysql","tag-mysql-administrator","tag-mysql-workbench","tag-php","tag-screen-of-death","tag-wordpress","tag-wordpress-blank-screen","tag-wordpress-blank-screen-of-death","tag-wordpress-no-source","tag-wordpress-respository","tag-wordpress-subversion","tag-wordpress-svn","tag-wordpress-white-page"],"_links":{"self":[{"href":"https:\/\/www.haydnwilliams.com\/blog\/wp-json\/wp\/v2\/posts\/1446","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.haydnwilliams.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.haydnwilliams.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.haydnwilliams.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.haydnwilliams.com\/blog\/wp-json\/wp\/v2\/comments?post=1446"}],"version-history":[{"count":0,"href":"https:\/\/www.haydnwilliams.com\/blog\/wp-json\/wp\/v2\/posts\/1446\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.haydnwilliams.com\/blog\/wp-json\/wp\/v2\/media?parent=1446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.haydnwilliams.com\/blog\/wp-json\/wp\/v2\/categories?post=1446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.haydnwilliams.com\/blog\/wp-json\/wp\/v2\/tags?post=1446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}