500 internal server error error cpanel

500 internal server error error cpanel

wpastra.com › guides-and-tutorials › 500-internal-server-error. The 500 Internal Server Error means that the server has been unable to fulfill the request due to an unexpected condition. As a result, the page. How to fix 500 internal server error in WordPress sites · Solution 1: Reset the.htaccess via WordPress admin panel · Solution 2: Manually reset. 500 internal server error error cpanel

Remarkable: 500 internal server error error cpanel

Emm386 error #e2 memory
Terror mixen 2007
I/O ERROR 103 NETSPH

500 internal server error error cpanel - final, sorry

The message 500 Internal Server Error is one of the most frustrating messages a website owner can encounter. If you are lucky, it is followed by an explanation such as “Connection Timed Out” or “Please check your internet connection and try again”.

However, if it is not followed by an explanation, you may just see a blank page where you cannot continue.

If you are a WordPress user, you will at some point come across the term “500 Internal Server Error”. This error is triggered by your WordPress website whenever there is an internal problem. If this is the case with your website, you can be sure that something has gone wrong with the configuration of your web hosting provider’s server.

If you have accessed a particular website and received the dreaded 500 Internal Server Error message, do not panic! This usually means that the server cannot process the request properly. There are things you can do to fix this problem. You can find these solutions here.

You may want to leave this task to an experienced developer. But you do not have to. If you are one of those who, like me, want to fix things immediately, then you are in the right place.

Are you ready to get to the bottom of this? OK, First you need to understand the error, why it is a server error and how to fix it.

What is a 500 Internal Server Error?

500 Internal Server Error image - 500 Internal Server Error Solved Learn To Fix It😁 Speed

(500-internal-server-error-example-image-562×340)

First of all, you need to know that this internal server error 500 is an HTTP error and that there are several status codes associated with the Hypertext Transfer Protocol AKA as HTTP. You can see the complete list of status codes here:

10 Status Code Definitions.

Today we will deal with one of the worst status codes: the status code 500 Internal Server Error. This HTTP status tells you that the server hosting the website you are accessing is unable to process such a request. There are many causes for this error, but in general, it is best to investigate the server itself.

What causes a 500 Internal Server Error?

There are many reasons why a 500 Internal Server Error may occur, some of which are: 

  • No permission to access the website
  • You cannot connect to the server hosting the website
  • There is a configuration problem with your network
  • Excessive PHP timeout
  • PHP memory limit exceeded
  • Incompatibility with the PHP version

Fixing 500 Internal Server Error WordPress

Fixing 500 Internal Server Errors can be a challenge, even for an IT professional. They occur when the server is busy or can not handle all your requests at once, and they are usually caused by problems configuring the hosting server that runs most websites. To fix this 500 HTTP protocol server error, we first need to locate it. This requires a troubleshooting strategy. So let us begin.

Troubleshooting 500 Internal Server Error in WordPress.

Learning to fix the 500 Internal Server Error - 500 Internal Server Error Solved Learn To Fix It😁 Speed

Troubleshooting 500 Internal Server Error in WordPress can be a daunting task, to say the least. The first thing you should do is check that your server is working and operational. If the server is up and running, you should check if your hosting provider has a customer support hotline. The problem is that sometimes the hosting provider’s support team takes too long to respond and you need to fix the 500 error now. That’s why we created this 500 Internal Server Error Troubleshooting Guide.

In this guide, we will troubleshoot your 500 Internal Server Error in five steps:

  1. Check if plugins are causing the problem
  2. We will check the installation of the theme
  3. Check if the .htaccess file is corrupted 
  4. Ask help to the support of the hosting provider
  5. Reinstall or reset WordPress

1. Checking WordPress plugins

Plugins on WordPress Provoking the 500 Internal Server Error - 500 Internal Server Error Solved Learn To Fix It😁 Speed

The best way to find out what plugins might be the cause of the 500 status error is to disable all plugins and then activate them one by one. Which will make it easier to find the culprit and fix it. Now, disabling the plugins is very simple, here is how:

3 Steps to disable all WordPress Plugins:

  1. Log in to your WordPress dashboard.
  2. Under Appearance, find the “Plugins” section. Hover over the word “Plugins” and click on “Installed Plugins”.
  3. In the plugin dashboard, click on “Bulk Actions”, select “Disable” from the list of drop-down options and click on “Apply”.

All installed plug-ins should now be deactivated.

Now it is time to find the culprit!

For this, you need some patience because you have to go through one plug-in after the other until you find the plug-in that is causing the 500 Internal Server Error.

The best way to find out which plugin is causing the HTTP 500 Internal Server Error:

  1. After you have deactivated all plug-ins, keep the normal browser open in which you have deactivated all plug-ins. Then open an incognito browser and open your website or the web page that triggered the Internal Server Error Code 500.
  2. Go back to the normal browser (not the incognito browser) and activate the first plugin in the list.
  3. Clear the entire cache, wait 1-2 minutes and press Ctrl+Alt+Sup on the incognito page.
  4. Check whether the error occurs again. If it does, you have found the culprit. If the error does not reoccur, continue troubleshooting all other plug-ins until you find the one causing the error.

Ok, having done all that, you have solved the problem? Great, then you can continue your work, but if not, then you need to do more tests!

There is another possible scenario that happens when you can even load your website at all due to the 500 internal server error. In this case, you will need to login to your Cpanel and go to the section called “File manage”, find the folder that contains all plugins and disable them from there. here is how to disable all plugins using Cpanel.

Steps to disable all WordPress plugins using Cpanel:

  1. Log into your cPanel and click on the file manager folder.
  2. Navigate to your WordPress installation folder. Example – Public_html/your-website
  3. Locate the plugins folder, which you can find here: Public_html/your-website/wp-content/plugins. There are all plugins you were using in your WordPress website.
  4. Now rename the plugins folder, to something like “faulty-plugins”. To rename the folder – > simply right-click on it – > Rename

Now all plugins that you have installed in your WordPress are disabled. Try reloading your site in your browser’s incognito mode to see if the problem you were having is now gone. If so, you need to find out which of the plugins caused the problem.

To do this, you should first create another folder and name it “plugins”.

From here you should try to open your website in an incognito tab. The best thing to do is to reinstall all the plugins one after the other and try to see if the problem occurs again with each reinstallation.

The advantage of this approach is that you will not receive an error message in case of a faulty plugin. That means you do not have to check which one it was, you just have to delete the renamed plugin folder, and sayonara 500 Internal Server Error.

500 Internal Server Error: Solved!

No? Oh boy! let’s continue with our troubleshooting!

2. Check the WordPress theme installed

Themes are prone to internal server errors that can be fixed with the right know-how.

There are many reasons why your website is not working properly, but some of them point to your installed themes. WordPress is a popular content management system that often has issues with themes. With the right know-how, you can rule out your theme as the culprit for the 500 Internal Server Error by deactivating the theme marked as “active” in your theme’s dashboard. These are the steps:

  1. – Log in to your WordPress dashboard
  2. – Hover over the “Appearance” left menu item and click on “Themes”.
  3. – Deactivate the active theme and activate a default theme. (WordPress currently comes with three default themes: Twenty Nineteen, Twenty Twenty and Twenty Twenty-One).

After performing this method, you should open an incognito tab again and try to load your website. If it works, you have found the culprit. 500 Internal server error fixed!

But what if you can no longer log into the WordPress backend dashboard because of this 500 Internal Server Error?

Then you need to follow these further steps to manually deactivate the themes via Cpanel.

Disabling WordPress Themes Using Cpanel:

  1. Log in to your cPanel and click on “File Manager”.
  2. Double-click on the “public_html” folder and navigate to the “wp-content” folder and click on the “themes” folder. 
  3. You should then see the list of installed themes. It is best to rename your main theme folder to “testing-theme”.

Once this is done, open your website in an incognito tab to check if it works!

If it does not, we move on to the third and simpler method of troubleshooting the 500 Internal Server Error.

3. Check if the .htaccess file is corrupted

When you get an internal server error on your WordPress website, it is not uncommon for the cause to be a problem with your .htaccess file. If this is the case, it may be because you or someone else was trying to make changes to the site or perform upgrades or modifications when the error occurred.

To fix the 500 Internal Server Error, you can try repairing, restoring or recreating a .htaccess file. This htaccess file allows you to make changes to the configuration of your website without having to edit the server’s configuration files. Because of the great importance of this file, it must be handled with care, as it can mess up your entire website and cause the 500 Internal Server Error, among other errors.

If the Htaccess files become corrupted, this can lead to problems such as broken links, internal server errors, unwanted redirects and much more.

If your .htaccess file becomes corrupted, it is usually because you have installed a faulty plugin (often nulled plugins) or tried to customise the file by adding commands that are not supported by your web server. The most common cause is themes that are not coded correctly (or trying to install nulled themes). In any case, you need to fix this 500 Internal Server Error (and stop using nulled plugins and themes). So let us try to fix this server error by correcting your Htaccess file.

The best option you have is to use a backup that you or your hosting provider may have. 

If you replace your current .htaccess file with a backed-up file, most websites that experience this 500 Internal Server Error due to a corrupted .htaccess file will be back online and the error fixed!

Oh, you do not know how to find your htaccess file? I do not know that either! XDDD. Just kidding, here are the steps to find the htaccess file:

In most cases, you will find this .htaccess file in the root directory. Yes, there where you can also find other important folders like wp-admin, wp-content and wp-includes.

Some hosting providers hide the htaccess file because it is important for the operation of your website. If you can not see it, make sure all hidden files are viewable. Just check the file manager settings of your WordPress hosting account.

How to find an Open .htaccess File?

  1. Go to your file manager folder – > you will find the folder public_html. (root folder)
  2. If you cannot see the .htaccess file, navigate to the top-right menu, there you will see the word “Settings”, click on it and activate the option Show hidden files.
  3. Now activate the display of all hidden files so that you should now be able to see the .htaccess file.

Here you can simply delete the file and create a new one or edit the current file. Here you can see how to carry out these two tasks:

Task one: Delete the htaccess file:

Just click on the file and press delete! I told you it was easy! 

Task two: Create a new htaccess file:

OK, this is quite easy and you should do it directly from the Cpanel dashboard. These are the steps to create a new htaccess file:

Click the New File button at the top of the menu.

You need to name the file .htaccess, yes, with the dot in front of it. Paste the code I have given below, because that’s the default setting you need for your WordPress website, and click “Create” to save your changes.

The default settings of the Htaccess file:

# BEGIN WordPress

RewriteEngine On

RewriteBase /

RewriteRule ^index.php$ – [L]

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule . /index.php [L]

# END WordPres

There is also the option to use and FTP client.

An FTP Client is a sofware that manages files on a remote server.

So, if you are using an FTP Client to upload your website content instead of WordPress’ built-in editor, then follow these steps:

Go to the Server menu and enable the option “Force showing hidden files”.

Now you should see the .htaccess file that was hidden.

In case you were wondering: Are these steps the same for all hosting providers? They may vary a little, but in general, the variations are very small.

Ok, it’s time to test the salt! Is it sweet? Does your website load perfectly? Nice, you just fixed the 500 Internal Server Error. Hooray!

No? Do you mean you are still seeing the same error? Then it’s time to get help!

4. Ask for the support of your hosting provider

If you have come this far and your 500 Internal Server Error still persists after all of the above, it is time to ask the support team at the company providing your hosting service to reset your site to the last working version from which a backup was made.

Some unusual problems can trigger these 500 internal server errors in WordPress, but at this point, it may be best to ask your host. The problem may even be a genuine server issue that they can at least confirm, and they can also investigate things like file permissions errors and other causes.

The problem with this method is that hosting providers sometimes have very poor customer support. To fix the error today, try contacting the provider, preferably via live chat. If there is no such thing as live chat, change hosting providers. XDDD, Nah, just kidding, send them an email or give them a call. 

But at this point, these support features are an indicator of how good your hosting provider is, and if it’s bad, you’d better switch to a better provider. There are many options, I can tell you 4 of the best:

  1. SiteGround
  2. Hostinger
  3. WPEngine
  4. Namecheap

Now for the last method, which I list last because it should be your last option, namely resetting your WordPress installation.

5. Reinstalling your WordPress site

Say none of the above has worked, even your hosting provider’s support has not responded yet, but you need to fix that 500 Internal Server Error today. Desperate diseases need desperate cures!

Here you will carefully try to fix everything, and this article will help you. So let us do it right.

First of all, you need to make a backup of your files, for this, you have two options:

  1. Download the backup created by your hosting provider.
  2. Manually create your own backup.

Whatever you decide, these are the steps to create a backup of your website:

How to download a backup from your hosting provider:

  1. Log in to your Cpanel dashboard.
  2. Look for an icon labelled Tools & Utilities. There you should see an option called Backup Manager.
  3. Then click on the appropriate icon for the backup file you want to download and save the file to an easy-to-find location on your computer.

Manually create a backup of your website’s files.

There are two options here, depending on how serious your 500 Internal Server Error is.

  1. If you are able to log into your WordPress backend dashboard, you can simply export a backup using the “Export” option you see when you click on the “Tool” option in the left side menu of WordPress.
  2. If you do not have access to your WordPress dashboard at all, you’ll need to go to the Cpanel dashboard or use an FTP client. Let us take a look at how to do this properly.

Create a backup of your website via the WordPress dashboard:

Creating a backup of your website thru Cpanel and FTP Client

Finally, and no less importantly, once you have backed up all your files, you can simply reinstall your WordPress, preferably from your Cpanel dashboard. If you need help reinstalling WordPress, here is another nice video:

Uninstalling & Reinstalling WordPress to Troubleshoot.

How does the 500 Internal Server Error impact SEO?

Now you know what an internal server error is and how to fix it. Now it’s time to take a look at the effects this error could have on the search engine optimisation of your website.

An internal server error can be a serious problem that can cause you to lose visitors, revenue and even your search engine ranking. That’s why it’s important to invest in a service to optimise your website.

It can take months to recover if you do not take action. Therefore, it is important that you address this problem before your website is affected.

One way to identify potential 500 server errors on your website is to conduct weekly technical audits to identify issues before they can lead to bigger problems.

You do not want your online business to suffer the effects of 500 server errors for too long.

If you feel you can not do this, do not panic, just drop us a line in the comments below and we will sort it out for you.

Fixing the 500 Internal Server Error Final Words.

There you have it, all the most effective solutions for a very annoying problem that tends to break our nerves every time it happens. If you have any questions, please feel free to contact us and we will be glad to help!

I tried my best so everybody can follow regardless of their level of knowledge.

Hopefully, you found this article to be helpful, please share it with your friends and your cat.

Good luck!

Share:

In this article, we will show you how to fix the internal server errors in WordPress.

