Rename your .htaccess to off.htaccess and see if that gets you back in.
Thread Starter
BalaPV
(@balapv)
tq it work but i need my htaccess what i have to edit in it? and y i get that error? plz help!
Awesome, now go to your permalinks settings page and hit save there. It should rebuild you a proper one.
The error 500 means the old .htacess is corrupt or has bad code in it. So we should ask WP to make a new one 🙂
Thread Starter
BalaPV
(@balapv)
ok can they give new .htacess. and cab if no .htacess file in site give security problem comes?
i’m getting this error too after upgrading to 4.1. renaming, or deleting, .htaccess makes no difference.
the site is still up but anything under /wp-admin/ produces the 500 internal server error.
can you update your htaccess with the default code?
details here: http://codex.ww.wp.xz.cn/htaccess
Before updating the dozens of sites we manage, I tried updating some of my own sites. Two out of three gave the 500 Internal Server Error
All three of these sites are NOT new ..and never had a prob with updates before. All 3 are running 4.0.1 (well one updated 🙂 )
Can it be a timeout issue ? I notice the proftpd process being active for a seriously long time when i try the failing ones.
No progress. Yesterday the apache error log showed timeout errors in mod_fcgid
Today, I am getting an nginx error “504 Gateway Time-out”
Any help or insights would be appreciated.
Solved: for my instance .. i increased the
FcgidIOTimeout 60
from the original 45 in /etc/httpd/conf.d/fcgid.conf
Then restarted both apache and nginx
i’m still struggling with this. have also increased the timeout in fcgid.conf but still have no access to wp-admin
