Thanks, mercime. But when I add in “/wordpress/” in front of “/members/…”, I still get 404.

http://xxx.xxx.xx.xxx/wordpress/ also returns a 404. But http://xxx.xxx.xx.xxx/ returns the buddypress-enabled home page, fully themed and functional, except for the fact that clicking any deeper part of the admin menus returns 404.

My apache virtualhost settings are as follows:

`
ServerAdmin webmaster @xxx.xxx.xx.xxx
DocumentRoot /data01/home/username/production/wordpress
ServerName xxx.xxx.xx.xxx
ErrorLog logs/xxx.xxx.xx.xxx-error_log
CustomLog logs/xxx.xxx.xx.xxx-access_log common
`

Does anything need to change there to fix this problem?

As an experiment, I changed “wordpress” in the documentroot path to “wp”. Restarted apache. Still, the home page loads beautifully, yet every link in the site (buddypress link or blog post link) leads to 404. Totally confused here. Never had this happen before after many, many installs.

# There are lots of WordPress hacks designed to take the contents of your wp-config
# file (username and password) and dump them to a text file a spambot can pickup and
# send to a hacker. If you block access to wp-config file in your .htaccess using
# this method, you block those hackers from getting your database login information.
Order deny,allow
deny from all

# Turn off directory indexing to keep anyone from seeing the contents of a directory
# if there is no index file.
Options All -Indexes

