That does looks like an Apache issue…
You might try this Google search result
Hope that helps!
It’s certainly an Apache error message, but why’s it happening??
The directory has the same permissions as ones that are ok:
drwxr-xr-x 6 test users 4.0K May 11 22:37 wp-content
drwxr-xr-x 9 test users 4.0K May 4 12:56 wp-includes
drwxr-xr-x 2 test users 4.0K May 11 22:42 wp-snapshots
The files have the same permissions as ones that are ok:
drwxr-xr-x 2 test users 4.0K May 11 22:42 .
drwxr-xr-x 6 test users 4.0K May 11 22:37 ..
-rw-r--r-- 1 test users 633K May 11 22:37 518ec8460ccb39117_20130511_testsite_database.sql
-rw-r--r-- 1 test users 349K May 11 22:38 518ec8460ccb39117_20130511_testsite_installer.php
-rw-r--r-- 1 test users 4.2K May 11 22:38 518ec8460ccb39117_20130511_testsite.log
-rw-r--r-- 1 test users 13M May 11 22:38 518ec8460ccb39117_20130511_testsite_package.zip
-rw-r--r-- 1 test users 212 May 11 22:37 dtoken.php
-rw-r--r-- 1 test users 212 May 11 22:37 index.php
-rw-r--r-- 1 test users 39 May 11 22:37 robots.txt
(.htaccess deleted)
ls -lha wp-content/uploads/2011/09/
drwxr-xr-x 2 test users 4.0K Sep 26 2011 .
drwxr-xr-x 4 test users 4.0K Dec 25 2011 ..
-rw-r--r-- 1 test users 5.2K Sep 26 2011 a.jpg
-rw-r--r-- 1 test users 12K Sep 26 2011 b.jpg
etc..
If I create a simple text file in wp-snapshots, I get the same 403 error, but it works in wp-content.
So it’s something related to this directory, but I cannot see what.
I am running suPHP, and this was creating the package files to be only readable by the user, not group or anyone. But changing that so that they are doesn’t help either.
Ah ha, it’s suPHP – as I said, it was creating files with 0600 permissions. I changed all of them..
.. except .htaccess
If that’s not readable by Apache, it does a 403.
This suggests doing a chmod 0644 on .htaccess after you create it would be a good idea 🙂
Ah nice catch…
I’ll update that on the next version…