Still not fixed.

I did a ground-up uninstall and reinstall of all the components of the LAMP stack:

Uninstall
1) yum remove httpd (preserved my httpd.conf file in the /etc/httpd/conf directory, deleting everything else)
2) yum remove mysql
3) yum remove php
4) deleted everything out of /var/www/html

This puts the server back to its fresh install situation before I ever added any packages. This is a brand new RedHat Enterprise Linux install with nothing else running on it.

Install
1) yum install httpd
2) yum install -y mysql mysql-server
3) yum install -y php php-mysql
4) Copied wordpress files to /var/www/html, which is the DocumentRoot setting in my httpd.conf file, ensuring that chown -R apache:apache and chmod -R 755 on everything, including html directory
5) Restored /etc/httpd/conf/httpd.conf from backup
6) Started httpd using /sbin/service httpd start. It starts with zero errors. All ok.

I type in http:// followed by the IP address currently standing in for my domain name (as yet undetermined). Earlier in our discussion thread, I used to get the wordpress install script. Now I just get the Apache server test page for RedHat Linux. If I put index.html with “

It Works!

” into /var/www/html, then I see that. If I remove the index.html, I still don’t see the install script starting up. Just that Apache RHEL default test page.

But, if I add /wp-admin to my URL, it DOES go into the install script. That was something I didn’t have to do before. But at least I’m getting this far. So I go through the install and get into the Dashboard.

I immediately go to the Permalinks menu and switch to a different scheme so as to generate the .htaccess file. That works just fine. I then immediately go to test the home page. Nothing but a 404. Earlier in this thread, I at least got the home page when none of the other links worked. Now that doesn’t even work.

This really sucks. I can’t figure out what’s wrong because this server is exactly like other servers our hosting provider has given us for the same thing, and those all work fine. They don’t troubleshoot WordPress installs because, well, they just don’t. Their business is server hosting. The app level is up to the customer.

What did I miss? How could this time through (the same as the first, second, third, and fourth time through) of the install have resulted in something so different?

Thanks.