dononeil

@ipstenu… I agree, however if there was a server issue I would have seen it LONG ago and with the previous version of WP… I’m thinking it’s an incompatibility with one of the plugins and the new version that is causing this. I have dozens of other users using the older version of WP without issue, this was the first customer to upgrade.

Well, I am the hosting provider, so I know there aren’t any issue with the apache config… the problem only popped up when we upgraded to 3.04. I think it may be a plugin issue. I am going to try what others suggested, perhaps installing a fresh version and then seeing if everything works ok, then puttng the plugins in one at a time until it breaks.

@emil Uzelac, yes, I removed the extra part of the .htaccess file;

RewriteRule ^index\.php$ – [L]

And have tried it with both rewrite rules for index (both singularly and together) and no difference. I found the rule above listed in the blog on how to setup the permalinks and was originally thinking that was the problem, but it doesn’t seem to be.

wp-admin exists, and is not missing files.

Like I said… if I disable the .htaccess;

1) I can get to wp-admin and everything there works fine
2) I can get to ‘regular’ post names, but not permalinks (obviously)

If I enable the .htaccess

1) I can NOT get to wp-admin
2) I can get to the permalinks

So either something is wrong with the base code, or there is a bug somewhere in some part of the upgrade or code… I installed it with Installatron, and used Installatron to perform the upgrade. Maybe something they do broke it?

I would think I just need to add an exclusion for wp-admin (which is what I thought one of those is supposed to do, for directories), but I don’t know how to do that.

It’s in the main domain/folder, not in a sub folder…. the url is https://www.troublebrothers.com

Yes, I’ve tried exactly like that… same problem.

It’s like Apache (or wordpress) is ignoring

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

I’ve restarted the server to make sure it’s not that. This only started popping up when I did the upgrade.