yolandapadilla

Thanks @barnez and you are welcome @tacoverdo! Love Yoast plugins and blog.

I make my living diagnosing and fixing the tough stuff for people. Always keep a clear head, stay methodical and never freak out. ??

Is now OK, not giving error pages.

What I did:

Via FTP, renamed the SEO plugin … in effect disabling it. Was able to log in. Various pages that caused errors before were OK.

Logged out. Logged in with different OS. OK. Logged out.

Via FTP, renamed the SEO plugin back to its correct name.

Logged back in. All looked OK.

SEO Plugin showed no longer activate. I activated it.

Clicked around. All OK. Logged out. Logged back in. All still OK.

Glad I am back to being able to admin this site.

Puzzled about what this is.

Possibly my hosting company was making some changes that happened at the same time I was updating this great plugin????

I had the same problem when I went to log in after upgrading to 2.5. Here is how I fixed it.

First, I checked my error logs to look for a clue about what was causing the internal server error. (Here is a quick how to check your logs for sites running cPanel: https://www.cpanelsupport.net/?p=36)

The relevant entry in the logs was [2008-04-15 23:37:11]: error: file is writable by others: (/home/mysite/public_html/wp-login.php) (664)

So I looked at the permissions for the file wp-login.php and they were -rw-rw-r-- (644)

I did a CHMOD to change permissions to -rw-r--r--

And ta da, the problem went away and logging in worked fine.

I had the same problem when I went to log in after upgrading to 2.5. Here is how I fixed it.

First, I checked my error logs to look for a clue about what was causing the internal server error. (Here is a quick how to check your logs for sites running cPanel: )

The relevant entry in the logs was [2008-04-15 23:37:11]: error: file is writable by others: (/home/mysite/public_html/wp-login.php) (664)

So I looked at the permissions for the file wp-login.php and they were -rw-rw-r-- (644)

I did a CHMOD to change permissions to -rw-r--r--

And ta da, the problem went away and logging in worked fine.