Finding out the cause of 500 Internal server error. My conventional course to fixing blunders is to run WordPress logs to discover what’s causing your mistake in any case. You can utilize WordPress logs to fix a large number of the issues that happen on your WordPress site. This very supportive component tracks mistakes and records them so you can begin on the investigating cycle.
For a total manual for this cycle, you can peruse here, yet I’ll go over the rudiments on this post. Cautioning: Before changing any documents, make a reinforcement of your site.
Access your site’s records. You’ll need to utilize a FTP to do this.
Open your wp-config.php record. When you have this open in your FTP, you’ll need to open your root document (frequently named root or named after your site) and you’ll need to open the wp-config.php record. Look down until you see a line that peruses “/* That’s everything, quit altering! Upbeat writing for a blog. */.” You’ll have to glue in the accompanying line of code before this:
define( 'WP_DEBUG', true );
This coding educates WordPress to initiate the troubleshooting mode. On the off chance that it’s now there, simply change bogus to valid.
Directly underneath that line, you should add one more bit:
After this, you can spare the recently altered record and exit. At that point, you will need to trigger your mistake message again so it will record in the log.
Discover your WordPress logs. In your site’s root organizer, explore the wp-content folder, and search for another document called debug.log:
define( 'WP_DEBUG_LOG', true );
Also, you can paste the following code in your active themes functions.php file at the beginning.
ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(E_ALL);By doing the above steps you can see the errors which cause 500 error. After that, you can identify the error and fix.
After you see what caused the mistake, you might have the option to investigate it yourself. If not, you can go to the WordPress technical support gathering and discover answers there. On the off chance that you don’t discover answers, present a post and make certain to reorder your blunder code there so you can get help rapidly. I expectation this makes a difference! *One all the more snappy note, you’ll need to kill your logs subsequent to fixing the issue in light of the fact that having it run consistently can hinder your site. You’ll adhere to similar guidelines as above to get to your wp-config record just this time you’ll change the “valid” back to “bogus”.