The internal server errors are status codes returned by the web server whenever it encounters a condition that prevents it from completing the request initiated by the client. This error message does not necessarily mean that the web server is responsible. The causes of such errors are multiple. We’ll be discussing several solutions to this problem and walking you through each.

Quick Steps:

  1. Check for corrupt .htaccess rules.
  2. Increase the PHP Memory limit in WordPress.
  3. Deactivate faulty plugins.
  4. Check file permissions.
  5. Upload the core WordPress files to your site.

Create a New .htaccess File

Create a new .htaccess file on your WordPress root directory – public_html. If you cant find the .htaccess file or any dotfiles, enable Show Hidden Files (dotfiles) from the Settings icon on the top right corner of your window.

Settings in File Manager.

Once you found the .htaccess file, right-click the file and rename it to .htaccess.bk to disable it. To create a new .htaccess file,  go to your WordPress Admin  >> Settings and select Permalinks. Scroll down to the bottom of the page and click the save button. This will create a new .htaccess file with the proper redirection rules for your site. 

Open your browser and call your website. If your site loads then the 500 internal server error was caused by the corrupted .htaccess file. If you’re still seeing the error, move on to the next section.

Increasing the PHP Memory Limit

Another way of fixing the 500 internal server error is by increasing the PHP memory limit in WordPress and refreshing your site to test whether or not this is causing your 500 internal server error.

Open File Manager and locate the wp-config.php file from your root directory. Right-click on the file, and select Edit to add the following code below inside the opening PHP tag,

define(‘WP_MEMORY_LIMIT’, ’64M’); ini_set(‘post_max_size’, ’64M’); ini_set(‘upload_max_filesize’, ’64M’);

Refresh your site and if you are still seeing the error then the issue is not because of the PHP memory limits. Remove the above code from the file wp-config.php and save it.

Deactivating Plugins

Connect to your website using a FTP client, or the File Manager tool in cPanel. Once connected navigate to the wp-content folder. Right click on the plugins folder and select Rename. Change the name of the plugins folder to plugins.bk. This essentially deactivates all the plugins on your site. 

Refresh your website. If the site loads, then the error was due to a faulty plugin. Activate each plugin one by one and refresh your website after each plugin activation to find out the problematic plugin.

Check the File Permissions

Permissions for the folders and files in your WordPress directory should be 755 or 644, respectively .Check if they have the correct permissions.  If they are anything else but 755 or 644, it can cause these 500 errors. To solve this, open up File Manager, go to the root directory and right-click on the files/directories that have the incorrect permissions and click Change Permissions. A popup window will appear on which you can set the permissions to 755 or 644.  

Changing Permissions via File Manager.

Changing Permissions via File Manager.

Re-building the Core WP Files

This step is considered as a last resort. Download a fresh installation of WordPress from their downloads page. Extract the zip file and open the extracted folder. Connect to your WordPress website using an FTP client and upload the wp-admin and wp-includes from your fresh version of WordPress to the root folder of your website – /public_html. The FTP client will now transfer those folders to the site’s directory, overwriting the older files. 

Conclusion

The 500 internal server errors can be really frustrating, we know, as it is difficult to pin point the exact cause of the error. If all methods fail, then contact us. We’ll be happy to take a look.


If the steps above listed in this article do not resolve your issue, please feel free to open a support ticketand we’d be happy to take a look. 

Our Guiding Principles

  • Provide consistent, stable, and reliable web hosting services.
  • Ensure rapid ticket response and quick resolutions to issues.
  • Never saturate or over-provision servers to ensure stability and speed for our customers.
  • Use only high-quality enterprise-class hardware to ensure minimal downtime from hardware failures.
  • Provide clear pricing with no hidden fees or gotchas.
This article was posted in How-To Guide, Troubleshooting & Errors, WordPress and tagged 500 Internal Server error, internal server error, WordPress

How to fix 500 internal server error: 8 solutions

The error 500 – Internal Server Error is a very common issue in webservers. It can be caused by several reasons. In this article, we will explore the possible causes and present alternatives on how to fix 500 internal server error. This error is similar to the 404.

how to fix 500 internal server error

Article contents:

1.0 The causes of the 500 error
2.0 How to fix 500 internal server error in WordPress sites

CHEAP WEB HOSTING

2.1 Solution 1 – Reset the .htaccess via WordPress
2.2 Solution 2 – Manually reset the .htacess file
2.3 Solution 3 – Update and deactivate plugins
2.4 Solution 4 – Try to change your theme

3.0 How to fix the 500 error in non-Wordpress sites

3.1 Solution 5 – Check your .htaccess syntax
3.2 Solution 6 – Rename your .htaccess file
3.3 Solution 7 – Enable error displaying in PHP
3.4 Solution 8 – Check your error logs

4.0 Conclusion

The causes of the HTTP error 500

Whenever a web server delivers a web page to the client, it throws HTTP status codes. Each status code means the result of such a request. For example, the HTTP status 200 means success: when a page was delivered and shown correctly.

For example, the status code 404, means the error Page not found. Then, the HTTP error 500 means an internal server error message. Such error 500 is one of the widest HTTP errors and may have several possible causes. In this article, we will approach the most common causes. And of course, show the fixes for them.

Such specific error is most commonly caused by server side issues. Even one single PHP script syntax errors, file permissions or htaccess misconfiguration can cause such error. This error doesn’t depend on the operating system – both Windows and Linux based web servers will present such HTTP status code. Even external resources can cause the 500 error.

How to fix 500 internal server error in WordPress sites

Most of the problems generating the 500 server error in WordPress are caused by issues in the .htaccess file. Some of the problems are caused by plugins or templates. To troubleshoot this issue, we will, first of all, reset the .htaccess file. Then, if it persists, we will look into a problem with plugins or the templates.

The .htaccess file is a common file that defines redirections and behaviours in the web server. cPanel has a default .htaccess file, which is placed inside the root folder of your WordPress blog. For example, our blog is on the root folder of the website. So, the .htaccess file is located inside public_html.

Most of the error 500 issues in WordPress are caused by plugins or a misconfiguration in the .htaccess file. We suggest resetting this file.

There are two methods:

Solution 1: Reset the .htaccess via WordPress admin panel

First of all, open the Permalinks section. It’s located under Settings.

Whenever you make changes to your permalinks structure, WordPress automatically resets the .htaccess file. Please note that resetting this configuration may affect your SEO. Now, we recommend changing the option on this screen. After that, click Save. This way, WordPress will reset your .htaccess file and the error 500 may be solved.

CHEAP WEB HOSTING

Solution 2: Manually reset the .htaccess file

If you use WordPress, you may want to reset your .htaccess to default. Make sure to copy and keep a backup of your old/current .htacess file.

This is how the default .htaccess file of WordPress looks like. Just empty the .htaccess and. Then, copy and paste this content to your .htaccess:

# BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress

Solution 3: Solve problems in plugins

To help our customers on how to fix 500 internal server error, we have to troubleshoot and try to find the cause of the problem. It’s very common to have plugins or templates generating this issue.

First of all, click on the Installed Plugins option. It’s located under Plugins.

Then, you have to try to update each plugin with such a message. To update, simply click Update now. If after updating every plugin, you still have the 500 internal server error, we recommend deactivating the plugins one by one until you find the problematic one. Simply click on Deactivate.

Solution 4: Change the theme

Sometimes a changed was applied to the theme, and some PHP file may be damaged. To fix the 500 server error, there is another possibility: changing the WordPress theme. To do that, simply go to Themes under the Appearance menu.


Then, locate a different theme, and click Activate.

How to fix this error in non-Wordpress sites

There is a vast possibility of causes of the 500 error in sites that don’t use WordPress. In this section, we will show the most common causes and solutions on how to fix the 500 internal server error problem. Most of the times, this problem is caused by issues in your .htaccess file. This file is always located in your root folder (public_html).

Solution 6 – Check the .htaccess file syntax

Simply edit this .htaccess file, and look for any misconfiguration. We recommend this .htaccess tester. This way, you can copy and paste the contents of your current .htaccess file. This site shows which lines have a bad syntax. It will highlight in red all the problematic lines, for you to fix them.

Solution 7: rename the .htaccess file

You can simply rename this file. It will deactivate it in the server. Just change its name to something like .htacess-old, for example. This way you can see the behaviour of your site without it.

Solution 8: enable error displaying in PHP

By default, PHP shows the 500 errors this way. There is an option that you can enable, in order to force PHP to show on screen the exact error message.

Simply add these lines to the beginning of your PHP file, inside the <?php and ?> tags.

error_reporting(E_ALL); ini_set('display_errors', 'On');

Now you can see the exact error message, in order to fix the 500 internal server error issue:

Solution 9: Check the error logs in the server

Lastly, if none of the previous solutions worked, we recommend checking the error logs. They will probably show you the reason of the 500 internal server error. In your cPanel control panel, open the Errors option, which is located under Metrics.

Then, all the error messages will be shown.

Conclusion

The 500 internal server error is one of the widest problems in web hosting. There are several possibilities and causes for that. We have helped many hosting customers on how to fix 500 internal server error issue so far. As we explained, there are easy and quick fixes and the toughest ones.

The last possibility is to check the log files if none of the solutions worked for you. Then, after checking the error logs, you can simply search in Google for the exact error message. For sure there will be pages showing their fixes. Least but not last, you may want to check this other article about how to use customized error pages in your site.

How to Fix 500 Internal Server Error in WordPress

Have you encountered a 500 Internal Server Error on your website? For most webmasters this can be a frustrating situation.

If you don’t manage to catch the problem early enough, your site’s SEO might take a hit. You might also lose some customers and sustain long-lasting reputational damage.

If spotted and corrected early enough, there may be little to no harm done. The real problem with 500 Internal Server Error is that you often have no clue what the root cause is.

The good news is that It is generally not a serious problem and can be easily fixed once you uncover the root cause.

If you follow all the steps we’ll show you in this guide, you will have your website back up and running in no time!

What Is a 500 Internal Server Error?

500 Internal server error example

The 500 Internal Server Error means that the server has been unable to fulfill the request due to an unexpected condition.

As a result, the page will not load and you will see a browser page outlining the error.

Chances are, if it’s down for you, it could be down for your visitors too, making this a vital error to tackle!

When you navigate to a website, you are accessing web files and content that are stored on a remote server. Your browser communicates with this server, requesting the content that you need.

In response, the server sends a HTTP response status code back to your browser, informing it of the status of the request. If successful, the code returned to the browser will be a HTTP code: 200 OK.

The server will then execute the commands, providing a copy of the relevant content to your browser.

If unsuccessful, the server might return one of two classes of codes: a HTTP 400 or 500. Broadly speaking, these aren’t single types of errors, rather, they are classes of errors.

For example, the range of HTTP 500 errors includes codes such as:

Each of which indicates a different challenge to address.

How to Resolve a 500 Internal Server Error

While a 500 Internal Server error can be annoying, it is typically easy to fix.

These errors can sometimes be caused by temporary, minor situations such as issues with your device, network, router or hosting service.

Before you get started with more technical troubleshooting, try these two basic fixes:

Reload the Page

500 Internal Server errors can often be resolved with no need for complex troubleshooting.

Sometimes the problem is a temporary situation with your hosting service, ISP or local network. Simply refreshing the web page could be enough to load the site correctly.

If that doesn’t work, perhaps try a forced refresh. This ‘forces’ the browser to request a new page from the server rather than showing you its cached version. This is the best way to assess the current situation with any website.

You can use keyboard shortcuts to force-refresh your web pages. The combinations are slightly different depending on the browser and device you are working in.

Here are the combinations to try.

In Chrome, Firefox, or Edge on a Windows powered device, hold down Ctrl+F5 or Shift+F5 or Ctrl+Shift+R.

If you’re using Chrome or Firefox on a Mac device hold down Shift+Command+R.

Clear the Cache

Clearing the browser cache is a fundamental part of website troubleshooting. Browser caches help to speed up the browsing experience by storing bits of data from websites you have visited in the past.

Sometimes that cached data can become corrupted and communication between the browser and the website you’re looking at is interrupted. One symptom of this is the 500 error.

Clearing the cache is a straightforward procedure. The steps might differ slightly depending on the browser in use.

Here are the steps to clear your cache in Firefox, Safari, Chrome and Edge:

Firefox

clear firefox cache

Open up Firefox and click on the menu button.

Select Settings, then on the left hand side panel, select Privacy and Security > Cookies and Site Data and click clear data.

A popup will appear offering the option to check/uncheck Cookies and Site Data, and Cached Web Content.

What you’re after is cached content so tick this box and leave the Cookies and Site Data box unchecked. Click on Clear Data and the cache will be cleared automatically.

Safari

The process is even simpler in Safari.

To clear the cache in Safari click on the Safari menu > Empty Cache > Empty.

Chrome

clear chrome cache

To clear the cache in Chrome, open the browser and click on the three-dots icon in the topmost right hand corner.

On the dropdown menu, click on more Tools > Clear browsing data.

This will open up a new page where you will be presented with the options of clearing Browsing History, Cookies and Other Site Data, and Cached Images and Files.

Check the box to clear Cached images and files, click on Clear data, and that’s it.

Edge

Open the browser and click on the three-dot menu at the top right hand corner. Navigate to Settings > Privacy & Services.

You will see options for clearing different classes of browsing data. Choose Cached images and files and select Clear now.

clear edge cache

Note that the precise steps may vary based on the version of the browser you are using.

If neither of these two simple fixes work, then you’re going to have to apply some more technical troubleshooting methods. Some of these may require making changes to your website or your web server.

Now would be a good time to make a backup.

Troubleshooting can be a risky process and people have been known to completely lose their data.

To avoid this, back up your data safely before you get started. Most hosting providers will keep a backup of your files, but you may not want to rely solely on this.

Read on for a complete step by step-by-step guide on how to back up your WordPress website.

How to Backup Your Website

There are several methods to back up a website. You can do this by installing a plugin, by downloading the files through FTP, or by creating a backup in cPanel.

Each method has its pros and cons and may be more or less suitable depending on your skill level.

Using a Plugin

There are a few plugins you can use to create a backup of your WordPress website. One that we recommend is Updraft.

updraft backup plugin settings

Log in into the WordPress backend using the wp-admin path. Navigate to Plugins > Add new and search for Updraft.

Install and activate the plugin.

Once activated, a popup will appear, prompting you to ‘Press here to start’. You can also click on Settings under Updraft.

There are quite a few options under Settings which allow you to determine things like backup frequency, which files to include in a backup, how to save your backup, and so on. Set them up as you need.

Once you have made your choices, it’s time to put the plugin to work!

Still on the Updraft Settings page, click on the Backup/restore tab and then on Backup Now.