# Block known spambots and crawlers. Update the following section with newly discovered
# spambots and crawlers. This blocks them from ripping off posts and images (costing
# bandwidth in the process.
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_USER_AGENT} ^BlackWidow [OR]
RewriteCond %{HTTP_USER_AGENT} ^Bot mailto:craftbot @yahoo.com [OR]
RewriteCond %{HTTP_USER_AGENT} ^ChinaClaw [OR]
RewriteCond %{HTTP_USER_AGENT} ^Custo [OR]
RewriteCond %{HTTP_USER_AGENT} ^DISCo [OR]
RewriteCond %{HTTP_USER_AGENT} ^Download Demon [OR]
RewriteCond %{HTTP_USER_AGENT} ^eCatch [OR]
RewriteCond %{HTTP_USER_AGENT} ^EirGrabber [OR]
RewriteCond %{HTTP_USER_AGENT} ^EmailSiphon [OR]
RewriteCond %{HTTP_USER_AGENT} ^EmailWolf [OR]
RewriteCond %{HTTP_USER_AGENT} ^Express WebPictures [OR]
RewriteCond %{HTTP_USER_AGENT} ^ExtractorPro [OR]
RewriteCond %{HTTP_USER_AGENT} ^EyeNetIE [OR]
RewriteCond %{HTTP_USER_AGENT} ^FlashGet [OR]
RewriteCond %{HTTP_USER_AGENT} ^GetRight [OR]
RewriteCond %{HTTP_USER_AGENT} ^GetWeb! [OR]
RewriteCond %{HTTP_USER_AGENT} ^Go!Zilla [OR]
RewriteCond %{HTTP_USER_AGENT} ^Go-Ahead-Got-It [OR]
RewriteCond %{HTTP_USER_AGENT} ^GrabNet [OR]
RewriteCond %{HTTP_USER_AGENT} ^Grafula [OR]
RewriteCond %{HTTP_USER_AGENT} ^HMView [OR]
RewriteCond %{HTTP_USER_AGENT} HTTrack [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^Image Stripper [OR]
RewriteCond %{HTTP_USER_AGENT} ^Image Sucker [OR]
RewriteCond %{HTTP_USER_AGENT} Indy Library [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^InterGET [OR]
RewriteCond %{HTTP_USER_AGENT} ^Internet Ninja [OR]
RewriteCond %{HTTP_USER_AGENT} ^JetCar [OR]
RewriteCond %{HTTP_USER_AGENT} ^JOC Web Spider [OR]
RewriteCond %{HTTP_USER_AGENT} ^larbin [OR]
RewriteCond %{HTTP_USER_AGENT} ^LeechFTP [OR]
RewriteCond %{HTTP_USER_AGENT} ^Mass Downloader [OR]
RewriteCond %{HTTP_USER_AGENT} ^MIDown tool [OR]
RewriteCond %{HTTP_USER_AGENT} ^Mister PiX [OR]
RewriteCond %{HTTP_USER_AGENT} ^Navroad [OR]
RewriteCond %{HTTP_USER_AGENT} ^NearSite [OR]
RewriteCond %{HTTP_USER_AGENT} ^NetAnts [OR]
RewriteCond %{HTTP_USER_AGENT} ^NetSpider [OR]
RewriteCond %{HTTP_USER_AGENT} ^Net Vampire [OR]
RewriteCond %{HTTP_USER_AGENT} ^NetZIP [OR]
RewriteCond %{HTTP_USER_AGENT} ^Octopus [OR]

RewriteCond %{HTTP_USER_AGENT} ^Offline Explorer [OR]
RewriteCond %{HTTP_USER_AGENT} ^Offline Navigator [OR]
RewriteCond %{HTTP_USER_AGENT} ^PageGrabber [OR]
RewriteCond %{HTTP_USER_AGENT} ^Papa Foto [OR]
RewriteCond %{HTTP_USER_AGENT} ^pavuk [OR]
RewriteCond %{HTTP_USER_AGENT} ^pcBrowser [OR]
RewriteCond %{HTTP_USER_AGENT} ^RealDownload [OR]
RewriteCond %{HTTP_USER_AGENT} ^ReGet [OR]
RewriteCond %{HTTP_USER_AGENT} ^SiteSnagger [OR]
RewriteCond %{HTTP_USER_AGENT} ^SmartDownload [OR]
RewriteCond %{HTTP_USER_AGENT} ^SuperBot [OR]
RewriteCond %{HTTP_USER_AGENT} ^SuperHTTP [OR]
RewriteCond %{HTTP_USER_AGENT} ^Surfbot [OR]
RewriteCond %{HTTP_USER_AGENT} ^tAkeOut [OR]
RewriteCond %{HTTP_USER_AGENT} ^Teleport Pro [OR]
RewriteCond %{HTTP_USER_AGENT} ^VoidEYE [OR]
RewriteCond %{HTTP_USER_AGENT} ^Web Image Collector [OR]
RewriteCond %{HTTP_USER_AGENT} ^Web Sucker [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebAuto [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebCopier [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebFetch [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebGo IS [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebLeacher [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebReaper [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebSauger [OR]
RewriteCond %{HTTP_USER_AGENT} ^Website eXtractor [OR]
RewriteCond %{HTTP_USER_AGENT} ^Website Quester [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebStripper [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebWhacker [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebZIP [OR]
RewriteCond %{HTTP_USER_AGENT} ^Wget [OR]
RewriteCond %{HTTP_USER_AGENT} ^Widow [OR]
RewriteCond %{HTTP_USER_AGENT} ^WWWOFFLE [OR]
RewriteCond %{HTTP_USER_AGENT} ^Xaldon WebSpider [OR]
RewriteCond %{HTTP_USER_AGENT} ^Zeus
RewriteRule ^.* – [F,L]

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

Andrea_r: Thanks. So I commented out the current AllowOverride None directive and added AllowOverride FileInfo Options, like this:

`# First, we configure the “default” to be a very restrictive set of
# features.
#

Options FollowSymLinks
#AllowOverride None
AllowOverride FileInfo Options
`

Then I restarted httpd. Now I get 500 internal server error. Is there another place I should be putting AllowOverride FileInfo Options instead?

Here are example lines from my error log and access log (IP numbers obfuscated for security):

Error log:
`[Tue Mar 08 14:25:49 2011] [error] [client 123.456.789.0] File does not exist: /data01/home/username/production/wp/members, referer: http://098.765.43.210/`

Access log:
`123.456.789.0 – – [08/Mar/2011:14:25:49 +0000] “GET /members/admin/profile/ HTTP/1.1” 404 300`

With Permalinks set to “Month and Name”, a hit to the hello world blog post for this install generates the following error and access log entries:

Error log:
`[Tue Mar 08 14:38:48 2011] [error] [client 123.456.789.0] File does not exist: /data01/home/username/production/wp/2011, referer: http://098.765.43.210/`

Access log:
`123.456.789.0 – – [08/Mar/2011:14:38:48 +0000] “GET /2011/03/hello-world/ HTTP/1.1” 404 298`

Setting the Permalinks to “Day and Name” gives this:

Error log:
`[Tue Mar 08 14:35:02 2011] [error] [client 123.456.789.0] File does not exist: /data01/home/username/production/wp/2011, referer: http://098.765.43.210/`

Access log:
`123.456.789.0 – – [08/Mar/2011:14:35:02 +0000] “GET /2011/03/05/hello-world/ HTTP/1.1” 404 301`

Ok, I did finally realize that my problem of getting nothing at http://ip.address… was because I my index.php file went missing.

Duh.

But, despite the permalink update and correctly generated .htaccess file, I still don’t have access to posts and pages. Just the home page. BuddyPress isn’t installed yet. This is just the base WP 3.1 install.