500 Internal Server Error – upload.php

Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

If that does not resolve the issue, try switching to the Twenty Fourteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP client to view invisible files.

If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

Hello,

Once I got the same error in uploading media files to one of my word press site.

I just change the file name to only text (Without using any special character) and able to upload that.

I have no so much idea on working with codes. May be It will help you to solve your problem at this case. Then you try to search the actual problem and resolve that.

Thanks.

Ah, if that were the case it could have been a server-side security filter, like mod_security, misinterpreting the file as code.

Hi guys,

thanks for all the tips so far! As I said, unfortunately I have tried all of your suggestions before, James. But it’s good that now there is a thread where all of them are in one post for others to find! ??

Mihirbabu, that’s an interesting approach, however this wasn’t my issue. The author of my theme had a look at my server settings and he found out that my PHP memory is too small. My client’s website runs on PHP 5.4 with only 64M memory. He told me that today’s standard is 128M and that he recommends at least that for his and other themes to run properly. 64M apparently is a very unusual configuration these days.

I managed to upload another theme via FTP and it worked. However, when working with it, the website constantly crashes with a 500 error. Now it seems like it just can’t handle the amount of data that is being uploaded when I change, for example, the font of my H1. So I think that’s the solution for my problem.

Right now, I am trying to convince my host to grant me more memory – let’s see how they respond.

Thanks everybody for your help!

As I said, unfortunately I have tried all of your suggestions before, James.

Ok, so what does your server error log say at the time of the error? Because that’s one of the suggestions. ??

As I wrote in my original post: Premature end of script headers ??

Oh, that’s all it says? Nothing more specific to the error in the log?