Moderator
t-p
(@t-p)
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 default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, 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 SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP 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.
Thread Starter
jalte
(@jalte)
Hi Tara
Thanks for your answer, but the things you say I should do is exactly what I wrote I already did (with no result)! I’ve also posted the server error log you asked for at the bottom of my question.
Jalte
Moderator
t-p
(@t-p)
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 SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.
Thread Starter
jalte
(@jalte)
Hi Tara.
Thanks for the response.
I’ve tried that (deleting .htaccess and later uploading a new version) with no result.
I suspect the solution to the problem has something to do with the error I’m getting when I log onto my cpanel (“[Thu Aug 11 21:51:42.411927 2016] [:error] [pid 167345] [client 85.204.195.166:60258] SoftException in Application.cpp:430: Mismatch between target GID (651) and GID (99) of file “/home/jaltewin/public_html/index.php””. But I have no idea what it means.
Moderator
t-p
(@t-p)
Have you tried contacting your hosting provider and discussing this issue with them?
Thread Starter
jalte
(@jalte)
Hi Tara
Over the weekend the error oddly enough fixed it self the same way it occurred — out of the blue.
I think it had something to do with my provider (meebox). Anything else (I can think of) doesn’t really make any sense.
Thanks again for your time
Jalte
i think “500 Internal Server Error” = problem in wordpress core or plugins
If you ‘ve changed your WordPress Core ( more than all function.php ) or change plugins code , PLZ UNDO STEP BY STEP
more information about 500 internal server error in ma site ( http://www.aracode.ir)
