Cannot login or access dashboard after WP update to 4.4

Joshua the /tmp was full and they cleaned it, MySQL was unable to write temporary files which was causing the login issue with WP.

FYI for testers: the database change in 4.4 is not a breaking change for reverting to 4.3.1. Don’t bother with restoring db backups. Just a change to the size of one column.

Hmm, with Sam’s insight and my hosting support’s looking into the logs, I don’t think the /tmp was the issue for the login 404 error, at least not in my case. I’ve ruled everything out except restoring the database, so I’ll try that later tonight when I’m able.

Outside of that, I’m stumped at this point.

Still no luck, but I have other sub-directory sites updating without issue. Could the issue be related to the database update? I just updated another site in a similar fashion and it prompted me for a database update before successfully working, whereas the site in questions with the error did not.

Here’s a twist – I changed the database in wp-config.php to a new, empty database. This resulted in my having a redirect loop error for the site. If I modify it back to the original database, it’s back to a 404 on the admin pages. I’ve done just about everything else short of creating a new site at a new domain…

Hey guys,

Here’s my update: I did a manual upgrade and everything works fine now; no more problems with login and accessing dashboard.

There might be a problem with the auto-update.

There might be a problem with the auto-update.

Unfortunately that’s not it.

@joshua David Nelson I’ll contact you directly via email and see if I can help resolve it.

After debugging this with Joshua, I’ve found that multiple files in the account had their file permissions incorrectly set to 0664 instead of 0644.

MediaTemple doesn’t like 0664 file permissions and attempts to run PHP files with those permissions causes a 404, correcting the permissions fixes it.

Can the others experiencing the issues please check the file ownerships via FTP? / are you on MediaTemple too?

Hello all,

I have a similar error after updating to WP 4.4, i’m able to login, but when i try to access

https://www.saabportugalclube.org/wp-admin/

i just get the Admin bar on top of the page, but whatever i click on (updates, admin bar whatever), the page just redirects to for instance

https://www.saabportugalclube.org/wp-admin/update-core.php/

bus shows only the main page content(https://www.saabportugalclube.org) and not the Admin console content.

I’ve disabled the plugins, themes and the situation is the same no behaviour change.

Can someone help out?

Well, with some great help from Dion, we were able to determine that the issue with my staging site was related to file permissions. I’ve played around with the git some more (switching branches, merging updated file permissions) and replicated the issue, but I can’t verify yet the root cause.

So, if you’ve done everything else, be sure to check your file permissions. I’d recommend using ssh to unilaterally update your directory and file permissions as outlined in the codex article.

UPDATE: I didn’t see Dion’s response above until after writing this, but hopefully it’s helpful to someone.

Hello all the folders have 755 and file 644.

@apathy98 are you behind any caching or CDN? Those might need to be cleared. Otherwise, it could be a corrupted htaccess issue as well.

I cleared browser cache on the several browsers I tried, still the same…

Regarding the harness, is it normal to be corrupted via upgrade?

Thanks

the htaccess? no, but it’s next on the list to check ??

Your error is a little different, because you’re not receiving a 404, it’s just showing the main site at the /wp-admin url. However, if you’ve eliminated caching, plugins, themes, and file permissions as potential causes you should try re-installing WP (replace the core files, not your wp-content folder or wp-config.php file with a fresh copy) and checking your htaccess file.

OK so also tried to overwrite a fresh WordPress core ( for version 4.4 and older) but the behavior maintained the same, I’ll have to check in depth the htaccess.

I wonder if there were any changes made to this DB version that were not populated properly.