FIXED 500 Internal Server Error on WordPress

https://bit.ly/2GWSkNL Wftpserver secret sale page.
FIXED 500 Internal Server Error on WordPress https://youtu.be/OhWUvQU2diU Grab your free 17-Point WordPress Pre-Launch PDF Checklist: http://vid.io/xqRL The 500 internal server error is not a WordPress-specific error. It is a general server error that may be related to your server settings or your WordPress files. Use the information in this tutorial to troubleshoot the 500 internal server error you are receiving. Here are the things you'll need to troubleshoot. 1. Your htaccess file may be corrupted. Try renaming it and see if that fixes the 500 error. If it does then the problem is in the htaccess file. 2. You may have reached the memory limit on your hosting account. Try increasing the limit using one of the methods outlined in this tutorial: https://www.youtube.com/watch?v=WmlGHje1V50 3. Try replacing the wp-admin and wp-include folders with fresh versions of those folders. This one is more complicated. Basically you'd backup those two folders in your hosting account and upload those two folders from a fresh version of WordPress downloaded from WordPress.org. Check Your Plugins The first 500 internal server error troubleshoot is by deactivating all of your plugins. To do this log into your site files using FTP or going through cPanel. If you go the cPanel route, click on File Manager in your cPanel. The find your website's root folder. It is usually in the public_html folder. Then navigate to wp-content and locate the "plugins" folder. Next rename the Plugins folder to something different like "plugins-old". This deactivates all the plugins on your site. If that fixes the problem, then you know the problem is with your plugins. Now that you know the problem is with your plugins you can go into the Wordpress back-end and activate each plugin individually to isolate the cause. You do this by activating one plugin, then reload your website. If you do not see the 500 Internal Server Error then it's not that plugin. Then activate another plugin and do the same until one of them breaks your site. Once you know which plugin is causing the 500 Internal Server error, you can either delete that plugin, replace it, or contact the developer for more help. If deactivating the plugins didn't fix the problem, keep on reading. Increase Your Memory Limit The next step in the troubleshooting process is to increase the memory limit on your website. Go cPanel and open the File Manager again. There may be a file in your website's root called php.ini. If there is not just create a file with that name. Now, open the newly created file in the code editor and type memory=128MB in the file. This should increase your memory limit. Now refresh your website. If the error is gone, the cause was a memory problem on the server and you have identified the problem. You should now contact your host support to figure out what is draining your memory and remedy the problem with their help. Replace wp-admin and wp-include Files If increasing the memory limit did not clear up the error, then copy in a new "wp-admin" folder and "wp-includes" folder in your WordPress site. This can be done quite simply, but you want to follow the right process to protect yourself in case anything goes wrong. First, go to your root folder and compress each of the current "wp-admin" and "wp-includes" folders into a zip archive. Just in case something goes wrong you'll have a backup of those files. Now go to wordpress.org and click on the "Download Wordpress" button. The downloaded zip file will contain the latest versions of "wp-admin" and "wp-includes". Unzip that WordPress file. Find the "wp-admin" and "wp-includes" inside the WordPress folder on your harddrive. Highlight both of them and compress them. Upload them into the root folder of your website using cPanel or FTP. Now go ahead delete the uncompressed versions of these folders in your website root. Next, extract the compressed folders and now you have fresh copies of them on your website. Refresh your website to see if that fixes the problem. If it does fix the problem, you can safely delete the compressed backups. Subscribe to this awesome channel here: http://www.youtube.com/subscription_center?add_user=wplearninglab