That’s it! Your website will be backed up.

For more detailed guidance, checkout our step-by-step guide on how to back up your WordPress website.

Backing Up Manually Using FTP/SFTP

File Transfer Protocol (FTP), is the traditional way of uploading and downloading data or content to or from your website. Secure File Transfer Protocol (SFTP) does the same thing but using extra layers of security.

To use this method, you will begin by connecting to your FTP server through an FTP client. The most popular one is Filezilla.

FTP allows for a transfer of files between two computers over a network. In this case, you will be uploading your data from your web server to your computer.

Begin by downloading the Filezilla Client and installing it on your desktop.

Filezilla interface

Next, you will need to have the FTP server address, along with your username and password. These details are usually provided by your hosting service.

You will then need to set the port to port 21 if you are using FTP, and port 22 if you are using SFTP.

Once your FTP client is all set up, the files and folders that make up your WordPress website will be visible for download.

All you will then have to do is drag and drop them into folders on your computer.

Use cPanel/Ask your Host

Most hosts provide default backup tools in cPanel. If you know your way around cPanel, this is a good option.

cPanel backup wizard

Login into cPanel and navigate to Files > Backup Wizard > cPanel Backup > Backup > Full Backup > Download a Full Account Backup > Generate Backup.

How to Fix the Internal Server Error in WordPress Step by Step

Once you have created a backup of your files, it will be time to turn to serious WordPress troubleshooting.

Here are the steps to follow, along with different methods for troubleshooting an internal 500 error on your WordPress website.

Turn On Debugging

Once you’ve gotten your web files safely backed up, it’s time to get into the nitty gritty of resolving the 500 Internal Server Error.

As there could be a wide range of causes for this error message, the first step is to turn on debugging mode.

In debugging mode, WordPress will provide more specific warnings and error messages that help to clarify the cause of the 500 Internal Server Error.

Turning on debugging mode will require a tiny bit of coding. Before you begin, you’ll want to have a fail-safe if things go wrong.

When editing a WordPress core file like the wp-config file, the best practice is to create a backup version.

To do this, first create a copy of the wp-config file.

To find the file, enter cPanel and navigate to Files > File Manager > public_html > wp-config.php.

Go to cPanel file manager

Next, rename the file by changing its extension. In this case, you would be changing .php to .anything.

Most webmasters like to use .old but it doesn’t matter what you choose.

If things go wrong for any reason, all you have to do is first delete the modified file, then rename the copied file. In this case, that would mean turning your new wp-config.old file back to the default wp-config.php.

Once you have safely created a backup wp-config file, you’ll be ready to turn on debugging mode in WordPress.

Right click on the wp-config folder, to edit it within cPanel.

edit WP config file

When the file opens up, scroll to the bottom of the page, where you can add the following line of code:

editing wp config file

Once done, don’t forget to save the change.

Once you’re done debugging, you will need to reverse this. No need to delete the code. Just replace true with false like so:

Again, remember to save the change.

Switch Themes

A lot of the time, when things go wrong with a WordPress website, it is down to plugin/theme upgrade issues or compatibility issues. The first step in troubleshooting will usually be to start by changing your theme to one of the default WordPress themes like Twenty Twenty-One.

To do this, navigate over to Appearance > Themes. Click on the theme you would like to install, in this case, Twenty Twenty-One, and activate it.

If the problem persists, you will progress to troubleshoot your plugins.

Deactivate All Plugins

To check if the problem is with your plugins, follow a similar process. In your WordPress backend, navigate to Plugins on the side menu.

Deactivate all plugins and reactivate them one after the other to see which one triggers the problem. Test between each activation to see which plugin causes the 500 error to reappear.

As soon as the error reappears, deactivate the plugin you just activated and test again. If the error disappears, you have found the cause of the error.

If neither changing your theme or plugin resolves the situation, the problem might lie a little deeper under the hood.

Check the .htaccess File

The .htaccess file is a file that controls much of how your users interact with your website. Web servers generally run on two types of software. These are NGINX and Apache, with Apache being the more commonly used.

If your web server runs on Apache, your website will need a .htaccess file that provides instructions to Apache on how access to your site should be granted.

Errors in .htaccess configuration are a common cause of 500 internal server errors.

To check if the error is caused by the .htaccess file, change its name from .htaccess to something else to prevent the server from recognizing and loading it. If this resolves the error message, then you should repair the file or create another.

The .htaccess file can be found in the public_html folder.

To find and edit it, you can either use cPanel or FTP. If you’re using cPanel, you will need to navigate to File Manager > public_html.

Right click on the .htaccess file and select Edit.

Below is what a .htaccess file should look like. If yours is in need of repair, simply paste in this code via FTP/SFTP or access it through the cPanel File Manager.

If you cannot find a .htaccess file in your public_html folder, you may need to create a new one. This is easy to do.

create new file in cPanel file manager

At the top left-hand corner of your screen, click on + File. In the pop up that appears, enter .htaccess as the New File Name.

Once created, copy and paste in the code above and save the file as .htaccess..

Increase the PHP Memory Limit

When browsers send requests to a web server, some PHP memory is required to execute this process. Sometimes, a 500 Internal Server error occurs because of scripts that use up too much memory before they complete.

To fix this, you can increase the amount of PHP memory available for processing requests while you contact your web hosting service to help with finding and fixing the troublesome scripts.

There are a number of ways to increase PHP memory for a WordPress website as you will see below. By now, you will have learned how to work in these files. All you’ll have to do is add in little bits of code here and there.

Edit the .htaccess file

You’ve already learned how to work with .htaccess earlier. To increase the PHP memory allocation for your website, simply open the .htaccess file in a text editor, and add the following code:

Then save the change.

You can also use 128M or 256M if required. There is no guarantee that this will work as some web hosts limit memory from the server side, which ignores the setting you’re changing. Not all hosts do this, which is why we suggest it here.

Edit the Wp-Config File

You can find the wp-config file for your website in cPanel or using FTP. Download the wp-config file from your root directory, open it in a text editor, and add the following code:

And save the change.

Increase Memory Allocation in PHP.ini

A final method of increasing your WordPress websites’s PHP memory allocation is by increasing the memory allocation from the PHP.ini file. The PHP.ini file is a PHP configuration file that controls things like execution time, memory and much more.

If you’re using shared hosting you won’t be able to edit your PHP.ini file. If you have dedicated hosting or a virtual hosting plan, you might be able to edit your PHP.ini file in cPanel.

Ordinarily, you will find the PHP.ini file stored in your root folder. You can also edit this file manually.

In both cases, first find the PHP.ini file in the root directory of your WordPress installation. As we advised earlier, to create a safety net in case things go wrong, copy a new version of the PHP.ini file and save the old one with a different extension such as .old.

Next, download the file and open it in a text editor. Paste in the configuration values you would like to use on your website–in this case, if you’re trying to set the memory limit at 128 megabytes, you would include a line of code like this:

If you’re working in cPanel, simply save this file and delete the backup. If you’re working with FTP, upload the file and that should fix the issue.

Check File Permissions

Another possible cause of an internal 500 error is a file permissions error. File permissions determine who can read, write and execute functions within your WordPress code.

Incorrect permissions are a security threat but they can also lead to 500 Internal Server error messages.

If things have gone awry on your WordPress website, check your permissions files to see if the the following WordPress recommended settings are still in place:

  • wp-admin: 755
  • wp-content: 755
    • wp-content/themes: 755
    • wp-content/plugins: 755
    • wp-content/uploads: 755
  • wp-config.php: 644
  • .htaccess: 644
  • All other files – 644

To check these, you can simply right click on each file in the public_html folder in cPanel or in your FTP client, and click on change permissions.

cPanel user permissions

If the contents of your version of this file look different, update it with these settings. As always, don’t forget to save your changes.

Ask Your Host

If you have tried all the previous steps and nothing has worked, you may need to report the error to your hosting service provider. They will usually be able to accurately troubleshoot any errors, and in many cases, will carry out fixes themselves.

Be sure to provide as many details as you can including what actions you suspect may have triggered the 500 Internal Server Error, as well as the steps you have taken to resolve it.

There are a couple more steps you may take if you would like to complete the troubleshooting process on your own.

Check the Database Connection

An error in establishing a database connection is another potential cause of an internal 500 server error. This can happen for a number of reasons. For example, incorrect database login credentials, a corruption of your WordPress database, or a problem with the server.

A broken database connection will be a little more challenging to resolve as you will not have access to either the front or back end of your WordPress installation.

To resolve this, you will need to access your WordPress files via FTP/SFTP or cPanel.

Next, check the php.ini file to confirm that your database login credentials are correct. As we mentioned earlier, you won’t be able to access this file if you’re using a shared hosting plan. If you are, you may need to ask your hosting service for some help.

If you aren’t, you can find the php.ini file in your cPanel, in the public_html folder.

These credentials include:

  • MySQL name
  • MySQL database surname
  • MySQL database password
  • My SQL hostname

You should have these credentials recorded somewhere from when you first set up WordPress.

If these are in order, the problem may lie with a corrupted database.

Fixing a corrupt database is straightforward. Be aware, though, that in rare circumstances, this process can cause you to lose data.

enable WP_ALLOW_REPAIR

You will have to enable database repair mode by adding a bit of code into the wp-config.php file:

You can do this from your cPanel or via FTP.

Navigate to the public_html folder in file manager, right click on the wp_config file and click Edit.

Scroll down to the bottom of the page–right before the line that says “That’s all, stop editing! Happy blogging.”, and paste in the code above.

Once this is done, visit the following address in your browser:

https://yourdomain.com/wp-admin/maint/repair.php

Once here, you will have the options of enabling a WordPress repair, or optimizing the database.

We recommend that you choose the repair option.

Reinstall WordPress

Reinstalling WordPress or reverting to an error-free version of your WordPress installation is a method that will help you get around the problem without really solving it.

If you have gone through all the previous methods without success, you may want to priorities getting your site back online and this method is the quickest way of doing it.

If you opt for this path, then be sure to build your website the right way from the beginning. Properly configured websites are less likely to run into 500 Internal Server errors, at least, not frequently!

Preventing a 500 Internal Server Error

armor stock image

There isn’t an exhaustive list of things that could cause a 500 Internal Server error but the following tips should help you avoid the majority of them

These are our top three tips:

Use a Reliable Hosting Service

As you might have realized by now, a lot of what could go wrong with a 500 Internal Server error may happen on your web server, out of your control.

Simply choosing a web hosting provider that provides faster servers and more bandwidth can help. You should also choose a web host that offers responsive and technically skilled customer support.

Use Properly Coded Themes and Plugins

Not all WordPress themes and plugins are built using high-quality code or industry best practices. Astra is, which is why it is so popular with web developers around the world. For a smooth WordPress experience, try Astra!

Use a Staging Environment

Major changes to your website should be tested in a staging environment before being implemented on your live site.

This will allow you to catch any issues with themes of plugins before they have a chance to cause a 500 Internal Server error on your live site.

Final Thoughts

The 500 Internal Server error can cause much distress but now you know what to do when it happens.

Like most technical troubleshooting, it’s largely a case of a process of elimination, trying a fix, testing it and then moving on to another. It’s slow and steady but it works!

Remember to create regular backups of your WordPress website and don’t wait for issues to crop up before you do!

With the steps we’ve shown you, you will overcome any instances of this frustrating error like a pro.

If you have had to deal with a 500 Internal Server error in the past, let us know which of these solutions worked for you. We’d love to hear what tips you might have!

500 Error¶

The 500 status code, or "Internal Server Error," means that the server cannot process the request for an unknown reason. Sometimes this code will appear when more specific 5xx errors are more appropriate.

The most common causes for this error are server misconfiguration (e.g. a malformed file), missing packages (e.g. trying to execute a PHP file without PHP installed properly), permission or ownership changes, improperly configured , a PHP upgrade, etc. Anything that the server doesn't know how to handle can trigger a 500 error in a website. The impact of the error can vary based on the event that triggered it.

Before proceeding with the troubleshooting steps, it is a good idea to determine whether the issue is LiteSpeed-specific, or whether it happens with Apache, too.

Does it Occur with Apache?¶

If your server is running on an Apache control panel, such as cPanel or Plesk, there is an easy way to determine whether an issue is caused by your LiteSpeed server:

  1. Temporarily switch to Apache
  2. Repeat the steps that originally led to the issue.

Are you able to reproduce the error under Apache?

NO¶

If the error could not be triggered under Apache, then the problem is likely to be a LiteSpeed server issue. Please open a ticket from your client area or email and provide as many details as possible, so that we may assist you.

YES¶

If Apache experiences the same problems, then the issue is not a LiteSpeed Web Server issue.

Switch back to LiteSpeed Web Server, and keep reading! Even though it is not a server problem, we have provided the following troubleshooting documentation that we hope will help you to find the solution.

Determine the Scope¶

To troubleshoot a 500 error, first check whether the error affects just one site or every site in the server. Depending on the impact of the error, you can debug further. If only one domain is affected, it can be pin-pointed to a specific script error or permission issue. If multiple domains show a 500 error, it could be due to some server wide setting change or update.

You can check the server , or PHP error log (normally located where the PHP script is running) to see if there is any hint of the error. During the troubleshooting, you may want to ensure PHP error reporting is on in . Please revert the settings back when you're done with debuging.

If you only want to apply the above for a single domain for quick testing, you can add the following PHP override to the domain's to enable the logging. Simply comment out or remove the lines after testing.

Please be aware that not all 500 errors appear in the logs and it is common not to see any hint in log files. This makes troubleshooting more difficult.

Here are some of the common reasons, and a few examples, which may help you during the troubleshooting process.

Permission or Ownership Changes¶

Permission or ownership changes may cause 500 error.

For example, to enable the LiteMage extension in your Magento installation through SSH, you will need to run a a non-root user. However, if you run the command incorrectly as the root user, the Magento front end may return 500 instantly. The fix is to reverse file ownership and permissions back to the original user.

phpinfo.php owned by root instead of user¶

Sometimes we need to check phpinfo page during the troubleshooting. When ssh login as root to server, go to document root and create phpinfo.php, the file will be owned by instead of .

Sometimes it may return 500 error when accessing if some restriction set there but not always.

The server error may show the following:

Changing the info.php to be owned by will generally fix the issue.

Faulty .htaccess¶

There is a huge range of things can do and it isn't difficult to use, however, if you do not enter the syntax correctly it can result in a Server 500 Error.

Example 1¶

For example,

Will cause a 500 error. But change it to
and that will fix the issue.

Example 2¶

can not be used in .htacess and it will cause 500 error for Apache, While LSWS will ignore the unsupported directive instead of giving 500 error.

For example, the following should not be used in .htaccess.

instead, you can create .htaccess under /wp-admin/ and place diretive there.

