There’s usually four problems that cause a 500 error. Follow our available solutions to resolve it. <\/p>\n\n\n\n
A 500 error means there’s an issue in the PHP code of your site. To identify the issue, start by enabling debug<\/a>. Then, follow our four available solutions. <\/p>\n\n\n\n The most common cause for a 500 error is running out of memory. To check if this is the problem, see if the error log file shows:<\/p>\n\n\n\n The second most common cause for a 500 error is conflict between different plugins and themes. Since your site is stuck, you’ll need to use an FTP program to resolve the code conflict. <\/p>\n\n\n\n To resolve a code conflict with an FTP program: <\/p>\n\n\n\n Deleting WPML won’t affect your site’s language information. Once you resolve the conflict, all your language information will be restored when you re-enable WPML.<\/p>\n\n\n\n The 500 error can happen when you don’t run the newest version of WordPress, or WPML. To check if this is the problem, update WordPress and WPML to the newest version. <\/p>\n\n\n\n In rare cases, hosting companies switch off some of WPML’s PHP versions<\/a> and extensions. If this happens, the error log will show an extension or function doesn’t exist.<\/p>\n\n\n\nIs the 500 error happening because I’m running out of memory?<\/h3>\n\n\n\n
Allowed memory size of YOUR_LIMIT bytes exhausted (tried to allocate SOME_MEMORY bytes) in...<\/code><\/p>\n\n\n\n\n
\n
Is the 500 error happening because of a code conflict?<\/h3>\n\n\n\n
\n
Is the 500 error happening because of compatibility issues with WordPress versions?<\/h3>\n\n\n\n
Is the 500 error happening because of compatibility issues with PHP versions and extensions?<\/h3>\n\n\n\n