[SOLVED] Help hosting Wordpress site in cloud

Habitual · 03-01-2014, 03:12 PM

Here's what I did:
installed. Debian 7.0.4 - No desktop. Web Server and mysql-server.

Code:

apache2 -version | head -1 && cat /var/www/index.html
Server version: Apache/2.2.22 (Debian)
<html><body><h1>It works!</h1>
<p>This is the default web page for this server.</p>
<p>The web server software is running but no content has been added, yet.</p>
</body></html>

cd /var/www
wget http://wordpress.org/latest.tar.gz
tar ztf latest.tar.gz

shows:
wordpress/ as the directory prefix, soooooooooooooooo....wishing to be of further help, I untar'd it and moved everything up one directory to /var/www and re-edited /etc/apache2/sites-enabled/000-default using:

Code:

DocumentRoot /var/www
...
                <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                DirectoryIndex index.php

and bounced apache again.
with

Code:

service apache2 restart

and voilá!
Wordpress at http://192.168.1.4/

Hope that's helpful.

JJ

Ryanms3030 · 03-01-2014, 05:02 PM

I solved it. Maybe not the most elegant solution but I just had to remove the index.html file in /var/www and restart apache. Now apache is looking at the index.php which is my wordpress site. I didn't actually remove the .html , just renamed. Thanks for all the help here, forced me to read up on some more stuff I didn't know about and learn.

Ryanms3030 · 03-01-2014, 05:04 PM

Quote:

Originally Posted by Habitual

Here's what I did:
installed. Debian 7.0.4 - No desktop. Web Server and mysql-server.

Code:

apache2 -version | head -1 && cat /var/www/index.html
Server version: Apache/2.2.22 (Debian)
<html><body><h1>It works!</h1>
<p>This is the default web page for this server.</p>
<p>The web server software is running but no content has been added, yet.</p>
</body></html>

cd /var/www
wget http://wordpress.org/latest.tar.gz
tar ztf latest.tar.gz

shows:
wordpress/ as the directory prefix, soooooooooooooooo....wishing to be of further help, I untar'd it and moved everything up one directory to /var/www and re-edited /etc/apache2/sites-enabled/000-default using:

Code:

DocumentRoot /var/www
...
                <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                DirectoryIndex index.php

and bounced apache again.
with

Code:

service apache2 restart

and voilá!
Wordpress at http://192.168.1.4/

Hope that's helpful.

JJ

Thanks! That is helpfull as that is probably more elegant than my solution. It all will help when I eventually want to host two sites on the same server, which I will want to do

Habitual · 03-01-2014, 05:34 PM

Quote:

Originally Posted by Ryanms3030

I solved it. ... I just had to remove the index.html file in /var/www and restart apache. Now apache is looking at the index.php which is my wordpress site. I didn't actually remove the .html , just renamed.

Great.

3 ways to correct this issue:
rename or remove /var/www/index.html or an explicit DirectoryIndex directive (that's my personal preference)

Code:

DirectoryIndex index.php

or
http://192.168.1.4/index.php would have "worked" also.

Apparently, there is an order of preference to

Code:

DirectoryIndex index.html index.php

which I did not realize.

Glad it worked out.

Habitual · 03-01-2014, 05:48 PM

Quote:

Originally Posted by Ryanms3030

I decided to blow way this server and rebuild it with Debian 7 since that is what I'm running on my home server.

I installed and configured lamp, owncloud and wordpress and I'm at the same place. Wordpress works fine in the admin dashboard but when I got to my domain I get "it works"

To be fair, it was a waste of time, but not so much mine as yours.
Re-installing an OS to "fix" or correct a trivial issue such as this is never an answer.
DocumentRoot was not the issue as was the DirectoryIndex directive apparently has an order of precedence.

20 years and I'm still learning.
Sorry about the 'tude'.

Peace.
JJ

frankbell · 03-01-2014, 08:18 PM

Quote:

I didn't actually remove the .html , just renamed.

I think that is wise. If something happens and your WordPress has a bad day, it's handy to have an index page you can quickly edit appropriately, rename, and put into play while you go troubleshooting.