Internal server errors, aka Error 500, can happen under WordPress just as often as they happen under practically anything else running on a server. You may think that the error itself will tell a tech all they need to know, but it really doesn’t say anything. In fact, internal server errors are the server equivalent of a patient explaining to a doctor, “I did something and now I don’t feel well.”
Before you ask for support, internal server errors are often caused by plugin or theme function conflicts, so you should start by manually resetting all of your plugins and your theme, which we already covered in WordPress and the White Screen of Death. If that doesn’t 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, it’s time to ask for support, but it would certainly help the supporter if you could offer 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.
Once you have all the relevant details, ask either your hosting provider or the WordPress Support Forums for further help. Be sure to describe what you were doing before the error occurred, all the troubleshooting steps that you have taken thus far, and include the quoted error message(s) from your server error log.