To confirm whether a misconfiguration in is the cause of the 500 Internal Server error, either remove or rename the .htaccess file temporarily and then try to reload the page.

Example 3¶

The following "Alias" directive in .htaccess will cause 500 on Apache (LSWS will ignore it without returning 500) since "Alias" directive is not allowed in .htaccess.

Example 4¶

Syntax is wrong for the followintg directive:

which will lead to Too many arguments to directive error in error_log:

The correct syntax is the following and it should fix the 500 error for Apache:

Example 5¶

Syntax wrong for the following:

It should be:

Example 6¶

and are for mod_php handler. Most of the time php-fpm or lsphp will be used and mod_php has been deprecated most of the time. When you use or , Apache will return 500 error. However, lsphp supports php override in .htaccess without any problem and there is no 500 error when running LSWS.

Different level of Rewrite rules misplaced to the wrong level¶

Per virtual host rewrite rules (rewrite rules in Apache virtual host configuration) and per directory rewrite rules (rewrite rules in .htaccess) are different. When placing the same rules to the wrong place, it may cause 500 error.

For example, the following works in .htaccess:

Putting the same thing in Apache VirtualHost config doesn’t work at all:

Apache doesn’t tell you why it doesn’t work. It just doesn’t work. You most likely will get an Error 500 status with a message in the logs that looks like this:

Incorrect Rewrite Rules misplace in differernt directories¶

The following rewrite rules in subfolder is incorrect and it will cause 500 for LiteSpeed.

The correct rule should be:

Bad PHP Code¶

Bad PHP code will bring a website to 500 immediately.

For example, the right syntax should be:

If the is removed somehow:
It will bring the website to 500 immediately. This is only one example. Many times, wrong PHP syntax will lead to a 500 error.

Another example is:

A typing error in phpinfo page , which should be , will lead to 500 error.

PHP Short open tag used when not being enabled in php.ini¶

When PHP parses a file, it looks for the opening and closing tags and , which tell PHP to start and stop interpreting the code between them. Parsing in this manner allows PHP to be embedded in all sorts of different documents, as everything outside of a pair of opening and closing tags is ignored by the PHP parser.

PHP also allows for the short open tag . However, it is only available if it has been enabled using in php.ini. If it has not been enabled in php.ini, a short open tag on a page will return a 500 error.

PHP Code with wrong php configuration settings¶

Sometimes, a 500 error may be not easy to locate. If you move to and move to , and the 500 error still happens, it might mean there is something wrong in the PHP code. That can be hard to find.

We experienced a case with WHMCS. Someone placed an incorrect setting in :

is an incorrect value for the PHP setting. Rather, it is meant for the setting. should be either /, or /. We changed it to , and that fixed the 500 error.

CloudLinux LVE Limit Reached¶

