I don’t use MU and I can’t test this right now but…
If you started with a fresh 3.8.1, then your .htaccess
file should look like this (per the Codex):
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*\.php)$ wp/$1 [L]
RewriteRule . index.php [L]
Your .htaccess
doesn’t match, notably this line:
RewriteRule ^.*/files/(.+) wp-includes/ms-files.php?file=$1 [L]
That line is missing in the canonical file but included in yours. It is similar to a line from the WordPress 3.0 through 3.4.2 sub-folder example, but not an exact match:
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
And also similar to the WordPress 3.0 through 3.4.2 subdomain example, but not an exact match to that either:
RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]
Either way, you appear to have a not-quite-correct legacy rewrite rule in your .htaccess
file.
That said, I don’t think that rule should get in the way, though it makes me wonder how it got there.
I do notice that the sites/
directory 404s (HttpFox output):
GET 404 text/html http://nsw.findrhinoplasty.com.au/wp-content/uploads/sites/
That makes me suspect a permissions problem on that directory or a parent.