How to Fix HTTP Error 500 WordPress | Fixing Internal Server Error WordPress | 2023

Aug 16, 2023

How to Fix HTTP Error 500 WordPress | Fixing Internal Server Error WordPress | 2023

If you’re running a website, you may have encountered the dreaded HTTP Error 500, also known as the Internal Server Error. This error can be frustrating and confusing, as it doesn’t provide much information about what’s causing it.

In this video, we’ll show you 5 easy methods to fix HTTP Error 500 on your website, so you can get your site up and running again. We’ll cover common causes of the error, such as faulty plugins or themes, server issues, and more.

We’ll walk you through each method step-by-step, so you can follow along even if you’re not a tech expert. By the end of the video, you’ll have the tools you need to troubleshoot and fix HTTP Error 500 on your website.

Don’t let this frustrating error keep your website down - watch this video and get back online today!

00:00 - Intro
00:31 - Caution Before Proceeding
00:49 - 1. Conflict Between Cookies \u0026 Cached Data
01:41 - 2. Problematic Plugins
02:06 - Checking Plugins from the WordPress Dashboard
03:13 - Deactivating Plugins From Your Hosting Account
04:13 - 3. New Theme Installation or Update
04:28 - Checking Themes from the WordPress Dashboard
04:56 - Checking Themes from PhpMyAdmin
06:22 - Quick Favor Before Moving Forward
06:50 - Faulty .htacces File
07:59 - Insufficient PHP Memory Limit
08:49 - Enabling Error Display
09:45 - Restore Backup Files of the WordPress Website
10:08 - Outro

👩‍💻 Codes Used In Video:

Default WordPress .htacces Code: https://wordpress.org/documentation/a…

Code For Insufficient PHP Limit:

php_value upload_max_filesize 128M
php_value post_max_size 128M
php_value max_execution_time 300
php_value max_input_time 300
php_value memory_limit 256M

🔗 Affiliate Links:

Hostinger: https://hostinger.sjv.io/GjeBkL
Bluehost: https://bluehost.sjv.io/ZdoVJq
HostGator: https://partners.hostgator.com/MXxYYK
Get Elementor Pro: https://be.elementor.com/visit/?bta=2…

___

I appreciate you taking the time to watch my video! If you have any questions or concerns, feel free to leave them in the comments section below. I wish you the best of luck on your online journey.

#httperror500 #wordpress #Webinide #internalserver #error

Content

0.22 -> Hello & Welcome everyone, my name is Zaman Azam and today I'm going to show you the common

4.25 -> causes along with the ways to fix the HTTP error 500, so let's Dive In.

9.139 -> (Intro)

14.65 -> This error is quite frequent in WordPress, but there's no need to worry.

18.15 -> Pinpointing the root cause of the HTTP 500 internal server error on your website may

23.11 -> require some effort since there are several factors that could be to blame.

26.43 -> We'll take a closer look at each of the common causes and go through the steps for resolving

30.679 -> this issue.

31.68 -> Before proceeding, please note that Some Solutions require changes to the WordPress database.

36.16 -> It is important to exercise caution as any incorrect changes made to the database can

40.89 -> result in irreversible damage to your website.

42.75 -> I strongly recommend that you backup your website before making any changes to the database.

47.48 -> Alright then Let's begin.

49.47 -> Conflict Between Cookies and Cached Data

53.78 -> If the information displayed on a website doesn't match the stored cookies and cache,

58.35 -> it may result in the 500 internal server error.

60.38 -> As a website owner, you can attempt to determine whether the problem lies in your browser by

65.35 -> clearing the cookies and cache.

66.74 -> To do so in Google Chrome, first click on the three-dot menu icon in the top right corner

71.959 -> of your browser, then choose "Settings."

73.95 -> Next, select "Privacy and security" from the left-hand menu, after that select clear browsing

79.52 -> data, next change the time range to all time then select the cookies and cache from the

84.51 -> pop-up menu, and click the "Clear data" button to complete the process.

89.689 -> If the HTTP 500 error continues to persist even after clearing the cookies and cache,

94.39 -> it is necessary to explore other potential causes and examine whether the problem is

99.229 -> originating from the back end of your website.

102.29 -> Problematic Plugins The activation of a new plugin is the most