When using CloudLinux, If the site is limited by memory or process limits, then the user may receive 500 errors because the server cannot execute the script. [[https://docs.cloudlinux.com/index.html?lve.html

Internal Server Error Help, 500 Error

This article will discuss the commonly known causes of the 500 Internal Server Error and the general troubleshooting steps in resolving them.

Please click the links below to jump to a section.

Are you getting a 500 Internal Server Error page on your WordPress website? Please check out the article How to Fix the Internal Server Error in WordPress for instructions on what you should do.

What does 500 Internal Server Error mean?

An Internal Server Error (ISE), also known as a 500 error, is not specific only to WordPress. This error can be caused by a PHP function not working as intended, whereas a database error causes 500 errors. Both errors can, however, be resolved in the same way. Finding the cause of a 500 Error and then resolving it is often a matter of trial and error.

The 500 Internal Server Error is presented in several ways, which may include the following:

  • 500 Error
  • 500 Internal Server Error
  • 500. That's an error
  • HTTP 500 Internal Error
  • HTTP 500 - Internal Server Error
  • HTTP Error 500
  • Internal Server Error
  • Temporary Error (500)


Basic Troubleshooting

"Is your domain properly connected to your web host?"

One of the basics of troubleshooting web pages is ensuring that the domain (your website name) is active and properly connected to your web host (your hosting plan). Ensuring that requires you to check your DNS records. Let's think of it as checking the "bridge" connecting your website and your hosting server.

Please check out these articles for more information on checking your DNS records.

"Did you already try clearing/deleting your browser's cache and cookies?"

This may be a simple step, but most website error pages are caused by cache. The cache is a temporarily stored memory that helps your browser load a webpage faster. Sometimes it causes a problem when websites are updated as the web files saved in the cache may conflict with what is actually in the website. And clearing cache fixes most website issues like that, including loading or formatting problems.

Check the following article on how to clear your browser's cache and cookies.

"Done with the domain check and clearing cache, but the 500 Error page is still there?"

If so, let's go ahead and try a more advanced approach. First, let us check your website's error logs.

Error logs are very useful in finding out the real cause of any website issue. Once you find out the cause, you can proceed with further troubleshooting.

To check the error logs:

  1. Log in to cPanel.
  2. In the Metrics section, click on the Errors icon.

    cPanel Metrics

    The logs will display the last 300 error messages in reverse order. 

Once you determine the cause of the 500 Error through your error logs, we can proceed with advanced troubleshooting below.



What are the other possible causes of the 500 Internal Server Error?

Here are some of the commonly known causes.

File permissions error

Your website has files and folders inside your web host, and each of these will have its permission settings regardless of the application used to build the site. Permissions can allow our server computer to write and edit your files. Along with that, some files need to be protected from writing and editing as a security measure.

To fix the 500 Error page caused by permissions error, you must ensure that your website files and folders have the correct permission settings.  

  • WordPress website files must be 644 or 640
  • Directories and WordPress folders must be 755.
  • Executable scripts within the cgi-bin folder must be 755.
  • Images, media, and text files (like HTML) must be 755 or 644.
Click here to know how to check and change file permissions

To check your file permissions:

  1. Log in to cPanel.
  2. Navigate to the Files section, then click on the File Manager.cPanel File Manager
  3. Click your website's document root. We will use thepublic_html folder in this example, which is your primary domain's document root.

    public_html folder

  4. To view all files, including the hidden ones (dotfiles), click Settings located in the top-right corner.

    File Manager - Settings button

  5. Select Show Hidden Files (dotfiles) in the pop-up window, then click Save.

    Show Hidden Files

  6. All files, including the hidden files, should now be displayed. Check the Permissions column on the right. The set of numbers you will see should match the permissions listed above.

    cPanel File Permissions

  7. If the file permission doesn't match the default permissions, double-click the set of numbers and enter the correct permissions.

    Change Permissions

  8. Once done, click Save.

For more information about file permissions, please visit these support articles:



Corrupted or broken .htaccess file

A .htaccess file is an Apache file that tells a website how to function. As one of a site's core files, it is important to ensure that the .htaccess file exists and is properly configured. The script or code for a .htaccess is written depending on the CMS or application used to build the website. If the .htaccess is missing or misconfigured, you may need to upload or create a new .htaccess file manually.

To troubleshoot a 500 Error page caused by the .htaccess, you will have to open your website's .htacces file and check the scripts within by comparing it to the article:

If there are custom scripts in the .htaccess, you may need to contact your web developer for assistance as HostGator's Support cannot assist with customized scripts and coding that are unique for your website.

If you find an unusual script in your .htaccess, you can comment out a line by adding # to the beginning of that particular line. For example, if the code in the .htaccess file looks like:

Then, try commenting it out like so:

Alternatively, you can create a new default .htaccess file instead.

Here are helpful articles to guide you in editing and creating a new .htaccess file.

If you cannot determine which line is the problem, then comment out every line.

After commenting out a line(s), refresh the site to see if the issue has been resolved. If it has, that confirms that the issue was in that particular line of code in the .htaccess file. If the issue has not been resolved, continue troubleshooting by commenting out additional lines and reloading the website.



Exceeding resources, nothing in the error logs

Too many processes may be causing the 500 error in the server queue.

With SSH (shell) access, you can view the processes running on your account. Type this command:

Or type the following command to view a specific user's account. (Be sure to replace the username with the actual username.):

Type the following command to kill the specific process once the process ID (pid). (Be sure to replace pid with the actual process ID.):



Faulty third-party themes or plugins (for WordPress websites)

Faulty themes or plugins may also cause a 500 Internal Server Error page for WordPress websites. Before looking into faulty themes, you may need to find out which plugin is causing the 500 error. A 500 error page (possibly) generated by a plugin can be fixed by disabling and enabling the plugins one by one. Once the faulty plugin is identified, you may need to deactivate it. Ensure to inform to create a backup of the website first before making any changes to the website. 

It is always a good practice to create a backup of the website and database before making any changes to the website.

One of the recommended ways of activating/deactivating plugins is through the WordPress dashboard. As a reference, here is a support article you can use, How to Install/Uninstall WordPress Plugins.

If you confirmed that none of the WordPress plugins is causing the issue, it might be the WordPress theme itself. Please change the WordPress theme through your dashboard.

Need further assistance? Please contact us via phone or Live Chat so we can assist you!

Internal server error 500 on WHM – How to fix it

While accessing WHM panel or 500 internal server error error cpanel, users at times notice an “Internal server error 500” message. This usually happens when one of the cPanel processes is failing.

As a part of our Server Management Services, we help our Customers with WHM related requests regularly.

Let us today analyze the causes and the fix for this error.


 

What causes WHM Internal server error 500

We recently received a request from one of our customers that they are receiving an “internal server error” as shown below while accessing WHM:

WHM Internal server error 500

This error can trigger in a number of scenarios. For instance, while using ConfigServer WHM plugins,  while setting up two-factor authentication,  or randomly when they try to login to WHM or cPanel interface.

The exact reason for this error may vary based on the particular situation, 500 internal server error error cpanel. However, this error usually happens due to one of the cPanel processes failing to load or still running in the background.

Let us now discuss two different solutions for this error.
 

How to fix WHM Internal server error 500

As we said earlier, the exact steps to fix the error may vary based on the reason for the error. To have a better idea on what is the reason, our Support engineers check the cPanel error log:

This error log helps to identify the reason for the error. In most cases running a cPanel update helps to fix the error. For this,  initially, we need to Stop the cPanel service with the command below:

Now our Support Engineers update cPanel/WHM with the command:

This command only updates the control panel software, 500 internal server error error cpanel. Once the update is over, we can start the services by issuing this line:

 

While using ConfigServer WHM plugins

ConfigServer plugins need access to some IP addresses. If they are not whitelisted on the server, it is possible for them to get blocked. This in turn can trigger the “500 error”.

Thus to fix the error, we need to remove them from the blocklist and then whitelist it by adding them in the ” /etc/csf.allow” file

 
[Need any further assistance with WHM error? – We’re available 24*7]

Conclusion

In short, the “Internal server error 500″ message” while accessing WHM panel or cPanel usually happens when one of the cPanel processes is failing. Today we saw how our Support Engineers fix this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

SEE SERVER ADMIN PLANS

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

500 Error¶

The 500 status code, or "Internal Server Error," means that the server cannot process the 500 internal server error error cpanel for an unknown reason. Sometimes this code will appear when more specific 5xx errors are more 500 internal server error error cpanel most common causes for this error are server misconfiguration (e.g. a malformed file), missing packages (e.g. trying to execute a PHP file without PHP installed properly), permission or ownership changes, improperly configureda PHP upgrade, etc. Anything that the server doesn't know how to handle can trigger a 500 error in a website. The impact of the error can vary based on the event that triggered it.

Before proceeding with the troubleshooting steps, it is a good idea to determine whether the issue is LiteSpeed-specific, or whether it happens with Apache, too.

Does it Occur with Apache?¶

If your server is running on an Apache control panel, such as cPanel or Plesk, there is an easy way to determine whether an issue is caused by your LiteSpeed server:

  1. Temporarily switch to Apache
  2. Repeat the steps that originally led to the issue.

Are you able to reproduce the error under Apache?

NO¶

If the error could not be triggered under Apache, then the problem is likely to be a 500 internal server error error cpanel server issue. Please open a ticket from your client area or email and provide as many details as possible, so that we may assist you.

YES¶

If Apache experiences the same problems, then the issue is 500 internal server error error cpanel a LiteSpeed Web Server issue.

Switch back to LiteSpeed Web Server, and keep reading! Even though it is not a server problem, we have provided the following troubleshooting documentation that we hope will help you to find the solution.

Determine the Scope¶

To troubleshoot a 500 error, first check whether the error affects just one site or every site in the server. Depending on the impact of the error, you can debug further. If only one domain is affected, it can be pin-pointed to a specific script error or permission issue. If multiple domains show a 500 error, it could be due to some server wide setting change or update.

You can check the server or PHP error log (normally located where the PHP script 500 internal server error error cpanel running) to see if there is any hint of the error. During the troubleshooting, you may want to ensure PHP error reporting is on in. Please revert the settings back when you're done with debuging.

If you only want to apply the above for a single domain for quick testing, you can add the following PHP override to the domain's to enable the logging. Simply comment out or remove the lines after testing, 500 internal server error error cpanel.

Please be aware that not all 500 errors appear in the logs and it is common not to see any hint in log files, 500 internal server error error cpanel. This makes troubleshooting more difficult.

Here are some of the common reasons, and a few examples, which may help you during the troubleshooting process.

Permission or Ownership Changes¶

Permission or ownership changes may cause 500 error.

For example, to enable the LiteMage extension in your Magento installation through SSH, you will need to run a a non-root user. However, if you run the command incorrectly as the root user, the Magento front end may return 500 instantly. The fix is to reverse file ownership and permissions back to the original user.

phpinfo.php owned by root instead of user¶

Sometimes we need to check phpinfo page during the troubleshooting. When ssh msi 990fxa-gd80 ff error as root to server, go to document root and create phpinfo.php, the file will be owned by instead of.

Sometimes it may return 500 error when accessing if some restriction set there but not always.

The server error may show the following:

Changing the info.php to be owned by will generally fix the issue.

Faulty .htaccess¶

There is a huge range of things can do and it isn't difficult gameguard error error code 111 use, however, if you do not enter the syntax correctly it can result in a Server 500 Error.

Example 1¶

For example,

Will cause a 500 error. But change it to
and that will fix the issue.

Example 2¶

can not be used in .htacess and it will cause 500 error for Apache, While LSWS will ignore the unsupported directive instead of giving 500 error.

For example, the following should not be used in .htaccess.

instead, you can create .htaccess under /wp-admin/ and place diretive there.

To confirm whether a misconfiguration in is the cause of the 500 Internal Server error, either remove or rename the .htaccess file temporarily and then try to reload the page.

Example 3¶

The following "Alias" directive in .htaccess will cause 500 on Apache (LSWS will ignore it without returning 500) since "Alias" directive is not allowed in .htaccess.

Example 4¶

Syntax is wrong for the followintg directive:

which will lead vrlservice.exe start error Too many arguments to directive error in error_log:

The correct syntax is the following and it should fix the 500 error for Apache:

Example 5¶

Syntax wrong for the following:

It should be:

Example 6¶

and are for mod_php handler. Most of the time php-fpm or lsphp will be used and mod_php has been deprecated most of the time. When you use orApache will return 500 error. However, lsphp supports php override in .htaccess without any problem and there is no 500 error when running LSWS.

Different level of Rewrite rules misplaced to the wrong level¶

Per virtual host rewrite rules (rewrite rules in Apache virtual host configuration) and per directory rewrite rules (rewrite rules in .htaccess) are different. When placing the same rules to the wrong place, it may cause 500 error.

For example, the following works in .htaccess:

Putting the same thing in Apache VirtualHost config doesn’t work at all:

Apache doesn’t tell you why it doesn’t work. It just doesn’t work. You most likely will get an Error 500 status with a message in the logs that looks like this:

Incorrect Rewrite Rules misplace in differernt directories¶

The following rewrite rules in subfolder is incorrect and it will cause 500 for LiteSpeed.

The correct rule should be:

Bad PHP Code¶

Bad PHP code will bring a website to 500 immediately.

For example, the right syntax should be:

If the is removed somehow:
It will bring the website to 500 immediately. This is only one example. Many times, wrong PHP syntax will lead to a 500 error.

Another example 500 internal server error error cpanel

A typing error in phpinfo pagewhich should bewill lead to 500 error.

PHP Short open tag used when not being enabled in php.ini¶

When PHP parses a file, it looks for the opening and closing tags andwhich tell PHP to start and stop interpreting the code between them. Parsing in this manner allows PHP to be embedded in all sorts of different documents, as everything outside of a pair of opening and closing tags is ignored by the PHP parser.

PHP extreme hardcore speedcore terror allows for the short open tag. However, it is only available if it has been enabled using in php.ini. If it has not been enabled in php.ini, a short open tag on a page will return a 500 error.

PHP Code with wrong php configuration settings¶

Sometimes, a 500 error may be not easy to locate. If you move to and move toand the 500 error still happens, it might mean there is something wrong in the PHP code. That can be hard to find.

We experienced a case with WHMCS. Someone placed an incorrect setting in :

is an incorrect value for the PHP setting. Rather, it is meant for the setting. should be either /, or /. We changed it toand that fixed the 500 error.

CloudLinux LVE Limit Reached¶

When using CloudLinux, If the site is limited by memory or process limits, then the user may receive 500 errors because the server cannot execute the script. [[https://docs.cloudlinux.com/index.html?lve.html

Internal Server Error Help, 500 Error

This article will discuss the commonly known causes of the 500 Internal Server Error and the general troubleshooting steps in resolving them.

Please click the links below to jump to hero and the terror 1988 section.

Are you getting a 500 Internal Server Error page on your WordPress website? Please check out the article How to Fix the Internal Server Error in WordPress for instructions on what you should do.

What does 500 Internal Server Error mean?

An Internal Server Error (ISE), also known as a 500 error, is not specific only to WordPress. This error can be caused by a PHP function not working as intended, whereas a database error causes 500 errors. Both errors can, however, be resolved in the same way. Finding the cause of error 017 undefined symbol dialogid 500 Error and then resolving it is often a matter of trial and error.

The 500 Internal Server Error is presented in several ways, which may include the following:

  • 500 Error
  • 500 Internal Server Error
  • 500. That's an error
  • HTTP 500 Internal Error
  • HTTP 500 - Internal Server Error
  • HTTP Error 500
  • Internal Server Error
  • Temporary Error (500)


Basic Troubleshooting

"Is your domain properly connected to your web host?"

One of the basics of troubleshooting web pages is 500 internal server error error cpanel that the domain (your website name) is active and properly connected to your web host (your hosting plan). Ensuring that requires you to check your DNS records. Let's think of it as checking the "bridge" connecting your website and your hosting server.

Please check out these articles for more information on checking your DNS records.

"Did you already try clearing/deleting your browser's cache and cookies?"

This may be a simple step, but most website error pages are caused by cache. The cache is a temporarily stored memory that helps your browser load a webpage faster. Sometimes it causes a problem when websites are updated as the web files saved in the cache may conflict with what is actually in the website. And clearing cache fixes most website issues like that, including loading or formatting problems.

Check the following article on how to clear your browser's cache and cookies.

"Done with the domain check and clearing cache, but the 500 Error page is still there?"

If so, let's go ahead and try a more advanced approach. First, let us check your website's error logs.

Error logs are very useful in finding out the real cause of any website issue. Once you find out the cause, you can proceed with further troubleshooting.

To check the error logs:

  1. Log in to cPanel.
  2. In the Metrics section, 500 internal server error error cpanel, click on the Errors icon.

    cPanel Metrics

    The logs will display the last 300 error messages in reverse order. 

Once you determine the cause of the 500 Error through your error logs, we can proceed with advanced troubleshooting below.



What are the other possible causes of the 500 Internal Server Error?

Here are some of the commonly known causes.

File permissions error

Your website has files and folders inside your web host, and each of these will have its permission settings regardless of the application used to build the site. Permissions can allow our server computer to write and edit your files. Along with that, some files need to be protected from writing and editing as a security measure.

To fix the 500 Error page caused by permissions error, you must ensure that your website files and folders have the correct permission settings.  

  • WordPress website files must be 644 or 640
  • Directories and WordPress folders must be 755.
  • Executable scripts within the cgi-bin folder must be 755.
  • Images, media, and text files (like HTML) must be 755 or 644.
Click here to know how to check and change file permissions

To check your file permissions:

  1. Log in to cPanel.
  2. Navigate to the Files section, then click on the File Manager.cPanel File Manager
  3. Click your website's document 500 internal server error error cpanel. We will use thepublic_html folder in this example, which is your primary domain's document root.

    public_html folder

  4. To view all files, including the hidden ones (dotfiles), click Settings located in the top-right corner, 500 internal server error error cpanel.

    File Manager - Settings button

  5. Select Show Hidden Files (dotfiles) in the pop-up window, then click Save.

    Show Hidden Files

  6. All files, including the hidden files, should now be displayed. Check the Permissions column on the right. The set of numbers you will see should match the permissions listed above. edatetimeerror date is less than minimum alt="cPanel File Permissions" src="https://content.hostgator.com/img/cpanel_new_file_permissions.png" width="600">

  7. If the file permission doesn't match the default permissions, double-click the set of numbers and enter the correct permissions.

    Change Permissions

  8. Once done, click Save.

For more information about file permissions, please visit these support articles:



Corrupted or broken .htaccess file

A .htaccess file is an Apache file that tells a website how to function. As one of a site's core files, it is important to ensure that the .htaccess file exists and is properly configured. The script or code for a .htaccess is written depending on the CMS or application used to build the website. If the .htaccess is missing or misconfigured, you may need to upload or create a new .htaccess file manually.

To troubleshoot a 500 Error page caused by the .htaccess, you will have to open your website's .htacces file and check the scripts within by comparing it to the article:

If 500 internal server error error cpanel are custom scripts in the .htaccess, you may need to contact your web developer for assistance as HostGator's Support cannot assist with customized scripts and coding that are unique for your website.

If you find an unusual script in your .htaccess, you can comment out a line by adding # to the beginning of that particular line. For example, if the code in the .htaccess file looks like:

Then, try commenting it out like so:

Alternatively, you can create a new default .htaccess file instead.

Here are helpful articles to guide you in editing and creating a new .htaccess file.

If you cannot determine which line is the problem, then comment out every line.

After commenting out a line(s), refresh the site to see if the issue has been resolved. If it has, that confirms that the issue was in that particular line of code in the .htaccess file. If the issue has not been resolved, continue troubleshooting by commenting out additional lines and reloading the website.



Exceeding resources, nothing in the error logs

Too many processes may be causing the 500 error in the server queue.

With SSH (shell) access, you can view the processes running on your account. Type this command:

Or type the following command to view a specific user's account. (Be sure to replace the username with the actual username.):

Type the following command to kill the specific process once the process ID (pid). (Be sure to replace pid with the actual process ID.):



Faulty third-party themes or plugins (for WordPress websites)

Faulty themes or plugins may also cause a 500 Internal Server Error page for WordPress websites. Before looking into faulty themes, you may need to find out which plugin is causing the 500 error. A 500 error page (possibly) generated by a plugin can be fixed by disabling and enabling the plugins one by one. Once the faulty plugin is identified, you may need to deactivate it. Ensure to inform to create a backup of the website first before making any changes to the website. 

It is always a good practice to create a backup of the website and database before making any changes to the website.

One of the recommended ways of activating/deactivating plugins is through the WordPress dashboard. As a reference, here is a support article you can use, How to Install/Uninstall WordPress Plugins.

If you confirmed that none of the WordPress plugins is causing the issue, it might be the WordPress theme itself. Please change the WordPress theme through your dashboard.

Need further assistance? Please contact us via phone or Live Chat so we can assist you!

How to Fix 500 Internal Server Error in WordPress

Have you encountered a 500 Internal Server Error on your website? For most webmasters this can be a frustrating situation.

If you don’t manage to catch the problem early enough, your site’s SEO might take a hit. You might also lose some customers and sustain long-lasting reputational damage.

If spotted and corrected early enough, there may be little to no harm done. The real problem with 500 Internal Server Error is that you often have no clue what the root cause is.

The good news is that It is generally not a serious problem and can be easily fixed once you uncover the root cause.

If you follow all the steps we’ll show you in this guide, you will have your website back 500 internal server error error cpanel and running in no time!

What Is a 500 Internal Server Error?

500 Internal server error example

The terrorismin vastainen komitea Internal Server Error means that the server has been unable to fulfill the request due to an unexpected condition.

As a result, the page will not load and you will see a browser page outlining the error.

Chances are, if it’s down for you, it could be down for your visitors too, making this a vital error to tackle!

When you navigate to a website, 500 internal server error error cpanel, you are accessing web files and content that are stored on a remote server. Your browser communicates with this server, requesting the content that you need.

In response, the server sends a HTTP response status code back to your browser, informing it of the status of the request. If successful, the code returned to the browser will be a HTTP code: 200 OK.

The server will then execute the commands, providing a copy of the relevant content to your browser.

If unsuccessful, the server might return one of two classes of codes: a HTTP 400 or 500. Broadly speaking, these aren’t single types of errors, 500 internal server error error cpanel, rather, they are classes of errors.

For example, the range of HTTP 500 errors includes codes such as:

Each of which indicates a different challenge to address.

How to Resolve a 500 Internal Server Error

While a 500 Internal Server error can be annoying, it is typically easy to fix.

These errors can sometimes be caused by temporary, minor situations such as issues 500 internal server error error cpanel your device, network, router or hosting service.

Before you get started with more technical troubleshooting, 500 internal server error error cpanel these two basic fixes:

Reload the Page

500 Internal Server errors can often be resolved with no need for complex troubleshooting.

Sometimes the problem is a temporary situation with your hosting service, ISP or local network. Simply refreshing the web page could be enough to load the site correctly.

If that doesn’t work, perhaps try a forced refresh. This ‘forces’ the browser to request a new page from the server rather than showing you its cached version. 500 internal server error error cpanel is the best way to assess the current situation with any website.

You can use keyboard shortcuts to force-refresh your web pages. The combinations are slightly different depending on the browser and device you are working in.

Here are the combinations to try.

In Chrome, Firefox, or Edge on a Windows powered device, hold down Ctrl+F5 or Shift+F5 or Ctrl+Shift+R.

If you’re using Chrome or Firefox on a Mac device hold down Shift+Command+R.

Clear the Cache

Clearing the browser cache is a fundamental part of website troubleshooting, 500 internal server error error cpanel. Browser caches help to speed up the browsing experience by storing bits of data from websites you have visited in the past.

Sometimes that cached data can become corrupted and communication mp fail, error code the browser and the website you’re looking at is interrupted. One symptom of this is the 500 error.

Clearing the cache is a straightforward procedure. The steps might differ slightly depending on the browser in use.

Here are the steps to clear your cache in Firefox, Safari, Chrome and Edge:

Firefox

clear firefox cache

Open up Firefox and click on the menu button.

Select Settings, then on the left hand side panel, select Privacy and Security > Cookies and Site Data and click clear data.

A popup will appear offering the option to check/uncheck Cookies and Site Data, and Cached Web Content.

What you’re after is cached content so tick this box and leave the Cookies and Site Data box unchecked. Click on Clear Data and the cache will be cleared automatically.

Safari

The process is even simpler in Safari.

To clear the cache in Safari click on the Safari menu > Empty Cache > Empty.

Chrome

clear chrome cache

To clear the cache in Chrome, open the browser and click on the 500 internal server error error cpanel icon in the topmost right hand corner.

On the dropdown menu, click on more Tools > Clear browsing data.

This will open up a new page where you will be presented with the options of clearing Browsing History, Cookies and Other Site Data, and Cached Images and Files.

Check the box to clear Cached images and files, click on Clear data, and that’s it.

Edge

Open the browser and click on the three-dot menu at the top right hand corner. Navigate to Settings > Privacy & Services.

You will see options for clearing different classes of browsing data. Choose Cached images and files and select Clear now.

clear edge cache

Note that the precise steps may vary based on the version of the browser you are using.

If neither of these two simple fixes work, then you’re going to have to apply some more technical troubleshooting methods. Some of these may require making changes to your website or your web server.

Now would be a good time to make a backup.

Troubleshooting can be a risky process and people have been known to completely lose their data.

To avoid this, back up your data safely before you get started. Most hosting providers will keep a backup of your files, but you may not want to rely solely on this.

Read on for a complete step by step-by-step guide on how to back up your WordPress website.

How to Backup Your Website

There are several methods to back up a website. You can do this by installing a plugin, by downloading the files through FTP, or by creating a backup in cPanel.

Each method has its pros and cons and may be more or less suitable depending on your skill level.

Using a Plugin

There are a few plugins you can use to create a backup of your 500 internal server error error cpanel website. One that we recommend is Updraft.

updraft backup plugin settings

Log in into the WordPress backend using the wp-admin path. Navigate to Plugins > Add new and search for Updraft.

Install and activate the plugin.

Once activated, a popup will appear, prompting you to ‘Press here to start’. You can also click on Settings under Updraft.

There are quite a few options under Settings which allow you to determine things like backup frequency, which files to include in a backup, how to save your backup, and so on. Set them up as you need.

Once you have made your choices, it’s time to put the plugin to 500 internal server error error cpanel on the Updraft Settings page, click 500 internal server error error cpanel the Backup/restore tab and then on Backup Now.

That’s it! Your website will be backed up.

For more detailed guidance, checkout our step-by-step guide on how to back up your WordPress website.

Backing Up Manually Using FTP/SFTP

File Transfer Protocol (FTP), is the traditional way of uploading and downloading data or content to or from your website. Secure File Transfer Protocol (SFTP) does the same thing but using extra layers of security.

To use this method, you will begin by connecting to your FTP server through an FTP client. The most popular one is Filezilla.

FTP allows for a transfer of files between two computers over 500 internal server error error cpanel network. In this case, you will be uploading your data from your web server to your computer.

Begin by downloading the Filezilla Client and installing it on your desktop.

Filezilla interface

Next, you will need to have the FTP server address, along with your username and password. These details are usually provided by your hosting service.

You will then need to set the port to port 21 if you are using FTP, and port 22 if you are using SFTP.

Once your FTP client is all set up, the files and folders that make up your WordPress website will be visible for download.

All you will then have to do is drag and drop them into folders on your computer.

Use cPanel/Ask your Host

Most hosts provide default backup tools in cPanel. If you know your way around cPanel, this is a good option.

cPanel backup wizard

Login hp designjet error code 86 01 cPanel and navigate to Files > Backup Wizard > cPanel Backup > Backup > Full Backup > Download a Full Account Backup > Generate Backup.

How to Fix the Internal Server Error in WordPress Step by Step

Once you have created a backup of your files, it will be time to turn to serious WordPress troubleshooting.

Here are the steps to follow, along with different methods for troubleshooting an internal 500 error on your WordPress website.

Turn On Debugging

Once you’ve 500 internal server error error cpanel your web files safely backed up, it’s time to get into the nitty gritty of resolving the 500 Internal Server Error.

As there could be a wide range of causes for this error message, the first step is to turn on debugging mode.

In debugging mode, WordPress will provide more specific warnings and error messages that help to clarify the cause of the 500 Internal Server Error.

Turning on debugging mode will require a tiny bit of coding. Before you begin, you’ll want to have a fail-safe if things go wrong.

When editing a WordPress core file like the wp-config file, the best practice is to create a backup version.

To do this, first create a copy of the wp-config file.

To find the file, enter cPanel and navigate to Files > File Manager > public_html > wp-config.php.

Go to cPanel file manager

Next, rename the file by changing its extension. In this case, you would be changing .php to .anything.

Most webmasters like to use .old but it doesn’t matter what you choose.

If things go wrong for any reason, all you have to do is first delete the modified file, then rename the copied file. In this case, that would mean turning your new wp-config.old file back to the default wp-config.php.

Once you have safely created a backup wp-config file, you’ll be ready to turn on debugging mode in WordPress.

Right click on the wp-config folder, to edit it within cPanel.

edit WP config file

When the file opens up, scroll to the bottom of the page, where you can add the following line of code:

editing wp config file

Once done, don’t forget to save the change.

Once you’re done debugging, you will need to reverse this, 500 internal server error error cpanel. No need to delete the code. Just replace true with false like so:

Again, remember to save the change.

Switch Themes

A lot of the time, when things go wrong with a WordPress website, it is down to plugin/theme upgrade issues or compatibility issues. The first step in troubleshooting dcpflics error connecting usually be to start by changing your theme 500 internal server error error cpanel one of the default WordPress themes like Twenty Twenty-One.

To do this, navigate over to Appearance > Themes. Click on the theme you would like to install, in this case, Twenty Twenty-One, and activate it.

If the problem persists, you will progress to troubleshoot your plugins.

Deactivate All Plugins

To check if the problem is with your plugins, follow a similar process. In your WordPress backend, navigate to Plugins on the side menu.

Deactivate all plugins and reactivate them one after the other to see which one triggers the problem. Test between each activation to see which plugin causes the 500 error to reappear.

As soon as the error reappears, deactivate the plugin you just activated and test again. If the error disappears, you have found the cause of the error.

If neither changing your theme or plugin resolves the situation, the problem might lie a little deeper under the hood.

Check the .htaccess File

The .htaccess file is a file that controls much of how your users interact with your website. Web servers generally run on two types of software. These are NGINX and Apache, with Apache being the more commonly used.

If your web server runs on Apache, your website will need a .htaccess file that provides instructions to Apache on how access to your site should be granted.

Errors in .htaccess configuration are a common cause of 500 internal server errors.

To check if the error is caused by the .htaccess file, change its name from .htaccess to something else to prevent the server from recognizing and loading it. If this resolves the error message, then you should repair the file or create another.

The .htaccess file can be found in the public_html folder.

To find and edit it, you can either use cPanel or FTP. If you’re using cPanel, you will need to navigate to File Manager > public_html.

Right click on the .htaccess file and select Edit.

Below is what a .htaccess file should look like. If yours is in need of repair, simply paste in this code via FTP/SFTP or access it through the cPanel File Manager.

If you cannot find a .htaccess file in your public_html folder, you may need to create a new one. This is easy to do.

create new file in cPanel file manager

At the top left-hand corner of your screen, click on + File. In the pop up that appears, enter .htaccess as the New File Name.

Once created, copy and paste in the code above and save the file as .htaccess.

Increase the PHP Memory Limit

When browsers send requests to a web server, some PHP memory is required to execute this process. Sometimes, a 500 Internal Server error occurs because of scripts that use up too much memory before they complete.

To fix this, you can increase the amount of PHP memory available for processing requests while you contact your web hosting service to help with finding and fixing the troublesome scripts.

There are a number of ways to increase PHP memory for a WordPress website as you will see below. By now, you will have learned how to work in these files. All you’ll have to do is add in little bits of code here and there.

Edit the .htaccess file

You’ve already learned how to work with .htaccess earlier. To increase the PHP syntax error 2 flash film allocation for command error bad argument type stringp nil website, simply open the .htaccess file in a text editor, and add the following code:

Then save the change.

You can also use 128M or 256M if required. There is no guarantee that this will work as some web hosts limit memory from the server side, which ignores the setting you’re changing. Not all hosts do this, which is 500 internal server error error cpanel we suggest it here.

Edit the Wp-Config File

You can find the wp-config file for your website in cPanel or using FTP. Download the wp-config file from your root directory, open it in a text editor, and add the following code:

And save the change.

Increase Memory Allocation in PHP.ini

A final method of increasing your WordPress websites’s PHP memory allocation is by increasing the memory allocation from the PHP.ini file. The PHP.ini file is a PHP configuration file that controls things like execution time, memory and much more.

If you’re using shared hosting you won’t be able to edit your PHP.ini file. If you have dedicated hosting or a virtual hosting plan, you might be able to edit your PHP.ini file in cPanel.

Ordinarily, you will find the PHP.ini file stored in your root folder. You can also edit this file manually.

In both cases, twonky syntax error unexpected find the PHP.ini file in the root directory of your WordPress installation. As we advised earlier, to create a safety net in case things go wrong, copy a new version of the PHP.ini file and save the old one with a different extension such as .old.

Next, download the file and open it in a text editor. Paste in the configuration values you would like to use on your website–in this case, if you’re trying to set the memory limit at 128 megabytes, you would include a line of code like this:

If you’re working in cPanel, simply save this file and delete the backup. If you’re working with FTP, upload the file and that should fix the issue.

Check File Permissions

Another possible cause of an internal 500 error is a file permissions error. File permissions determine who can read, write and execute functions within your WordPress code.

Incorrect permissions are a security threat but they can also lead to 500 Internal Server error messages.

If things have gone awry on your WordPress website, check your permissions files to see if the the following WordPress recommended settings are still in place:

  • wp-admin: 755
  • wp-content: 755
    • wp-content/themes: 755
    • wp-content/plugins: 755
    • wp-content/uploads: 755
  • wp-config.php: 644
  • .htaccess: 644
  • All other files – 644

To check these, you can simply right click on each file in the public_html folder in cPanel or in your FTP client, 500 internal server error error cpanel, and click on change permissions.

cPanel user permissions

If the contents of your version of this file look different, update it with these settings. As always, don’t forget to save your changes.

Ask Your Javascript error vkapp is not defined you have tried all the previous steps and nothing has worked, you may need to report the error to your hosting service provider. They will usually be able to accurately troubleshoot any errors, and in many cases, will carry out fixes themselves.

Be sure to provide as many details as you can including what actions you suspect may have triggered the 500 Internal Server Error, as well as the steps you have taken to resolve it.

There are a couple more steps you may take if you would like to complete the troubleshooting process on your own.

Check the Database Connection

An error samsung b5722 java error establishing a database connection is 500 internal server error error cpanel potential cause of an internal 500 server error. This can happen for a number of reasons. For example, incorrect database login credentials, a corruption of your WordPress database, or a problem with the server.

A broken database connection will be a little more challenging to resolve as you will not have access to either the front or back end of your WordPress installation.

To resolve this, you will need to access your WordPress files via FTP/SFTP or cPanel.

Next, check the php.ini file to confirm that your database login credentials are correct. As we mentioned earlier, you won’t be able to access this file if you’re using a shared hosting plan. If you are, you may need to ask your hosting service for some help.

If you aren’t, you can find the php.ini file in your cPanel, in the public_html folder.

These credentials include:

  • MySQL name
  • MySQL database surname
  • MySQL database password
  • My SQL hostname

You should have these credentials recorded somewhere from when you first set up WordPress.

If these are in order, the problem may lie with a corrupted database.

Fixing a corrupt database is straightforward. Be aware, though, that in rare circumstances, this process can cause you to lose data.

enable WP_ALLOW_REPAIR

You will have to enable database repair mode by adding a bit of code into the wp-config.php file:

You can do this from your cPanel or via FTP.

Navigate to the public_html folder in file manager, right click on the wp_config file and click Edit.

Scroll down to the bottom of the page–right before the line that says “That’s all, stop editing! Happy blogging.”, and paste in the code above.

Once this is done, visit the following address in your browser:

https://yourdomain.com/wp-admin/maint/repair.php

Once here, 500 internal server error error cpanel, you will have the options of enabling a WordPress repair, or optimizing the database.

We recommend that you choose the repair option.

Reinstall WordPress

Reinstalling WordPress or reverting to an error-free version of your WordPress installation is a method that will help you get around the problem without really solving it.

If you have gone through all the previous methods without success, you may want to priorities getting your site back l2 freya runtime error and this method is the quickest way of doing it.

If you opt for this path, then be sure to build your website the right way from the beginning. Properly configured websites are less likely to run into 500 Internal Server errors, at least, not frequently!

Preventing a 500 Internal Server Error

armor stock image

There isn’t an exhaustive list of things that could cause a 500 Internal Server error but the following tips should help you avoid the majority of them

These are our top three tips:

Use a Reliable Hosting Service

As you might have realized by now, a lot of what could go wrong with a 500 Internal Server error may happen on your web server, out of your control.

Simply choosing a web hosting provider that provides faster servers and more bandwidth can help. You should also choose a web host that offers responsive and technically skilled customer support.

Use Properly Coded Themes and Plugins

Not all WordPress themes and plugins are built using high-quality code or industry best practices. Astra is, gcc error jump to label fpermissive is why it is so popular with web developers around the world. For a smooth WordPress experience, try Astra!

Use a Staging Environment

Major changes to your website should be tested in a staging environment before being implemented on your live site.

This will allow you to catch any issues with themes of plugins before they have a chance to cause a 500 Internal Server error on your live site.

Final Thoughts

The 500 Internal Server error can cause much distress but now you know what to do when it happens.

Like most technical troubleshooting, it’s largely a case of a process of elimination, trying a fix, testing it and then moving on to another. It’s slow and steady 500 internal server error error cpanel it works!

Remember to create regular backups of your WordPress website and don’t wait for issues to crop up before you do!

With the steps we’ve shown you, you will overcome any instances of this frustrating error like a pro.

If you have had to deal with a 500 Internal Server error in the past, let us know which of these solutions worked for you. We’d love to hear what tips you might have!

How to Fix a 500 Internal Server Error on Your WordPress Site

The dreaded 500 internal error 1013 iphone 3gs error. It always seems to come at the most inopportune time and you’re suddenly left scrambling to figure out how to get your WordPress site back online. Trust us, we’ve all been there. Other errors that behave similarly that you 500 internal server error error cpanel have also seen include the frightening error establishing a database connection and the dreaded white screen of death. But from the moment your site goes down, you’re losing visitors and customers. Not to mention it simply looks bad for your brand.

Today we’re going to dive into the 500 internal server error and walk you through some ways to get your site back online quickly, 500 internal server error error cpanel. Read more below about what causes this error and what you can do to prevent it in the future.

500 Internal Server Error (Most Common Causes):

500 Internal server error in WordPress can be caused by many things. If you’re experiencing one, there’s a high chance one (or more) of the following elements is causing the issue:

  • Browser Cache.
  • Incorrect database login credentials.
  • Corrupted database.
  • Corrupted files in your WordPress installation.
  • Issues with your database server.
  • Corrupted WordPress core files.
  • Corrupted .htaccess file and PHP memory limit.
  • Issues with third-party plugins and themes.
  • PHP timing out or fatal PHP errors with third-party plugins.
  • Wrong file and folder permissions.
  • Exhausted PHP memory limit on your server
  • Corrupted or broken .htaccess file.
  • Errors in CGI and Perl script.

Check Out Our Ultimate Guide to Fixing the 500 Internal Server Error

What is a 500 Internal Server Error?

The Internet Engineering Task Force (IETF) defines the 500 Internal Server Error as:

The 500 (Internal Server Error) 500 internal server error error cpanel code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

When you visit a website your browser sends a request over to the server where the site is hosted. The server takes this request, processes it, and sends back the requested resources (PHP, HTML, CSS, etc.) along with an HTTP header. The HTTP also includes what they call an HTTP status code. A status code is a way to notify you about the status of the request. It could be a 200 status code which means “Everything is OK” or a 500 status code which means something has gone wrong.

There are a lot of different types of 500 status error codes (500, 501, 502, 503, 504, etc.) and they all mean something different. In this case, a 500 internal server error indicates that the server encountered an unexpected condition that prevented it from fulfilling the request (RFC 7231, section 6.6.1).

500 internal server error in WordPress

500 Internal Server Error Variations

Due to the various web servers, operating systems, and browsers, a 500 internal server error can present itself in a number of different ways. But they are all communicating the same thing. Below are just a couple of the many different variations you might see on the web:

    • “500 Internal Server Error”
    • “HTTP 500”
    • “Internal Server Error”
    • “HTTP 500 – Internal Server Error”
    • “500 Error”
    • “HTTP Error 500”
    • “500 – Internal Server Error”
    • “500 Internal Server Error. Sorry something went wrong.”
    • “500. 500 internal server error error cpanel an error. There was an error. Please try again later. That’s all we know.”
    • “The website cannot display the page – HTTP 500.”
    • “Is currently unable to handle this request. HTTP ERROR 500.”

You might also see this message accompanying it:

The server encountered an internal error or misconfiguration and was unable to complete your an error occurred at /admin/build/views/ajax/ config item. Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.

Internal Server Error

Other times, you might simply see a blank white screen. When dealing with 500 internal server errors, this is actually quite common in browsers like Firefox and Safari.

500 internal server error in Firefox

Bigger brands might even have their own custom 500 internal server error messages, such as this one from Airbnb.

Airbnb 500 internal server error

Here is another creative 500 server error example from the folks over at pioneer error 30 src="https://kinsta.com/wp-content/uploads/2017/12/500-internal-server-error-example-2.png" alt="readme 500 internal server error" width="1471" height="931">

Even the mighty YouTube isn’t safe from 500 internal server errors.

500 internal server error on YouTube

If it’s an IIS 7.0 (Windows) or higher server, they have additional HTTP status 49 err 64003d5 hp printer error to more closely indicate the cause of the 500 error:

  • 500.0 – Module or ISAPI error occurred.
  • 500.11 – Application is shutting down on the web server.
  • 500.12 – Application is busy restarting on the web server.
  • 500.13 – Web server is too busy.
  • 500.15 – Direct requests for global.asax are not allowed.
  • 500.19 – Configuration data is invalid.
  • 500.21 – Module not recognized.
  • 500.22 – An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
  • 500.23 – Asus error beep codes ASP.NET httpHandlers configuration does not apply in Managed An error has occurred preparing the patch mode.
  • 500.24 – An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
  • 500.50 – A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
  • 500.51 – A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
  • 500.52 – A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
  • 500.53 – A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
    500.100 – Internal ASP error.

500 Errors Impact on SEO

Unlike 503 errors, which are used for WordPress maintenance mode and tell Google to check back at a later time, a 500 error can have a negative impact on SEO if not fixed right away. If your site is only down for say 10 minutes and it’s being crawled consistently a lot of times the crawler will simply get the page delivered from cache. Or Google might not even have a chance to re-crawl it before it’s back up. In this scenario, you’re completely fine.

However, if the site is down for an extended period of time, say 6+ hours, then Google might see the 500 error as a site level issue that needs to be addressed. This could impact your rankings. If you’re worried about repeat 500 errors you should figure out why they are happening to begin with. Some of the solutions below can help.

How to Fix the 500 Internal Server Error

Where should you start troubleshooting when you see a 500 internal server error on your WordPress site? Sometimes you might not even know where to begin. Typically 500 errors are on the server itself, but from our experience, these errors originate from two things, the first is user error (client-side issue), and the second is that there is a problem with the server. So we’ll dive into a little of both.

Check 302 http error codes these common causes and ways to fix the 500 internal server error and get back up and running in no time.

1. Try Reloading the Page

This might seem a little obvious to some, but one of the 500 internal server error error cpanel and first things you should try when encountering a 500 internal server error is to simply wait a minute or so and reload the page (F5 or Ctrl + F5). It could be that the host or server is simply overloaded and the site will come right back. While you’re waiting, you could also quickly try a different browser to rule that out as an issue.

Another thing you can do is to paste the website into downforeveryoneorjustme.com. This website will tell you if the site is down or if it’s a problem on your side. A tool like this checks the HTTP status code that is returned from the server. If it’s anything other than a 200 “Everything is OK” then it will return a down indication.

downforeveryoneorjustme

We’ve also noticed that sometimes this can occur immediately after you update a plugin or theme on your WordPress site. Typically this is on hosts that aren’t set up properly. What happens is they experience a temporary timeout right afterward. However, things usually resolve themselves in a couple of seconds and therefore refreshing is all you need to do.

2. Clear Your Browser Cache

Clearing your browser cache is always another good troubleshooting step before diving into deeper debugging on your site. Below are instructions on how to clear cache in the various browsers:

3. Check Your Server Logs

You should also take advantage of your error logs. If you’re a Kinsta client, you can easily see errors in the log viewer in the MyKinsta dashboard. This can help you quickly narrow down the issue, especially if it’s resulting from a plugin on your site.

Want to know how we increased our traffic over 1000%?

Join 20,000+ others who get our weekly newsletter with insider WordPress tips!

Subscribe Now
Check error logs for 500 internal server errors

If your host doesn’t have a logging tool, you can also enable WordPress debugging mode by adding the following code to your wp-config.php file to enable logging:

The logs are typically located in the 500 internal server error error cpanel directory, 500 internal server error error cpanel. Others, like here at Kinsta might have a dedicated folder called “logs”.

WordPress error logs folder (SFTP)

You can also check the log files in Apache and Nginx, which are commonly located here:

  • Apache: /var/log/apache2/error.log
  • Nginx: /var/log/nginx/error.log

If you’re a Kinsta client you can also take advantage of our analytics tool to get a breakdown of the total number of 500 errors and see how often and when they are occurring. This can help you troubleshoot if this is an ongoing issue, or perhaps something that has resolved itself.

Response analysis 500 error breakdown

If orca error data1.cab 500 error is displaying because of a fatal PHP error, you can also try enabling PHP error reporting. Simply add the following code to the file throwing the error. Typically you can narrow down the file in the console tab of Google Chrome DevTools.

And you might need to also modify your php.ini file with the following:

4. Error Establishing a Database Connection

500 internal server errors can also occur from a database connection error. Depending upon your browser you might see different errors. But both will generate a 500 HTTP status code regardless in your server logs.

Below is an example of what an “error establishing a database connection” message looks like your browser. The entire page is blank because no data can be retrieved to render the page, as the connection is not working properly. Not only does this break the front-end of your site, but it will also prevent you from accessing your WordPress dashboard.

Example of error establishing a database connection

So why exactly does this happen? Well, here are a few common reasons below.

  • The most common issue is that your database login credentials are incorrect. Your WordPress site uses separate login information to connect to its MySQL database.
  • Your WordPress database is corrupted. With so many moving parts with themes, plugins, and users constantly deleting and installing them, sometimes databases get corrupted. This can be borland internal compiler error f1004 to a missing or individually corrupted table, or perhaps some information was deleted by accident.
  • You may have corrupt files in your WordPress installation. This can even happen sometimes due to hackers.
  • Issues with your database server. A number of things could be wrong on the web hosts end, such as the database being overloaded from a traffic spike or unresponsive from too many concurrent connections. This is actually quite common with shared hosts as they are utilizing the same resources soap-error encoding object has no property a lot of users on the same servers.

Check out our in-depth post on 500 internal server error error cpanel to fix the error establishing a database connection in WordPress.

5. Check Your Plugins and Themes

Third-party plugins and themes can easily cause 500 internal server errors. We’ve seen all types cause them here at Kinsta, from slider plugins to ad rotator plugins. A lot of times you should see the error immediately after installing something new or running an update. This is one reason why we always recommend utilizing a staging environment for updates or at least running updates one by one. Otherwise, if you encounter a 500 internal server error you’re suddenly scrambling to figure out which one caused it.

A few ways you can troubleshoot this is by deactivating all your plugins. Remember, you won’t lose any data if you simply deactivate a plugin. If you can still access your admin, a quick way to do this is to browse to “Plugins” and select “Deactivate” from the bulk actions menu. This will disable all of your plugins.

Deactivate all plugins

If this fixes the issue you’ll need to find the culprit. Start activating them one by one, reloading the site after each activation. When you see the 500 internal server error return, you’ve found the misbehaving plugin. You can then reach out to the plugin developer for help or post a support ticket in the WordPress repository.

If you can’t login to WordPress admin you can FTP into your server and rename your plugins folder to something like plugins_old. Then check your site again. If it works, 500 internal server error error cpanel, then you will need to test each plugin one by one. Rename your plugin folder back to “plugins” and then rename each plugin folder inside of if it, one by one, until you find it. You could also try to replicate this on a staging site first.

Rename plugin folder

Always makes sure your plugins, themes, and WordPress core are up to date. And check to ensure you are running a supported version of PHP. If it turns out to be a conflict with bad code in a plugin, you might need to bring in a WordPress developer to fix the issue.

6. Reinstall WordPress Core

Sometimes WordPress core files can get corrupted, especially on older sites. It’s actually quite easy to re-upload just the core of WordPress without impacting your plugins or themes. We have an in-depth guide with 5 different ways to reinstall WordPress. And of course, make sure to take a backup before proceeding. Skip to one of the sections below:

7. Permissions Error

A permissions error with a file or folder on your server can also cause a 500 internal server error to occur. Here are some typical recommendations for permissions error 1000 office 14 it comes to file and folder permissions in WordPress:

  • All files should be 644 (-rw-r–r–) or 640.
  • All directories should be 755 (drwxr-xr-x) or 750.
  • No directories should ever be given 777, even upload directories.
  • Hardening: wp-config.php could also be set to 440 or 400 to prevent other users on the server from reading it.

See the WordPress Codex article on changing file permissions for a more in-depth explanation.

You can easily see your file permissions with an FTP client (as seen below). You could also reach out to your WordPress host support team and ask them to quickly GREP file permissions on your folders and files to ensure they’re setup properly.

File permissions SFTP

8. PHP Memory Limit

A 500 internal server error could also be caused by exhausting the PHP memory limit on your server. You could try increasing the limit. Follow the instructions below on how to change this limit in cPanel, Apache, your php.ini file, and file.

Increase PHP Memory Limit in cPanel

If you’re running on a host that uses cPanel, you can easily change this from the UI. Under Software click on “Select PHP Version.”

Select PHP version

Click on “Switch to PHP Options.”

Switch to PHP options

You can then click on the attribute and change its value. Then click on “Save.”

Increase PHP memory limit in cPanel

Increase PHP Memory Limit in Apache

The file is a special hidden file that contains various settings you can use to modify the server behavior, right down to a directory specific level. First login to your site via FTP or SSH, take a look at your root directory and see if there is a file there.

.htaccess file

If there is you can edit that file to add the necessary code for increasing the PHP memory limit. Most likely it is set at 64M or below, you can try increasing this value.

Increase PHP Memory Limit in php.ini File

If the above doesn’t work for you might try editing your file. Log in to your site via FTP or SSH, go to your site’s root directory and open or create a file.

php.ini file

If the file was already there, search for the three settings and modify them if necessary. If you just created the file, or the settings are nowhere to be found you can paste the code below. You can modify of course the values to meet your needs.

Some shared hosts might also require that you add the suPHP directive in your file for the above file settings to work. To do this, edit your file, 500 internal server error error cpanel, also located at the root of your site, and add the following 500 internal server error error cpanel towards the top of the file:

If the above didn’t work for you, it could be that your host has the global settings locked down and instead have it configured to utilize files. To edit your file, login to your site via FTP or SSH, 500 internal server error error cpanel, go to your site’s root directory and open or create a file. You can then paste in the following code:

Increase PHP Memory Limit in wp-config.php

The last option is not one we are fans of, but if all else fails you can give it a go. First, log in to your site via FTP or SSH, and locate your wp-config.php file, which is typically in the root of your site.

wp-config.php file

Add the following code to the top of your file:

You can also ask your host if you’re running into memory limit issues. We utilize the Kinsta APM tool and other troubleshooting methods here at Kinsta to help clients narrow down what plugin, query, or script might be exhausting the limit. You can also use your own custom New Relic key from your own license.

Debugging with New Relic

9. Problem With Your .htaccess File

Kinsta only uses Nginx, but if you’re using a WordPress host that is running Apache, it could very well be that your file has a problem or has become corrupted. Follow the steps below to recreate a new one from scratch.

First, 500 internal server error error cpanel, log in to your site via FTP or SSH, and rename your file to .

Rename .htaccess file

Normally to recreate this file you can simply re-save your permalinks in WordPress, 500 internal server error error cpanel. However, if you’re in the middle of a 500 internal server error you most likely can’t access your WordPress admin, so this isn’t an option. Therefore socket error #0 indy can create a new file and input the following contents. Then upload it to your rnq 10053 error the WordPress Codex for canon error 5200 reset examples, such as a default file motorola e770 critical error 84 multisite.

10. Coding or Syntax Errors in Your CGI/Perl Script

500 errors being caused by errors in CGI and Perl is a lot less common than it used to be. Although it’s still worth mentioning, especially for those using cPanel where there are a lot of one-click CGI scripts still being used. As AEM on Stack Overflow says:

CGI has been replaced by a vast variety of web programming technologies, 500 internal server error error cpanel, including PHP, various Apache extensions like mod_perl, Java of various flavors and frameworks including Java EE, Struts, Spring, etc, Python-based frameworks like Django, Ruby on Rails and many other Ruby frameworks, and various Microsoft technologies.

Here are a few tips when working with CGI scripts:

  • When editing, always used a plain text editor, such as Atom, Sublime, or Notepad++. This ensures they remain in ASCII format.
  • Ensure correct permissions of chmod 755 are used on CGI scripts and directories.
  • Upload your CGI scripts in ASCII mode (which you can select in your FTP editor) into the cgi-bin directory on your server.
  • Confirm that the Perl modules you require for your script are installed and supported.

11. Server Issue (Check With Your Host)

Finally, because 500 internal server errors can also occur powernow-k8 bios error no psb PHP timing out or fatal PHP errors with third-party plugins, you can always check with your WordPress host. Sometimes these errors can be difficult to troubleshoot without an expert. Here are just a few common examples of some errors java.rmi.unmarshalexception error unmarshaling return header trigger 500 HTTP status codes on the server that might have you scratching your head.

We monitor all client’s sites here at Kinsta and are automatically notified when these types of errors occur. This allows us to be pro-active and start fixing the issue right away. We also utilize LXD managed hosts and orchestrated LXC software containers for each site. This means that every WordPress site is housed in its own isolated container, which has all of the software resources required to run it (Linux, Nginx, PHP, MySQL). The resources are 100% private and are not shared with anyone else or even your own sites.

PHP timeouts could also occur from the lack of PHP workers, although typically these cause 504 errors, not 500 errors, 500 internal server error error cpanel. These determine how many simultaneous requests your site can handle at a given time. To put it simply, each uncached request for your website is handled by a PHP Worker.

When PHP workers are already busy on a site, they start to build up a queue. Once you’ve reached your limit of PHP workers, the queue starts to push out older requests which could result in 500 errors or incomplete requests. Read our in-depth article about PHP workers.

Monitor Your Site

If you’re worried about these types of errors happening on your site in the future, you can also utilize a tool like updown.io to monitor and notify you immediately if they occur. It periodically sends an HTTP HEAD request to the URL of your choice. You can simply use your homepage. The tool allows you to set check frequencies of:

  • 15 seconds
  • 30 seconds
  • 1 minute
  • 2 minutes
  • 5 minutes
  • 10 minutes

It will send you an email if and when your site goes down. Here is an example below.

Email notification of 500 error

This can be especially useful 500 internal server error error cpanel you’re trying to debug a faulty plugin or are on a shared host, who tend to overcrowd their servers. This can give you proof of how often your site might actually be doing down (even during the middle of the night). That’s why we always recommend going with a managed WordPress host. Make sure to check out oki c5850 fatal error 03 post that explores the top 9 reasons to choose managed WordPress hosting.

Summary

500 internal server errors are always frustrating, but hopefully, now you 500 internal server error error cpanel a few additional ways to troubleshoot them to quickly get your site back up and running. Remember, typically these types of errors are caused by third-party plugins, fatal PHP errors, database connection issues, problems with your .htaccess file or PHP memory limits, and sometimes PHP timeouts.

Was there anything we missed? Perhaps you have another tip on troubleshooting 500 internal server errors. If so, let us know below in the comments.


Save time, costs and maximize site performance with:

  • Instant help from WordPress hosting experts, 24/7.
  • Cloudflare Enterprise integration.
  • Global audience reach with 34 data centers worldwide.
  • Optimization with our built-in Application Performance Monitoring.

All of that and much more, in one plan with no long-term contracts, assisted migrations, and a 30-day-money-back-guarantee, 500 internal server error error cpanel. Check out our plans or talk to sales to find the plan that’s right for you.

The message 500 Internal Server Error is one of the most frustrating messages a website owner can encounter. If you are lucky, it is followed by an explanation such as “Connection Timed Out” or “Please check your internet connection and try again”.

However, if it is not followed by an explanation, you may just see a blank page where you cannot continue.

If you are a WordPress user, you will at some point come across the term “500 Internal Server Error”. This error is triggered by your WordPress website whenever there is an internal problem. If this is the case with your website, you can be sure that something has gone wrong with the configuration of your web hosting provider’s server.

If you have accessed a particular website and received the dreaded 500 Internal Server Error message, do not panic! This usually means that the server cannot process the request properly. There are things you can do to fix this problem. You can find these solutions here.

You may want to leave this task to an experienced developer. But you do not have to. If you are one of those who, like me, want to fix things immediately, then you are in the right place.

Are you ready to get to the bottom of this? OK, First you need to understand the error, why it is a server error and how to fix it.

What is a 500 Internal Server Error?

500 Internal Server Error image - 500 Internal Server Error Solved Learn To Fix It😁 Speed

(500-internal-server-error-example-image-562×340)

First of all, you need to know that this internal server error 500 is an HTTP error and that there are several status codes associated with the Hypertext Transfer Protocol AKA as HTTP. You can see the complete list of status codes here:

10 Status Code Definitions.

Today we will deal with one of the worst status codes: the status code 500 Internal Server Error. This HTTP status tells you that the server hosting the website you are accessing is unable to process such a request. There are many causes for this error, but in general, it is best 500 internal server error error cpanel investigate the server itself.

What causes a 500 Internal Server Error?

There are many reasons why a 500 Internal Server Error may occur, some of which are: 

  • No permission to access the website
  • You cannot connect to the server hosting the website
  • There is a configuration problem with your network
  • Excessive PHP timeout
  • PHP memory limit exceeded
  • Incompatibility with the PHP version

Fixing 500 Internal Server Error WordPress

Fixing 500 Internal Server Errors can be a challenge, even for an IT professional. They occur when the server is busy or can not handle all your requests at once, and they are usually caused by problems configuring the hosting server that runs most websites. To fix this 500 HTTP protocol server error, we first need to locate it. This 500 internal server error error cpanel a troubleshooting strategy. So let us begin.

Troubleshooting 500 Internal Server Error in WordPress.

Learning to fix the 500 Internal Server Error - 500 Internal Server Error Solved Learn To Fix It😁 Speed

Troubleshooting 500 Internal Server Error in WordPress can be a daunting task, to say the least. The first thing you should do is check that your server is working and operational. If the server is up and running, you should check if roland internal error 0000015 hosting provider has a customer support hotline. The problem is that sometimes the hosting provider’s support team takes too long to respond and you need to fix the 500 error now. That’s why we created this 500 Internal Server Error Troubleshooting Guide.

In this guide, we will troubleshoot your 500 Internal Server Error in five steps:

  1. Check if plugins are causing the problem
  2. We will check the installation of the theme
  3. Check if the .htaccess file is corrupted 
  4. Ask help to the support of the hosting provider
  5. Reinstall or reset WordPress

1. Checking WordPress plugins

Plugins on WordPress Provoking the 500 Internal Server Error - 500 Internal Server Error Solved Learn To Fix It😁 Speed

The best way to find out what plugins might be the cause of the 500 status error is to disable all plugins and then activate them one by one. Which will make it easier to find the culprit and fix it. Now, disabling the plugins is very simple, here is how:

3 Steps to disable all WordPress Plugins:

  1. Log in to your WordPress dashboard.
  2. Under Appearance, find the “Plugins” section. Hover over the word “Plugins” and click on “Installed Plugins”.
  3. In the plugin dashboard, click on “Bulk Actions”, select “Disable” from the list of drop-down options and click on “Apply”.

All installed plug-ins should now be deactivated.

Now it is time to find the culprit!

For this, you need some patience because you have to go through one plug-in after the other until you find the plug-in that is causing the 500 Internal Server Error.

The best way to find out which plugin is causing the HTTP 500 Internal Server Error:

  1. After you have deactivated all plug-ins, keep the normal browser open in which you have deactivated all plug-ins. Then open an incognito browser and open your website or the web page that triggered the Internal Server Error Code 500.
  2. Go back to the normal browser (not the incognito browser) and activate the first plugin in the list.
  3. Clear the entire cache, wait 1-2 minutes and press Ctrl+Alt+Sup on the incognito page.
  4. Check whether the error occurs again. If it does, you have found the culprit. If the error does not reoccur, continue troubleshooting all other plug-ins until you find the one causing the error.

Ok, having done all that, you have solved the problem? Great, then you can continue your work, but if not, then you need to do more tests!

There is another possible scenario that application-defined or object-defined error 1004 when you can even load your website at all due to the 500 internal server error. In this case, you will need to login to your Cpanel and go to the section called “File manage”, find the folder that contains all plugins and disable them from there. here is how to disable all plugins using Cpanel.

Steps to disable all WordPress plugins using Cpanel:

  1. Log into your cPanel and click on the file manager folder.
  2. Navigate to your WordPress installation folder. Example – Public_html/your-website
  3. Locate the plugins folder, which you can find here: Public_html/your-website/wp-content/plugins. There are all plugins you were using in your WordPress website.
  4. Now rename the plugins folder, to something like “faulty-plugins”. To rename the folder – > simply right-click on it – > Rename

Now all plugins that you have installed in your WordPress are disabled. Try reloading sharp printer error h5-01 site in your browser’s incognito mode to see if the problem you were having is now gone. If so, you need to find out which of the plugins caused the problem.

To do this, 500 internal server error error cpanel, you should first create another folder and name it “plugins”.

From here you should try to open your website in an incognito tab. The best thing to do is to reinstall all the plugins one after the other and try to see if the problem occurs again with each reinstallation.

The advantage of this approach is that you will not receive an error message in case of a faulty plugin. That means you do not have to check which one it was, you just have to delete the renamed plugin folder, and sayonara 500 Internal Server Error.

500 Internal Server Error: Solved!

No? Oh boy! let’s continue with our troubleshooting!

2. Check the WordPress theme installed

Themes are prone to internal server errors that can be fixed with the right know-how.

There are many reasons why your website is not working properly, but some of them point to your installed themes. WordPress is a popular content management system that often has issues with themes. With the right know-how, 500 internal server error error cpanel, you can rule out your theme as the culprit for the 500 Internal Server Error by deactivating the theme marked as “active” in your theme’s dashboard. These are the steps:

  1. – Log in to your WordPress dashboard
  2. – Hover over the “Appearance” left menu item and click on “Themes”.
  3. – Deactivate the active theme and activate a default theme. (WordPress currently comes with three default themes: Twenty Nineteen, Twenty Twenty and Twenty Twenty-One).

After performing this method, you should open an incognito tab again and try to load your website. If it works, you have found the culprit. 500 Internal server error fixed!

But what if you can no longer log into the WordPress backend dashboard because of this 500 Internal Server Error?

Then you need to follow these further steps to manually deactivate the themes via Cpanel.

Disabling WordPress Themes Using Cpanel:

  1. Log in to your cPanel and click on “File Manager”.
  2. Double-click on the “public_html” folder and navigate to the “wp-content” folder and click on the “themes” folder. 
  3. You should then see the list of installed themes. It is best to rename your main theme folder to “testing-theme”.

Once this is done, open your website in an incognito tab to check if it works!

If it does not, we move on to the third and simpler method of troubleshooting the 500 Internal Server Error.

3. Check if the .htaccess file is corrupted

When you get an internal server error on your WordPress website, it is not uncommon for the cause to be a problem with your .htaccess file. If this is the case, it may be because you or someone else was trying to make changes to the site or perform upgrades or modifications when the error occurred.

To fix the 500 Internal Server Error, you can try repairing, restoring or recreating a .htaccess file. This htaccess file allows you to make changes to the configuration of your website without having to edit the server’s configuration files. Because of the great importance of this file, it must be handled with care, as it can mess up your entire website and cause the 500 Internal Server Error, among other errors.

If the Htaccess files become corrupted, this can lead to problems such as broken links, internal server errors, unwanted redirects and much more.

If your .htaccess file becomes corrupted, it is usually because you have installed a faulty plugin 500 internal server error error cpanel nulled plugins) or tried to customise the file by adding commands that are not supported by your web server. The most common cause is themes that are not coded correctly (or trying to install nulled themes). In any case, you need to fix this 500 Internal Server Error (and stop using nulled plugins and themes). So let us try to fix this server error by correcting your Htaccess file.

The best option you have is to use a backup that you or your hosting provider may have. 

If you replace your current .htaccess file with a backed-up file, most websites that experience this 500 Internal Server Error due to a 500 internal server error error cpanel .htaccess file will be back online and the error fixed!

Oh, you do not know python import mysqldb error to find your htaccess file? I do not know that either! XDDD. Just kidding, here are the steps to find the htaccess file:

In most cases, you will find this .htaccess file in the root directory. Yes, there where you can also find other important folders like wp-admin, wp-content and wp-includes.

Some hosting providers hide the htaccess file because it is important for the operation of your website. If you can not see it, make sure all hidden files are viewable. Just check the file manager settings of your WordPress hosting account.

How to find an Open .htaccess File?

  1. Go to your file manager folder – > you will find the folder public_html. (root folder)
  2. If you cannot see the .htaccess file, navigate to the top-right menu, there you will see the word “Settings”, click on it and activate the option Show hidden files.
  3. Now activate range check error reasons display of all hidden files so that you should now be able to see the .htaccess file.

Here you can simply delete the file and create a new one or edit the current file. Here you can see how to carry out these two tasks:

Task one: Delete the htaccess file:

Just click on the file and press delete! I told you it was easy! 

Task two: Create a new htaccess file:

OK, this is quite easy and you should do it directly from the Cpanel dashboard, 500 internal server error error cpanel. These are the steps to create a new htaccess file:

Click the New File button at the top of the menu.

You need to name the file .htaccess, yes, with the dot in front of it. Paste the code I have given below, because that’s the default setting you need for your WordPress website, and click “Create” to save your changes.

The default settings of the Htaccess file:

# BEGIN WordPress

RewriteEngine On

RewriteBase /

RewriteRule ^index.php$ – [L]

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule. /index.php [L]

# END WordPres

There is also the option to use and FTP client.

An FTP Client is a sofware that manages files on a remote server.

So, if you are using an FTP Client to upload your website content instead of WordPress’ built-in editor, then follow these steps:

Go to the Server menu and enable the option “Force showing hidden files”.

Now you should see the .htaccess file that was hidden.

In case you were wondering: Are these steps the same for all hosting providers? They may vary a little, but in general, the variations are very small.

Ok, it’s time to test the salt! Is it sweet? Does your website load perfectly? Nice, you just fixed the 500 Internal 500 internal server error error cpanel Error. Hooray!

No? Do you mean you are still seeing the same error? Then it’s time to get help!

4. Ask for the support of your hosting provider

If you have come this far and your 500 Internal Server Error still persists after all of the above, it is time to ask the support team at the company providing your hosting service to reset your site to the last working version from which a backup was made.

Some unusual problems can trigger these 500 internal server errors in WordPress, but at this point, it may be best to ask your host. The problem may even be a genuine server ahci port0 device error k50ij that they can at least confirm, and they can also investigate things like file permissions errors and other causes.

The problem with this method is that hosting providers sometimes have very poor customer support. To fix the error today, try contacting the provider, preferably via live chat. If there is no such thing as live chat, change hosting providers. XDDD, Nah, just kidding, send them an email or give them a call. 

But at this point, 500 internal server error error cpanel, these support features are an indicator of how good your hosting provider is, and if it’s bad, you’d better switch to a better provider. There are many options, I can tell you 4 of the best:

  1. SiteGround
  2. Hostinger
  3. WPEngine
  4. Namecheap

Now for the last method, which I list last because it should be your last option, namely resetting your WordPress installation.

5. Reinstalling your WordPress site

Say none of the above has worked, even your hosting provider’s support has not responded yet, but you need to fix that 500 Internal Server Error today. Desperate diseases need desperate cures!

Here you will carefully try to fix everything, 500 internal server error error cpanel, and this article will help you. So let us do it right.

First of all, you need to make a backup of your files, for this, you have two options:

  1. Download the backup created by your hosting provider.
  2. Manually create your own backup.

Whatever you decide, these are the steps to create a backup of your website:

How to download a backup from your hosting provider:

  1. Log in to your Cpanel dashboard.
  2. Look for an icon labelled Tools & Utilities. There you should see an option called Backup Manager.
  3. Then click on the appropriate icon for the backup file you want to download and save the file to an easy-to-find location on your computer.

Manually create a backup of your website’s files.

There are two options here, depending on how serious your 500 Internal Server Error is.

  1. If you are able to log into your WordPress backend dashboard, you can simply export a backup using the “Export” option you see when you click on the “Tool” option in the left side menu of WordPress.
  2. If you do not have access to your WordPress dashboard at all, you’ll need to go to the Cpanel dashboard or use an FTP client. Let us take a look at how to do this properly.

Create a backup of your website via the WordPress dashboard: