061375

Came across this error recently, leading me here.

Quote – “Usually an error 500 does not contain any information on content because it is thrown earlier than the sites content is generated.”

https://wpseek.com/function/_default_wp_die_handler/

This WP function in wp-includes/functions.php adds a 500 error after runtime FYI.

It looks like it checks if headers are sent and if not it can set the response code.

Still not sure why I’m getting this error however.

It appears to have fixed the issue for me.

Thanks!!!

Same issue here.
For me, in the body tag the main class is “admin-bar” instead of the “error404”.
So I am guessing its loading the wrong template.

In the debugger I can see that a proper 404 status was returned.

Logs are returning 200 again.
Thank you for the prompt update!

After the latest update in my logs I am getting an error when the Cron is running.

[Thu Jan 07 18:09:56 2016] [error] [client 104.130.216.196] PHP Warning: include_once(): Failed opening ‘/path/to/website/wp-content/plugins/wp-filebase/classes/CCron.php’ for inclusion (include_path=’.:/usr/share/pear:/usr/share/php’) in /path/to/website/wp-content/plugins/wp-filebase/wp-filebase.php on line 47
[Thu Jan 07 18:09:56 2016] [error] [client 104.130.216.196] PHP Fatal error: Class ‘WPFB_CCron’ not found in /path/to/website/wp-content/plugins/wp-filebase/classes/Core.php on line 104

The file is not there…
Its not in the latest version (following the link above) either.

In my case,”after” everything appeared to have completed and just before the database would have been updated I saw “failed because of readme.html” – (paraphrasing,..I don’t remember the error exactly).

Afterwards I was able to see the website initially.
But the admin page was just blank.
I turned on errors and saw that a function was missing.
Again, not totally sure what function.
But I know it was missing from wp-admin/includes/misc.php
I downloaded the new V from WP and uploaded the file.
Then the website stopped altogether and stopped producing errors or anything…just blank.

At this point I didn’t pursue it any further and simply went to the backup.

Looking at the folder I saw that the readme was changed on a different date than any the surrounding files.
( This made me a little alarmed ).

But then, I found this article, renamed the file and upgraded without issue.

I don’t think anything else in the directory is particularly unusual permissions wise.

This was the first upgrade of a few installations and I renamed all the other readme files before I upgraded, so I don’t know if this would be an issue elsewhere on the server.

I was unaware of this change to the readme file.
When I upgrade WP to 4.4 it broke because of the readme file change.
( as in broke the website instead of catching the error )

Luckily I had backups.

I was still unaware until I read this post. Now I will disable the feature as per your response. (I was worried my server was compromised when I saw the hashed file ).

It seems like it would be better to simply 403 these files in .htaccess.
Or better yet (if you can) do it in your conf.d or vhost.d files respectively.