107.46 -> common cause of the HTTP error 500 on WordPress websites.

111.45 -> If the error occurs immediately after installing or updating a plugin, try deactivating the

115.6 -> plugin to determine if it is the source of the issue.

118.119 -> There are two simple ways to troubleshoot this.

120.549 -> The first method involves using the WordPress dashboard, while the second requires accessing

124.59 -> your hosting account's file manager.

125.95 -> To begin, let's try the WordPress dashboard method.

128.489 -> Access the WordPress dashboard and go to the plugins menu, then select 'installed plugins.'

131.74 -> Here, you will see a list of all the installed plugins on your website.

136.52 -> Check the plugin option at the top of the list, then select 'deactivate' from the bulk

140.239 -> action drop-down menu and click 'apply.'

142.51 -> Don't worry, deactivating a plugin won't cause any data loss.

146.25 -> Now, refresh your website to see if the error has been resolved.

149.69 -> If the error still persists, reactivate all of your plugins and proceed to other troubleshooting

154.66 -> methods.

155.66 -> If the issue is resolved, you need to determine which plugin caused the error.

158.79 -> Reactivate your plugins one by one and refresh your site after each activation.

162.05 -> If your website loads properly after reactivating a plugin, you can leave that one enabled.

167.709 -> However, if the error message appears after enabling a plugin, you can identify the source

172.47 -> of the issue.

173.47 -> Delete the problematic plugin from your WordPress dashboard and find another plugin with similar

178.02 -> functionality to replace it.

179.66 -> In some rare cases, you may be unable to access the WordPress dashboard.

183.19 -> In this situation, you can use the file manager as an alternative method to disable or remove

188.44 -> plugins.

189.44 -> You can use the hostinger's hpanel file manager directory to follow the steps.

198.15 -> Log in to hpanel and navigate to the file manager, then click on the 'Public_HTML' folder.

211.319 -> Open the 'wp-content' directory, then find the 'plugins' folder to locate the plugin

217.17 -> files.

218.17 -> Right-click on the plugin file and select 'rename.'

220.82 -> Add an underscore and type the word 'disabled' after the plugin name to deactivate it.

226.51 -> Click 'rename,' then refresh your website to see if the error has been resolved.

230.75 -> If the error message still appears, repeat the process until all plugins are deactivated

235.22 -> or until you find that the website is working again.

238.42 -> Once you have identified the plugin causing the HTTP error 500, delete the file.

243.35 -> You can try to reinstall the plugin or find another plugin with similar functionality

247.159 -> to replace it.

248.269 -> If the error persists even after deactivating all plugins, move on to the next troubleshooting

253.409 -> option.

254.409 -> New Theme Installation or Update Similar to plugins, a new or updated theme

260.16 -> can also cause the HTTP 500 internal server error.

263.81 -> to fix this you can simply change the website's existing theme.

268.12 -> To fix it via the WordPress dashboard, go to the appearance menu from the WordPress

271.79 -> admin area and then choose themes.

274.65 -> Click the activate button on any other theme except for the current one.

279 -> Refresh your website to check if the problem persists, and if it does, move on to other

288.24 -> methods.

289.28 -> Alternatively, you can change the WordPress theme by editing the MySQL database via phpMyAdmin.

294.35 -> Here's how to do it from hpanel.

296.86 -> Log in to your hpanel, then go to file manager and open the public_HTML directory.

309.479 -> After that, open the Wp-config.php file to find the name of the database for your website,

315 -> which will be shown in the DB underscore name line.

318.65 -> We will use this information to enter phpMyAdmin.

321.77 -> While still opening the file manager, go to the wp-content directory and open the themes

326.699 -> folder to check all the available themes you currently have.

330.69 -> Now let's navigate to the "Database" menu on the hpanel, and enter the phpMyAdmin of

336.24 -> your website's database.

338.889 -> After that, head to the "wp_options" table and find the "template" and "stylesheet" rows,

352.21 -> which are usually located on the second page.

357.63 -> Next, double click on each row to edit the theme name and change it to any of the themes

363.96 -> installed other than the current one.

366.319 -> Make sure to type it identically to the themes folder name.

375.64 -> Once it's done, go back to your website and reload it.

378.889 -> If the problem persists, let's try to find other possible causes.

381.78 -> Quick Favor Before Moving Forward: If you're looking for reliable and affordable

385.13 -> web hosting for your website, I highly recommend Hostinger.

390.09 -> I've been using their services for a while now and have been extremely happy with their

393.81 -> performance, features, and customer support.

397.44 -> If you're interested in signing up for Hostinger, please consider using my affiliate link in

401.52 -> the description box below.

403.14 -> It won't cost you anything extra, but it will help support my channel and allow me to create

407.71 -> more helpful content in the future.

410.34 -> Faulty .htaccess file Another way to solve HTTP error 500 is to

417.22 -> check if your current .htaccess file is not corrupted.

421.02 -> In case it is, you will need to create a new one.

423.55 -> Start by opening the file manager and locating the public HTML directory.

436.23 -> Find the htaccess file, right-click on it, and choose to rename it.

440.22 -> Create a new name for the file, for example, by adding underscore disable to the existing

445.979 -> name, and then press the rename button.

448.509 -> Next, select the new file and name it HT access.

452.08 -> If it doesn't automatically open, right-click on the file and select edit.

456.789 -> Copy the default WordPress Ht access code from the official WordPress site, and paste

461.61 -> the code into the new Ht access file.

463.61 -> I'll put the link to this code in the description box below.

466.75 -> Hit the save button, and you will now have a brand new Ht access file running on your

470.909 -> WordPress website.

472.379 -> If your website still shows the HTTP error 500 after reloading, let's move on to another

477.68 -> way to fix it.

479.479 -> Insufficient PHP memory limit Insufficient PHP value or memory limits could

486.3 -> be a cause for encountering the HTTP error 500.

489.27 -> This occurs due to the fact that certain scripts and plugins require a certain amount of memory

495.55 -> to function.

497.319 -> One way to solve this issue is to increase the PHP memory limit by manually editing the

501.84 -> Htaccess file.

502.84 -> To do this, navigate to the public HTML directory in your hpanel's file manager and double-click

511.75 -> the htaccess file.

512.75 -> Paste the code lines, then click save and refresh your website.

517.22 -> , This Code can be found in the description box of this video.

520.76 -> If the error 500 was caused by insufficient PHP values, your website should load properly.

526.55 -> If not, let's try another option.

531.61 -> Enabling Error Display Identifying the root cause of the HTTP error

536.45 -> 500 can be challenging, but it's essential to fix the issue.

540.7 -> If the previous solutions don't work, you may need to explore further and investigate

544.44 -> any other unknown errors on your website's backend.

548.18 -> One way to do this is by enabling error display through your hosting account's PHP configuration

554.68 -> section.

555.68 -> In hpanel, you can access it by going to the advanced menu and selecting PHP configuration.

560.67 -> From there, switch to the PHP options tab, click the log errors option, and hit the save

567.48 -> button.

568.48 -> By doing so, if your website encounters a PHP error, the system will generate an error

572.75 -> log file.

573.85 -> You can find this file in the logs directory within the file manager, which contains error

578.5 -> log messages along with the date, error type, and details of the file and code line to correct.

585.19 -> Restore Backup Files of The WordPress Website If the previous methods don't work, you can

590.8 -> try restoring your website to a previously functional version.

593.8 -> You can do this manually through the file manager or use a WordPress plugin.

597.85 -> If you regularly back up your website, this process can be simple by accessing the files

602.13 -> and backups through hpanel.

603.6 -> I will surely be creating a video on how to backup and restore your WordPress website.

608.98 -> And that's it.

609.98 -> a few methods on how you can troubleshoot the HTTP error 500 on your WordPress site.

615.86 -> if the problem persists even after trying all of the methods presented in this video

620.17 -> contact your hosting provider for some technical assistance.

622.829 -> if you are able to successfully troubleshoot the error don't forget to give this video

627.8 -> a thumbs up and share it with anyone you think needs to see this guide.

631.31 -> if you have further questions leave them in the comments below and I'll be more than happy

635.42 -> to help.

636.42 -> hit the Subscribe button for more videos about web hostings, websites and WordPress development.

640.56 -> Hope you liked the video and i will See you in the next one.

Source: https://www.youtube.com/watch?v=GDFNAJHTgL0