how to solve error 500

How-To Geek

What is a 500 internal server error, and how do i fix it.

500 Errors? Is that a lot?

Quick Links

What a 500 internal server error means, how to fix a 500 internal server error, how to view an older copy of the web page, key takeaways.

A 500 Internal Server error means that the website you were trying to connect to has experienced a problem and can't provide a more specific error code. You cannot fix a 500 Internal Server error, but you can usually view an archived copy of the website on the Wayback Machine.

If you try to visit a website and see a "500 Internal Server Error" message, it means something has gone wrong with the website. This isn't a problem with your browser, your computer, or your internet connection. It's a problem with the site you're trying to visit.

Related: 6 Types of Browser Errors While Loading Web Pages and What They Mean

This error may appear in a variety of different ways, but they all mean the same thing. Depending on the website, you may see the message  "500 Internal Server Error", "500 Error", "HTTP Error 500", "500. That's an error", "Temporary Error (500)", or just the error code "500". It's one of many different  error messages you might see in your browser .

However you see this displayed, this is an error with HTTP status code 500. The 500 error code is a generic message that appears when something unexpected happened on the web server and the server can't offer more specific information. Rather than giving you a normal web page, an error occurred on the web server and the server gave your browser a web page with an error message instead of a normal web page.

This is a problem on the website's end, so you can't fix it yourself. Whoever runs the website will have to fix it.

However, there are often ways to quickly get around the problem. This error message is often temporary and the website may quickly fix itself. For example, many people may be connecting to the website at once, causing the problem. You may just need to wait a few minutes --- or a few seconds --- before trying again, and the website may work properly.

If you experience this problem, try reloading the web page. Click the "Reload" button on your browser's toolbar or press F5. Your browser will contact the web server and ask for the page again, and this may fix your problem.

You shouldn't try reloading the page if you were submitting an online payment or initiating some type of transaction when you view this message. This may cause you to submit the same payment twice. Most websites should stop this from occurring, but a problem could occur if the website experiences a problem during a transaction.

If this doesn't work, you may need to wait a while before coming back to the website later. The website is probably experiencing a problem, and the people who run the website will have to fix it. Try accessing the website again in the future and it may work properly.

If you're concerned that the people who run the website aren't aware of the problem, you may want to contact them and inform them of the problem you're experiencing. If the website is broken for you, it's probably broken for other people, too --- and the website's owner should want to fix it.

For example, if you experience the error on a business's website, you may want to dial that business's phone number. If the business has a customer service email address, you may want to write an email to that address. You can also contact many businesses on social networks like Facebook and Twitter.

Related: How to Access a Web Page When It's Down

If you're looking for a web page and it isn't available at the moment --- whether it's due to HTTP error 500 or any other problem --- you can view an older snapshot of the web page in several different ways . This won't work if you're trying to access a dynamic website or a web page with timely information (like breaking news), but it works very well for accessing older articles and other static pages.

For example, if you're using Google, use you access a cached copy of the web page in Google Cache. Locate the web page you want to view in Google's search results, click the arrow to the right of its address, and click "Cached" to view the old copy.

You may need to click the "Text-only version" link on the cache page to make the website load properly.

You could also load it up in a tool like the Wayback Machine to see older versions of the page.

If you're a website owner and you're experiencing this error on your server, there's no single easy fix. There's a problem with something, and it could be many things. Common problems include an error in your website's .htaccess file, incorrect permissions on files and folders on your server, a software package that your website depends on not being installed, or a timeout when connecting to an external resource.

You'll need to examine your web server's log files and do more troubleshooting to determine the specific cause of the problem and its solution.

• Affordable Luxury: Top-Tier Tech Delights
• Early Black Friday Deals!

How to Fix a 500 Internal Server Error

It's likely not on your side but reloading the page then clearing your browser cache and deleting cookies can sometimes help

• Emporia State University

In This Article

Jump to a Section

• Reasons for the Error
• Solutions to Try on Other Sites
• Solutions to Try on Your Own Site
• More Ways the Error Might Appear

Other Errors Like the HTTP 500

• Frequently Asked Questions

The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the website's server, but the server could not be more specific on what the exact problem is.

Are You the Web Manager? See Fixing 500 Internal Server Error Problems on Your Own Site towards the bottom of the page for some better advice if you're seeing the error on one or more of your pages.

What Causes an HTTP 500 Internal Server Error

Most of the time, this error appears when there's an issue with the page or site's programming, but there's certainly a chance that the problem is on your end. Those problems could be caused by cache or cookie errors in a browser,

More specific information about the cause of a particular HTTP 500 error is often provided when it occurs on a server using Microsoft IIS software. For example, look for numbers after  500 , as in  HTTP Error 500.19 - Internal Server Error , which means  Configuration data is invalid .

How to Fix a 500 Error

Because the 500 Internal Server Error is a server-side error, the problem probably isn't with your computer or internet connection but instead with the website's server.

While not probable, there may be something wrong on your end, in which case here are some things you can try:

Reload the web page. You can do that by selecting the refresh/reload button, pressing F5  or Ctrl+R , or trying the URL again from the address bar.

Even if the 500 Internal Server Error is a problem on the webserver, the issue might be temporary. Trying the page again will often be successful.

If the message appears during the checkout process at an online merchant, be aware that duplicate attempts to checkout may end up creating multiple orders— and multiple charges! Most merchants have automatic protections from these kinds of actions, but it's still something to keep in mind.

Clear your browser's cache . If there's a problem with the cached version of the page you're viewing, it could be causing HTTP 500 issues.

Caching issues do not often cause internal Server Errors, but we have, on occasion, seen the error go away after clearing the cache. It's such an easy and harmless thing to try, so don't skip it.

Delete your browser's cookies . You can correct some 500 Internal Server Error issues by deleting the cookies associated with the site on which you're getting the error.

After removing the cookie(s), restart the browser and try again.

Troubleshoot as a 504 Gateway Timeout error instead. It's not very common, but some servers produce a 500 Internal Server Error when in reality, 504 Gateway Timeout is a more appropriate message based on the cause of the problem.

Contacting the website is another option. There's a good chance that the site's administrators already know about the 500 error, but if you suspect they don't, letting them know helps both you and them (and everyone else).

Most sites have support-based social network accounts, and a few even have email and telephone numbers.

If it looks like the site is down entirely and you can't find a way to report the 500 Internal Server Error message to the website, it might help your sanity to keep up with the outage on social media. You can usually search for #websitedown , as in #gmaildown or #facebookdown .

Come back later. Unfortunately, at this point, the 500 Internal Server Error is no doubt a problem outside of your control that will eventually get fixed by someone else.

If the 500 Internal Server Error message appears at checkout during an online purchase, it might help to realize that sales are probably being disrupted—usually a great incentive to the online store to fix the issue very quickly.

Even if you're getting the 500 error on a site that doesn't sell anything, like YouTube or Twitter, as long as you've let them know about the problem, or at least tried, there's little more you can do than wait it out.

Fixing 500 Internal Server Error Problems on Your Own Site

A 500 Internal Server Error on your website requires an entirely different course of action. Because most 500 errors are server-side errors, it's likely your problem to fix if it's your website.

There are lots of reasons why your site might be serving a 500 Error to your users, but these are the most common:

• A Permissions Error. In most cases, a 500 Internal Server Error is due to an incorrect permission on one or more files or folders. In most of those cases, an incorrect permission on a PHP and CGI script is to blame. These should usually be set at 0755 (-rwxr-xr-x).
• A PHP Timeout. If your script connects to external resources and those resources timeout, an HTTP 500 error can occur. Timeout rules, or better error handling in your script, should help if this is the cause of the 500 error.
• A Coding Error in .htaccess. While not as common, be sure to check that your site's .htaccess file is properly structured.

If you're running WordPress , Joomla , or another content management or CMS system, be sure to search their support centers for more specific help troubleshooting a 500 Internal Server Error.

If you're not using an off-the-shelf content management tool, your web hosting provider, like InMotion , Dreamhost , IONOS (1&1) , etc., probably has some 500 Error help that might be more specific to your situation.

Ways You Might See an Internal Server Error

When Google services, like Gmail, are experiencing the error, they often report a Temporary Error (500) , or simply 500 . This error message might be seen in many ways because each website is allowed to customize the message.

Here are several common ways that you might see the HTTP 500 error wording:

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

Since a 500 Internal Server Error is generated by the website you're visiting, you could see one in any browser in any operating system, even on your smartphone. Most of the time, it displays inside the browser window, just as web pages do.

When Windows Update is involved, it appears as a WU_E_PT_HTTP_STATUS_SERVER_ERROR message or 0x8024401F error.

If the website that reports the 500 error is running Microsoft IIS, you might get a more specific error message:

Many browser error messages are similar to the 500 Internal Server Error message because they're all server-side errors, like 502 Bad Gateway , 503 Service Unavailable , and 504 Gateway Timeout .

Many client-side HTTP status codes also exist, like the popular 404 Not Found error , among others. You can see all of them in our  HTTP Status Code Errors  list.

5xx server errors on Instagram (from 500 to 511) indicate a problem with Instagram's servers. The best course of action is to wait for the problem to be fixed, but you can also try a few things yourself. Double-check your connection, try logging out and back in again, or reinstall the app or check for app updates.

If you see Hulu 500 error , it's most likely a problem with the website and maybe a problem with the stream. Refresh the web page and try again. If you're still getting the error, try a different web browser or change to a different streaming device. Also, test your internet speed  to make sure it's fast and stable.

If Discovery+ is giving you an error 500 message, the server isn't working correctly; the only thing you can do is check back every so often until the error stops appearing.

Get the Latest Tech News Delivered Every Day

• 404 Page Not Found Error: What It Is and How to Fix It
• How to Fix a 400 Bad Request Error
• 503 Service Unavailable Error Message: What It Is and How to Fix It
• What Does a 403 Forbidden Error Mean? How Do You Fix It?
• How to Fix a 408 Request Timeout Error
• How to Fix a 401 Unauthorized Error
• How to Fix a 504 Gateway Timeout Error
• HTTP Status Codes
• Hulu Error Codes: What They Are and How to Fix Them
• Is Twitch Down... Or Is It Just You?
• 502 Bad Gateway Error: What It Is and How to Fix It
• 8 Ways to Fix Roblox Error Code 403
• How to Fix It When Your ChatGPT Login Isn't Working
• Is Reddit Down... Or Is It Just You?
• How to Fix Mss32.dll Not Found or Missing Errors
• What Is a POST Code?

By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.

Deploy your app quickly and scale as you grow with our Hobby Tier

How to Fix a 500 Internal Server Error on Your Site

The dreaded 500 internal server error. It always seems to come at the most inopportune time and you’re suddenly left scrambling to figure out how to get your site back online. Trust us, we’ve all been there.

Other errors that behave similarly that you might 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. Read more below about what causes this error and what you can do to prevent it in the future.

What is a 500 Internal Server Error?

The 500 Internal Server Error happens when the server encounters an unexpected condition that prevents it from fulfilling the request. This is a general message indicating that the server knows something is wrong, but can’t be more specific about the exact problem.

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 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”
• “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. That’s 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 request. 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.

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.

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

Here is another creative 500 server error example from the folks over at readme.

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

If it’s an IIS 7.0 (Windows) or higher server, they have additional HTTP status codes 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 – An ASP.NET httpHandlers configuration does not apply in Managed Pipeline 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.

What Are the Causes of a 500 Internal Server Error?

500 Internal server errors 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.

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 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.

This is never not annoying 😖 pic.twitter.com/pPKxbkvI9K — Dare Obasanjo🐀 (@Carnage4Life) September 26, 2019

Check out 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 easiest 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.

We’ve also noticed that sometimes this can occur immediately after you update a plugin or theme on your 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:

• How to Force Refresh a Single Page for All Browsers
• How to Clear Browser Cache for Google Chrome
• How to Clear Browser Cache for Mozilla Firefox
• How to Clear Browser Cache for Safari
• How to Clear Browser Cache for Internet Explorer
• How to Clear Browser Cache for Microsoft Edge
• How to Clear Browser Cache for Opera

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.

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 /wp-content directory. Others, like here at Kinsta might have a dedicated folder called “logs”.

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.

If the 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. Check for Errors in 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.

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 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 due 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 for a lot of users on the same servers.

Check out our in-depth post on how to fix the error establishing a database connection .

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.

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, 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.

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:

• How to reinstall WordPress from the WordPress dashboard while preserving existing content
• How to manually reinstall WordPress via FTP while preserving existing content
• How to manually reinstall WordPress via WP-CLI while preserving existing content

7. Check for 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 when 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 host support team and ask them to quickly GREP file permissions on your folders and files to ensure they’re setup properly.

8. Increase 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 wp-config.php 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.”

Click on “Switch to PHP Options.”

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

Increase PHP Memory Limit in Apache

The .htaccess 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 .htaccess file there.

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 php.ini file. Log in to your site via FTP  or SSH, go to your site’s root directory and open or create a 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 .htaccess file for the above php.ini file settings to work. To do this, edit your .htaccess file, also located at the root of your site, and add the following code 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 .user.ini files. To edit your .user.ini file,  login to your site via FTP  or SSH, go to your site’s root directory and open or create a .user.ini 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.

Add the following code to the top of your wp-config.php file:

You can also ask your host if you’re running into memory limit issues. We utilize the Kinsta APM too l 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.

9. Fix Your .htaccess File

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

First, log in to your site via FTP  or SSH, and rename your .htaccess file to .htaccess_old .

Normally to recreate this file you can simply re-save your permalinks in WordPress. 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 you can create a new .htaccess file and input the following contents. Then upload it to your server.

See the WordPress Codex for more examples, such as a default .htaccess file for multisite .

10. Fix 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, 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. Check With Your Host About Server Issues

Finally, because 500 internal server errors can also occur from PHP timing out or fatal PHP errors with third-party plugins , you can always check with your host. Sometimes these errors can be difficult to troubleshoot without an expert. Here are just a few common examples of some errors that 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 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. 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:

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

This can be especially useful if 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 an application , database , and managed WordPress host (like Kinsta).

500 internal server errors are always frustrating, but hopefully, now you know 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.

Brian Jackson

Brian has a huge passion for WordPress, has been using it for over a decade, and even develops a couple of premium plugins. Brian enjoys blogging, movies, and hiking. Connect with Brian on Twitter .

Related Articles and Topics

How To Fix a 502 Bad Gateway Error

9 Proven Methods to Fix WordPress White Screen of Death (WSoD)

If that doesn’t work you can “FTP” into your server…easy for you maybe. I don’t even know what the he** that is.

Hey Jess, Perhaps our KB on how to FTP will help? https://kinsta.com/knowledgebase/how-to-use-sftp/

If not, I would recommend skipping to #11 and asking your host.

Thank you very much for your useful and well-explained post! After many tries trying to upload successfully my WordPress. You just saved my day!

I struggled with this after moving a site from one to another host on a different domain name. The problem was with the wordfence settings file. Once the path was corrected there, the site worked.

Only getting the 500 error when users post comments/replies…works fine otherwise. No errors in any logs.

I have tried pretty much everything suggested above.

Any advice is much appreciated.

Leave a Reply Cancel reply

By submitting this form: You agree to the processing of the submitted personal data in accordance with Kinsta's Privacy Policy , including the transfer of data to the United States.

You also agree to receive information from Kinsta related to our services, events, and promotions. You may unsubscribe at any time by following the instructions in the communications received.

HTTP 500 Internal Server Error: What It Means & How to Fix It

Published: September 15, 2022

Troubleshooting an HTTP 500 internal server error is like solving a mystery.

You don't know what exactly happened or why it happened — all you know is that something's wrong and you need to fix it.

To guide you through the hassle of troubleshooting the dreaded HTTP 500 internal server error, let's go over what it exactly means and its most common causes and solutions.

What is an HTTP 500 internal server error?

An HTTP 500 internal server error is a general error message. It covers unexpected issues that don't fit into existing error codes. HTTP 500 errors are difficult to troubleshoot because a range of issues on the server side can trigger them.

Here are some examples of what a 500 error page might look like in your browser:

Image Source

HTTP 500 errors aren't problems with your computer, browser, or internet connection. Instead, they're a generic response that catches any unexplainable server error. You'll see the HyperText Transfer Protocol (HTTP) 500 Internal Server Error when your server issue doesn't fit another error code.

Other Common Error Codes

HTTP codes show you how your web browser and website communicate. These are some other common error codes you might see on your website:

This is a standard status code for websites that are performing well.

This is the code for permanent redirects. For example, say you have two site pages about widgets with duplicate information and one gets more traffic than the other. It makes sense to redirect the low-traffic page to the high-traffic page to improve SEO for your site.

This code is for temporary redirects. This is for situations where you want to send users to an alternate page for a short amount of time.

This code shows up when the website you're requesting hasn't seen an update since your last visit.

This code comes from the server when you're trying to access a restricted URL.

Free Kit: How to Run an SEO Audit

Use this kit to start running a better website.

• SEO Template
• Audit Checklist
• Introductory Guide

You're all set!

Click this link to access this resource at any time.

Fill out the form to start running a better website.

A 404 code tells your users that your server can't find that page they requested with their browser. 404 errors are common, and some sites use this to their advantage .

This is an HTTP response status code error. It tells you that a web browser wants to access your web page and your server has rejected that specific HTTP method. This means that the browser can’t access the requested web page.

This is a permanent code that tells site visitors that the page they're looking for doesn't exist.

This code appears when a user tries to upload a file that exceeds the server’s file size limit.

This error is a server response to stop sending requests because of overloaded resources. This code might show up if your site needs to make too many API calls to meet a request.

This code tells users that the server is temporarily unable to load the page they're looking for.

Check out this post for a comprehensive overview of error codes .

Potential Causes of a 500 Internal Server Error

A 500 internal server error is, as the name implies, a general problem with the website's server. More than likely, this means there's an issue or temporary glitch with the website's programming.

Some potential causes of a 500 internal server error include:

Corrupted or Broken .Htaccess File

A .htaccess file is a text file with important server instructions. These instructions tell your software to enable or disable specific functions. They might help you protect passwords in a directory or restrict user access.

There are many ways to corrupt a .htaccess file. It can happen during plugin installation, file configuration, or while you are working on your server.

A Permissions Error

Permission errors come with file protection. Permissions errors might be bugs, user mistakes, or networking problems. Usually, this error means that the user isn’t allowed to perform the action they're trying.

Faulty Third-Party Plugins or Themes

To increase user features and functionality, you might add a third-party theme or plugin to your website. These plugins can be great for your site, but they can also impact site security, bugs, and performance.

These plugins and themes are often created by individuals or small groups. This can be challenging because they may need more time to address bug fixes and vulnerabilities.

Exceeding the PHP Memory Limit

PHP is a server-side scripting language embedded in HTML. PHP is for managing content, databases, session tracking, and more. Each PHP process uses memory, and your hosting account has a limit for each one of these processes.

If a website needs more than this memory limit, you may see an HTTP 500 error.

HTTP Error 500 Browser Compatibility

Most businesses design their websites for maximum browser compatibility. This means that your website is easy to access and use on any browser or operating system. But your site may work perfectly in one browser and have issues or errors in others.

Because HTTP 500 is a catch-all error, you can see this error on any browser and in any operating system .

How an HTTP 500 Error Might Appear

This error can come up on any site you try to visit on a browser. Because it’s such a common error, there are many ways to communicate this code.

• Internal server error
• The page isn't working
• 500 Internal Server Error
• 500 Server Error
• 500. That's an error.
• HTTP 500.0 - Internal Server Error
• Error code: 500
• The server returned a 500 Internal Server Error
• Temporary Error (500)

How to Fix a 500 Internal Server Error

Unlike other server-side errors like a 502 code , a 500 internal server error is it doesn't immediately tell you what the problem is , nor does it tell you how to fix it. If the error persists for too long on your site, it could even negatively impact your SEO .

So, let's dive into some solutions so you can try to fix the issue.

If You're Trying to Load a Page with a 500 Internal Server Error:

1. refresh the page..

This might seem obvious, but if it's a temporary loading issue, you might find success if you refresh the page. Before trying anything else in this list, reload the page and see what happens.

2. Come back later.

Since the error is on the server side, I'm willing to bet the website owners are working as quickly as possible to resolve the issue. Give it a few minutes or up to an hour or so, and then reload the URL and see if the development team has fixed the issue.

3. Delete your browser's cookies.

If clearing the browser history doesn't work, you might try deleting your browser's cookies. If the cookies are associated with the error-prone webpage, deleting the cookies might help reload the page.

4. Paste your URL into the website "Down for Everyone or Just Me."

Head to downforeveryoneorjustme.com and paste in the URL where you're seeing the internal server error. You'll either be told that the website is only down for you, or that the website is down for everyone.

If the 500 Internal Server Error is on Your Own Website:

1. deactivate a plugin or theme..

Newly activated software, add-ons, or third-party scripts might be conflicting with your current server configuration. To determine this, try (carefully) deactivating or uninstalling your software add-ons one at a time to identify what exactly is causing the internal server error.

If you run a WordPress website, this is easy to do with plugins. From your dashboard, choose Plugins > Installed Plugins , then deactivate the first plugin. If the error resolves, you know this plugin is part of the issue. Reactivate the first plugin, then repeat this deactivate-reactivate process one at a time for all plugins to determine which ones are causing your error.

2. Use a plugin like WP Debugging to identify the issue.

If your site is powered by WordPress and you're comfortable with WordPress debugging processes, consider installing a plugin to help you identify the issue with your server.

The debug plugin WP Debugging , for instance, helps you figure out exactly what's wrong with your site, which will result in a speedier fix.

3. Ensure your PHP setup is configured correctly.

If the issue is related to a PHP timeout, consider creating timeout rules or error handling in your script to resolve the issue. Here's a full list of php.ini directives to configure your PHP setup.

4. Check the code for your site's .htaccess file.

Incorrect coding or improper structure with your .htaccess file could be the reason you're seeing the 500 internal error. The .htaccess file helps you manage how long resources should be stored in a browser's cache. Try editing the file if you're seeing a 500 internal server error.

To locate your .htaccess file, access your website files through a file manager like cPanel or via FTP/SFTP. The file will probably be located in your public_html directory. There's a good chance your server will hide this file from view by default and you'll need to toggle hidden files on to see it.

Coding errors in .htaccess and custom scripts can also cause an HTTP 500 internal server error.

5. Ensure your new software is installed correctly.

Finally, check to see if your recently installed or upgraded software actually failed to install or upgrade. To refresh your software, check the vendor's website for instructions.

Last Resort: Ask a Server Administrator for Help

If troubleshooting popular software problems or debugging server-side scripts doesn't fix your HTTP 500 internal server error, you should read about the most common causes for this type of issue in your server's documentation — an HTTP 500 internal server error can occur in different operating systems for a multitude of reasons.

You can also ask your service provider to access your error logs and find evidence of the root cause of your problem.

Internal server errors are irritating because they're unhelpful — it's basically the web server's way of saying, "Eh, I'm not sure." Hopefully, one of the above steps will resolve the problem so you can get back to life as usual.

Editor's note: This post was originally published in October 2018 and has been updated for comprehensiveness.

Don't forget to share this post!

Related articles.

Does Google Think Your Website Is Spam?

A Beginner's Guide to Data Flow Diagrams

Image Alt Text: What It Is, How to Write It, and Why It Matters to SEO

The Top 11 Search Engines, Ranked by Popularity

Parts of a URL: A Short Guide

Sitemaps: What They Are, How to Create One & Submit it to Google

The Ultimate Guide to Technical SEO

Full List of Meta Tags, Why They Matter for SEO & How to Write Them

What is a Web Crawler? (In 50 Words or Less)

Permalinks: What They Are & How to Structure Them for Max SEO Value

Includes SEO Template, Audit Checklist, and a 9-Step Guide

• Domain Names
• Domain Name Search
• Free Domain Transfer
• .com Domain
• 1 Dollar Domain
• Cheap Domain
• Free Domain
• Buy SSL Certificate
• Website Builder
• Website Platforms
• Website Templates
• Web Design Services
• eCommerce Website Builder
• Web Hosting
• WordPress Hosting
• 1 Dollar Hosting
• Windows Hosting
• Free Website Hosting
• Create Business Email
• HiDrive Cloud Storage
• Microsoft 365 Business
• Cloud Server

Your fully virtualized private server.

• Dedicated Servers
• Rent a Server
• IONOS Cloud
• Business Name Generator
• Logo Creator
• Favicon Generator
• Whois Lookup
• Website Checker
• SSL Checker
• IP Address Check
• Technical matters

How to fix HTTP 500 internal server error?

HTTP status codes provide information about whether an online request was successful, and if not, what the error is. But the error messages aren’t always clear. This is especially the case for the “500 Internal Server Error.” This message indicates that an error has occurred during connection to the server and that the requested page cannot be accessed. However, it won’t tell you exactly why this is the case. Fortunately, there are different methods for finding the cause. We point out typical error sources and give tips on what to do if you encounter the HTTP error 500.

What does the internal server error mean?

What are the causes of error 500, how can website operators fix the 500 internal server error, how should internet users respond to an http error 500.

$1 Domain Names

Register great TLDs for less than $1 for the first year.

Why wait? Grab your favorite domain name today!

Using status codes, the web server tells an internet user’s browser (client) whether a request (i.e. accessing a website) was successful or not. If the browser receives the 200 status code, it knows that everything went well. However, the user never sees this message since the requested content appears instead. The situation is different with the 400 and 500 status codes. While the former indicate client errors, the latter are server-related. The Internal Server Error 500 is a collective status code for server errors . Therefore, at first glance, it is not possible to determine where the error actually lies. The user only knows that the server has reported an unexpected error.

However, if the server has installed Microsoft Internet Information Services (Microsoft IIS), the error code will be specified. Decimal places indicate the cause of the error in more detail:

• 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: An ASP.NET httpHandlers configuration does not apply in Managed Pipeline 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.

The “Internal Server Error” can occur when the request is processed by the web server. The collective status code includes everything unplanned that can happen on the server and prevent the website from being loaded. The server error 500 probably happens because an error has occurred in the configuration of the web server. Here is a selection of typical error sources:

• Permission error : The permissions of the main files and folders are not set correctly.
• PHP timeout : The script tries to access an external resource and experiences a timeout.
• Incorrect code in .htaccess : The structure in a .htaccess file could be wrong.
• Error in syntax or code in CGI /Perl scripts: In some cases, scripts are incorrect. Paths, especially, can be misaligned.
• PHP memory limit : A process exceeds memory and therefore cannot be executed correctly.

In the case of WordPress sites or other content management systems, installing a faulty or incompatible extension can also be the cause. Plugins and themes – especially from third-party providers – can affect the entire website.

Are your website visitors only seeing the 500 server error? As an operator, you should tackle the problem quickly because not only will this scare off your visitors, but it could also mean that Google will lower your ranking. Before you take action, first check whether your server is still running. If not, contact your hosting provider as soon as possible .

If there is an internal error, the first step is to view the log files . For Linux servers, the collection of error messages should be found at /var/log/httpd/error_log . It makes sense to reload the website to reproduce the HTTP error 500 code and observe how the log file is being created. This will help you find the source of the error quite quickly. Also consider which changes were made shortly before. In many cases, incorrectly programmed or incompatible plugins are the cause of error messages.

Errors can also occur if you have not set permissions correctly for important files . In general, there are three types of rights:

• Execute (x)

These permissions can be assigned for three different user types:

• Owner of the file
• Group of users

The rights are specified either in the abbreviations r, w, and x, or in corresponding numerical values: 4 for read, 2 for write, and 1 for execute. They are added for each user type and specified one after the other: rwxr-xr-x (rwx for the owner, r-x for the group, and r-x for all others) or 755 . This configuration (755) should be the default setting. If the permission assignment is set differently, an error may occur. You can change this with a command:

If this change does not solve the problem, you can also release all rights for each group for test purposes:

But only use this setting to locate the problem. Any user is allowed to rewrite the file, which is understandably a security risk.

Next, check (if distributing the rights didn’t produce the error message) if your scripts are running correctly. Sometimes errors occur because the script files have been moved, renamed, or deleted. Also check the .htaccess file : even a syntax error – no matter how small – can cause an internal server error. An equally common error is incorrectly formatting the .htaccess file. This must be created in ASCII or ANSI format , not in Unicode. Therefore, write the file in a text editor such as Notepad, Notepad++, or Sublime Text, and not in a word processing program such as Microsoft Word. To test whether the file is responsible for the error, you can temporarily rename it and reload the website. The server now won’t access .htaccess when loading the website. If you no longer receive the error message, you can repair the file or create a new one.

A timeout can also lead to an error message. In this case, it isn’t a web server error, but rather an interrupted connection to an external source. Are PHP scripts on your website set to access resources from other servers? Perhaps the resource is no longer available or server communication is down for some other reason. One way to eliminate this source of error is of course to not make your site dependent on external resources. If this is not possible, you can increase the time limit of your script. It also makes sense to implement efficient error handling so that errors in the PHP script can be detected more accurately.

Could it be that the memory is overloaded? The memory limit determines how much memory a process may use. If more RAM is needed than is available, this could result in an internal server error. You can increase the limit as a temporary solution. To do this, add a command like this to php.ini :

In this example, you would set the memory provided to 512MB. Note, however, that your hosting provider will only allow you a certain PHP script limit within the package that you’ve booked. If you enter a higher value, the web server will ignore it. Raising the limit is only a temporary solution: once your site is up and running again, you should look for the reason for the high RAM usage. There is a high probability that the error can be found in the code of your website.

If none of these methods offer you a solution, it is a good idea to contact your hosting provider . Before doing so, you can check the status of the servers: many hosting service providers will report the status of their servers via a status page or inform users via social media if a problem has occurred.

IONOS also has a status page where the hosting service’s customers are informed about current problems.

As a website visitor, there is little you can do if you encounter an internal server error. The web server on which the target website is located has an incorrect configuration. This means that there is no error in your PC settings or the network connection settings. Therefore, the easiest solution for you as an internet user is usually to reload the page again later . On the one hand, it is possible that the webmaster has already corrected the error. This is very likely, especially with large providers. On the other hand, it could be that you’re trying to access the website at an inconvenient time for the web server. If you’ve chosen the exact moment that the service is rebooting, the error message will be displayed even though everything is going to plan.

If you are confronted with the error message when ordering online , you must not reload the webpage, since you can’t see where the error occurred. It could be that the confirmation page failed to load, but the system has already accepted your order. Refreshing the page could therefore lead to a duplicate order.

It is also possible that an extreme increase in page views has brought the server down all of a sudden. This problem is usually solved within a few seconds – unless the website is permanently overloaded. If you still receive the error message after refreshing the page, you should first clear your browser’s cache . The browser may not actually reload the website, but use its internal memory instead. After emptying the cache , try again to access the website.

If the “500 Internal Server Error” is still being displayed, you simply have no other choice, but to wait for the website operator to solve the problem. There is, however, a little trick you can use in order to access the contents of the website. If you are not dependent on the latest state of the (functioning) page, you can access the Google cache . If you enter the command cache : followed by the relevant URL in the Google search bar, you can access an earlier – hopefully still working – version of the website. However, you won’t really be surfing the page, you will only be navigating within the copy on the Google server.

If you have to go back even further in the past, it may be worth taking a look at the Wayback Machine . There you can sometimes find older versions of websites that are even decades old.

If the website you want to visit is not accessible for a longer time, you can of course contact the webmaster . They may not even know that visitors are unable to access their site, which is why they will be grateful to be told.

Related articles

How to fix Error HTTP 504 (Gateway Timeout)

If the error message ‘HTTP 504 Gateway Timeout’ appears when you attempt to open a website, it means that the allowed time for responding to browser queries has been exceeded. A lot of the time the culprit is not the web server itself, but instead some other component of the server, i.e. a gateway, which is integral to the path of communication. What does 504 gateway timeout mean? How can you fix…

HTTP 503 (Service Unavailable): meaning and troubleshooting

It’s very likely that you’ve stumbled on the 'HTTP Error 503 The service is unavailable' notification or something similar during your daily browsing. The error message appears whenever a web server can’t display the website that the user is trying to access. There are many reasons for these notifications, just as there are many solutions. It’s your responsibility as the website operator to…

How to fix a Blue Screen of Death (BSOD)

The infamous blue screen of death usually shows up without any warning. It’s an important indicator of internal problems with hardware, software, or drivers. If Windows can no longer be run as a result of such a problem, then the forced shutdown takes place in the form of a blue screen containing an error message. This may cause unsaved files and documents to be lost. The most important thing with…

SMTP error 550: how to fix “Requested action not taken: mailbox unavailable” and other SMTP 550 error messages

If you want to send a message with your e-mail client and the sending fails, you’ll receive a corresponding error message from the server, including an SMTP status code. For example, the message “550 Requested action not taken: mailbox unavailable” means that the targeted address couldn’t be reached. Since this problem can have various causes, even more possible solutions exist, some of which you…

HTTP 400: Bad Request explained

Internet users are often confronted with error messages. HTTP status codes can be especially annoying, and even more so if you don’t understand what they mean. The message 'HTTP 400 – Bad Request' is a mystery for many internet users, but luckily it can be solved in most cases. We explain what the error message means and how to fix the error.

Build or host a website, launch a server, or store your data and more with our most popular products for less.

Other times, the page may have a customized design, as seen in the following image.

These are only a few examples of the error page and you can see it in countless variations. Regardless of how the page looks, it always has the same meaning – there is a problem that the server can’t pinpoint, and it prevents you from loading the website.

What are the common problems that can cause HTTP 500 Internal Server Error?

Although the error definition states the issue is from the server, that’s not always the case. Some of the common problems that can cause the error are:

• Corrupted browser cache
• Temporary connectivity issues
• Syntax errors or incorrect rules in the website’s .htaccess file
• Incorrect file and folder permissions
• Wrong PHP version for the website
• Corrupted .htaccess file
• Corrupted website’s database
• Problems with WordPress themes and plugins
• Exhausted PHP memory limit on the website
• Corrupted WordPress core files
• Large files on your website
• Problems with the MySQL server

How to Fix the “500 Internal Server” Error?

As you can see from the list above, the error’s origins are quite diverse. Since the error page will not clearly indicate the problem, you may need to troubleshoot a few of the possible causes until you find the culprit.

How to Fix 500 Internal Server – Video Tutorial

We will go over most of the eventual problems and their solutions.

How to Fix the “HTTP Error 500” as a visitor?

As a visitor, the only thing you can do is check if a connectivity issue from your end causes the error. You can also apply the following actions as a website owner since these are the quickest checks. If the error is caused by a local problem from your end, the steps below can save you a lot of time from troubleshooting.

Reload the page

The “HTTP Error 500” may be visible only for you, in case there was a brief connectivity problem. The website itself may be working fine, but you might have tried to access it when there was a momentary downtime, or your network failed to establish a connection to the website’s server.

Try reloading the page in the same browser with the Reload button or by pressing the keyboard shortcut Command+R for Mac, or F5 (Control+F5) for Windows.

If the website loads correctly, the issue was only temporary, and you can stop troubleshooting.

Clear your browser cache and cookies

When the website doesn’t open after reloading, your browser might be keeping expired or corrupted cache files and cookies. Reloading the page will not delete them, so you must clear them manually.

Read this guide on clearing cache and cookies in desktop browsers for detailed instructions.

Check these articles on deleting the cache on an Android phone or iPhone , if you use a mobile device.

Alternatively, you can test opening the page from another browser. For instance, if you use Chrome, try Firefox or vice versa.

After clearing the browser’s cache, reload the page to see if that solved the problem. If not, proceed with the next step.

Visit the website using another network

The connectivity problems causing the “HTTP 500 Error” may happen across your entire network. In this case, you will probably see the error on any device on this network.

To test if this is the problem, switch to another network. For instance, if you use a mobile phone connected to Wi-Fi, switch to mobile data.

How to Fix the HTTP 500 Internal Server Error from the website?

In the best-case scenario, the steps mentioned above will fix the problem. However, if the error persists, you may need to dig deeper into the issue since the error stems from the website itself.

As a site owner or webmaster, there are several checks you can do that can solve the “500 Internal Server Error.”

Check the Error Logs of the Website

In many cases, misconfigured files or scripts are the sources of the website’s errors. The error logs can help you identify them easier.

Typically, you should have such logs in your hosting’s control panel. SiteGround users can find the Error log in the website’s Site Tools.

To access it, navigate to the Websites section in your Client Area . Open the Site Tools of the respective site, select Statistics and click on Error Log.

You will see the most recent errors on your website that the server detected. Each error will be recorded with a few key pieces of information:

• The date and time of the error.
• Description of the error.
• Information about which folder or file is possibly generating the error.

Below, you can see an error log indicating a problem with the .htaccess file.

This record indicates that the problem is from the .htaccess file located in the root folder of the website. It also specifies that the error is related to a <IfModule> missing argument, which means there is a syntax error.

Using this information , you can navigate to the specified folder from File Manager , edit the . htaccess file and correct the syntax error.

Keep in mind that the Error log records errors related to the server configuration. Errors caused by PHP misconfiguration and scripts are not recorded, as they happen on application level.

PHP errors are recorded in php_errorlog . It is generated automatically in the folder of the offending PHP file. On SiteGround ’s hosting, the PHP error log is active by default. If you have previously deactivated it or your hosting hasn’t enabled it, read this guide on how to enable error reporting in a PHP script .

To inspect the PHP error log, you can use File Manager or FTP client. Navigate to the root folder, if the error is caused by a script located in the root folder. Open the file php_errorlog, where you can examine the errors.

The php_errorlog shows general PHP errors. However, you may need a more detailed log of the problem. If you have a WordPress website, you can also enable the debug log for WordPress that can show more information. For detailed steps on how to enable the WordPress debug log, see this guide .

Reset File and Folder Permissions

Another common problem that can cause the “HTTP 500 Error” is incorrect file and folder permissions on your website. If the permissions prevent visitors from opening the critical website’s files and folders, they may see the error page.

The standard permissions are 644 for files and 755 for folders . You can change them from the File Manager in your hosting panel or from an FTP Client .

For setting the permissions for WordPress sites, SiteGround clients can use the Reset Permissions tool for WordPress in Site Tools .

If your website is using another type of application, read this guide on how to change permissions for files and folders from File Manager .

Alternatively, if your hosting’s panel doesn’t have similar tools, you can change permissions from SSH or from an FTP Client .

Change the PHP version

An incorrect PHP version on your website may cause PHP scripts to time out or produce fatal errors. As a result, the website may return the “HTTP 500 Error.”

Test switching the PHP version to an older or later version. If the error disappears, it’s an indication that the previous version was wrong. Keep the site on the newly selected one.

SiteGround users can easily switch the PHP version with only a few clicks on Site Tools . For detailed steps, check this guide on how to switch to a different PHP version in Site Tools .

Inspect or regenerate the .htaccess file

A common cause of the “Internal Server Error” is a problem within the .htaccess file. If the file is corrupted, it defines an incorrect root folder or contains syntax errors, the usual result is the “HTTP 500 Error” page.

Fix the syntax error in .htaccess

As an example of a syntax error, we can use the previously mentioned error from the error log.

To inspect the file, open the Site Tools of the website. Then, select the section Site and open File Manager.

Navigate to the website’s root folder, which is the site name/public_html . In our example, the name is sg-testing.com, so the folder path is sg-testing.com/public_html .

In this folder, you can find the .htaccess file . Select the file and then press Edit to open the code editor.

Now, you can inspect its code. As the error log points, the problem is from the <IfModule>. The issue is a syntax error because the module is missing a forward slash in the closing tag </IfModule> .

Add the slash and then save the changes with the Save button. Reload the website and it should now load properly.

Wrong website’s root folder defined in .htaccess

Another common error in .htaccess is an incorrectly defined root folder for the website. Usually, this is a result of one of the following cases:

• You transferred the website from another hosting provider where it resided in a subfolder.
• You developed the website on a subfolder and then moved it to the main domain folder in the same hosting.
• For a WordPress website, you installed a plugin that has changed the RewriteBase in .htaccess. The plugin may need extra configuration to work with the modified code but currently, the website is inaccessible due to the “500 Internal Error”.

To illustrate the problem better, we can use the following example.

Notice the /dev path in RewriteBase . This code instructs the server to load the website from a folder named public_html/dev. Since the folder is non-existent, when you load a page from the website, it will produce the “Internal Server Error” screen.

To fix the problem, simply remove the subfolder path from RewriteBase so the code would look like this:

This is the default WordPress code defining the root folder for the website. Confirm the change in File Manager with the Save button and reload the website. The error shouldn’t appear anymore.

Regenerate the .htaccess file

Another standard troubleshooting scenario is to replace the .htaccess file with a new copy. To replace the file with a new copy, open File Manager, navigate to public_html , select the file .htaccess and choose Rename.

You can choose any name for the file. For example, you can name it htaccess-old and create a new . htaccess file.

If the website is WordPress, access the WordPress dashboard, navigate to the section Settings, and open Permalinks. Just click on the button Save Changes, and your website will generate a new .htaccess file with the default WordPress code.

If your website is not WordPress, find the default .htaccess code for your specific application. Use the button New File in File Manager and name the new file . htaccess . Paste the default code into .htaccess and save the changes.

After the new .htaccess file is set, reload the website again to see if the error is gone.

Repair the database or fix the database credentials

Another common problem that can cause the “500 Internal Server Error” is a corrupted database on your website . You may consider restoring the database from a backup or repairing it .

For WordPress, the error may occur if the website fails to connect to the database. Make sure that the credentials are set correctly in the wp-config.php file.

For detailed steps, read this guide on how to fix the error ‘Establishing a Database Connection’ in WordPress .

Disable plugins for your WordPress website

A misconfigured plugin can also trigger the “HTTP 500 Error” in WordPress. The standard procedure is to disable the plugins one by one until you find the culprit.

If the error is only on the front end, but you still have access to the WordPress admin dashboard, you can disable the plugins from the section Plugins. Then choose Installed plugins . From the drop-down Bulk actions menu , select Deactivate . Check the box Plugin and press Apply to deactivate all plugins.

In many cases, the error prevents you from logging into the WordPress dashboard so you may need to use an alternative way.

A popular suggestion you’ll find online is to rename the wp-content/plugins folder. We don’t recommend this method as it may fix the “HTTP 500 Error”, but cause other complications.

It is safer and more efficient to disable all plugins from Site Tools (if you are a SiteGround user) or from the database.

Read the following guides for detailed steps:

• How to disable all plugins from Site Tools
• How to disable all plugins from the website’s database

After the plugins are disabled, reload the website. If the website is fixed, it is a strong indication that the error is caused by one of the plugins.

Proceed by activating the plugins one by one. When the faulty plugin is reactivated, the error will return. You can then disable the plugins again to access the dashboard and activate all plugins apart from the problematic ones.

You may consider replacing this plugin with another one or contacting its developers to report the problem.

Change the theme for your WordPress website

A badly configured theme can also cause the “500 Internal Server Error” in WordPress. To check if the theme is the problem, you will need to replace it with another one.

Usually, you can change the theme from the website’s WordPress dashboard. However, in many cases, the ongoing “HTTP 500 Error” prevents you from logging in.

Read this guide on how to change the WordPress theme from the database for more information.

Increase the PHP Memory Limit of the Website

The “HTTP 500 Error” may also be caused by PHP scripts that exceeded the memory limit of your website. By default, the limit on all SiteGround plans is set to 512M . However, your WordPress website may be set to a lower value. To increase the memory limit, follow the steps from this guide on how to increase WP Memory Limit .

Restore a Backup of the Website

If none of the solutions helped solve the issue or you find them challenging to implement, you may consider restoring the website from a backup. Restoring the website will revert all changes that caused the error in the first place.

SiteGround users can check this detailed tutorial for the Website Backup Tool .

Check if your website contains large files

Another common reason for this error is having a very large file as a part of your website. On SiteGround’s shared hosting servers there is a size limit for files that can be opened through the web. The limit is 8GB, and if your website includes a larger file, this will result in the above error.

Check your website’s files either via SSH, FTP, or File Manager to locate the one causing the problem. Very often, these are logs with PHP errors.

On SiteGround’s servers, a log file is created automatically if your site’s PHP scripts produce any non-critical errors or warnings during their execution. The log file’s name is php_errorlog, and it is located in the same directory as the script that produced the errors. Usually, this would be your website’s root folder.

Contact the web hosting provider

Ultimately, the “500 Internal Server Error” may not be caused by your website configuration. The MySQL server may be down, or the server may be overloaded. Contact your web hosting’s support team so they can check the server’s status and help further with the problem.

The HTTP “500 Internal Server Error” can be very frustrating to deal with because of its unclear nature. The problem may originate from a local issue or an error on the website or the server .

This guide can help you narrow down the causes to fix the error more efficiently.

The “HTTP 500 Error” is one of the many error codes. Read this guide to find out more about the different error codes .

For more information about fixing other 5.X.X. status codes, read the following articles:

• How to fix the “HTTP 502 Bad Gateway Error”?
• How to fix the “HTTP 503 Service Temporarily Unavailable” error?
• What is “HTTP 504 Error” and how to fix it?

RELATED ARTICLES

• What to do when my site is down?
• Why do I receive "Internal Server Error 500" after I upload my site files?
• How to add custom error pages?
• HTTP Status Codes Explained

Share This Article

Secret Black Friday Deal

Hosting That Helps You Grow

From 1.99 € /mo. ( Regular 15.99 € /mo. Excl. VAT )

The Ultimate Guide to Understanding Error 500: Causes and Solutions

Error 500 is one of the most frustrating issues that website owners and users can encounter. It’s a generic error message that indicates something has gone wrong on the server, but it doesn’t provide any specific information about what the problem is. This can make it difficult to diagnose and fix the issue. In this ultimate guide, we’ll explore the causes of Error 500 and provide solutions to help you get your website back up and running. From server issues to coding errors, we’ll cover everything you need to know to understand and troubleshoot Error 500. So, whether you’re a website owner or a developer, this guide is for you. Let’s dive in and unravel the mystery of Error 500!

Article topics:

The Top 5 Causes of Error 500 and How to Fix Them

A beginner’s guide to troubleshooting error 500, the role of server logs in diagnosing error 500, common mistakes that lead to error 500 and how to avoid them, the importance of regular maintenance in preventing error 500, how to use debugging tools to solve error 500, the impact of third-party plugins on error 500, best practices for handling error 500 in your website or application.

Error 500, also known as the Internal Server Error, is one of the most frustrating issues that website owners and developers face. It can occur due to a variety of reasons, ranging from server-side issues to coding errors. In this blog, we will discuss the top 5 causes of Error 500 and how to fix them.

1. Server Overload: One of the most common causes of Error 500 is server overload. This happens when the server is unable to handle the number of requests it receives, leading to a crash. To fix this, you can try upgrading your hosting plan or optimizing your website’s code to reduce the server load.

2. Coding Errors: Another common cause of Error 500 is coding errors. This can happen due to syntax errors, missing files, or incorrect permissions. To fix this, you need to review your code and identify the errors. You can also use debugging tools to help you find the root cause of the issue.

3. Plugin or Theme Conflicts: If you are using a CMS like WordPress, plugin or theme conflicts can also cause Error 500. This happens when two or more plugins or themes are incompatible with each other. To fix this, you can try disabling the conflicting plugins or themes and see if the issue is resolved.

4. Corrupted .htaccess File: The .htaccess file is an important configuration file that controls how your website behaves. If this file is corrupted, it can cause Error 500. To fix this, you can try renaming the file or restoring it from a backup.

5. Memory Limit Exceeded: If your website exceeds the memory limit set by your hosting provider, it can cause Error 500. To fix this, you can try increasing the memory limit or optimizing your website’s code to reduce memory usage.

In conclusion, Error 500 can be caused by a variety of reasons, but with the right approach, it can be fixed. By identifying the root cause of the issue and taking the necessary steps, you can ensure that your website runs smoothly and efficiently.

The first step in troubleshooting Error 500 is to understand what it means. Error 500 is a generic error message that indicates that something has gone wrong on the server-side. It could be due to a problem with the server configuration, a coding error, or an issue with the database. The error message does not provide any specific information about the cause of the problem, which makes it challenging to diagnose.

The next step is to check the server logs. The server logs contain detailed information about the requests and responses that the server receives and sends. By checking the server logs, you can identify the specific error that is causing the problem. The server logs can be accessed through the hosting control panel or via FTP.

Another common cause of Error 500 is a plugin or theme conflict. If you have recently installed a new plugin or theme, it could be causing the error. To troubleshoot this, you can disable all plugins and switch to a default theme. If the error disappears, you can then enable the plugins one by one to identify the one causing the conflict.

Lastly, it is essential to keep your website updated. Outdated software can cause compatibility issues and security vulnerabilities, which can lead to Error 500. Make sure to update your website’s software regularly, including the CMS, plugins, and themes.

In conclusion, troubleshooting Error 500 may seem daunting, but it is not as complicated as it may seem. By understanding the causes of the error, checking the server logs, and keeping your website updated, you can quickly identify and resolve the issue. Remember, patience and persistence are key when troubleshooting errors, and don’t be afraid to seek help from a professional if needed.

Server logs are an essential tool for diagnosing errors on a website. One of the most common errors that can occur is the dreaded Error 500, also known as the Internal Server Error. This error can be frustrating for both website owners and users, as it can prevent access to important content and functionality.

Fortunately, server logs can provide valuable information for diagnosing the cause of an Error 500. These logs record every request made to the server, including any errors that occur. By analyzing the logs, website owners can identify the specific request that triggered the error and determine the root cause.

One common cause of Error 500 is a problem with the server configuration. This can include issues with the server software, such as outdated or incompatible versions, or problems with the server hardware, such as insufficient memory or disk space. By reviewing the server logs, website owners can identify any configuration issues and take steps to resolve them.

Another common cause of Error 500 is a problem with the website code. This can include syntax errors, missing files, or conflicts with other plugins or scripts. By reviewing the server logs, website owners can identify the specific code that triggered the error and take steps to fix it.

In addition to diagnosing errors, server logs can also provide valuable insights into website performance and user behavior. By analyzing the logs, website owners can identify trends in traffic, popular pages and content, and user demographics. This information can be used to optimize the website for better performance and user experience.

In conclusion, server logs are a powerful tool for diagnosing errors on a website, including the dreaded Error 500. By analyzing the logs, website owners can identify the root cause of the error and take steps to resolve it. In addition, server logs can provide valuable insights into website performance and user behavior, making them an essential tool for any website owner.

Error 500, also known as the Internal Server Error, is a common issue that website owners face. It occurs when the server encounters an unexpected condition that prevents it from fulfilling the request made by the user. This error can be frustrating for both the website owner and the user, as it can lead to a loss of traffic and revenue. In this blog, we will discuss some common mistakes that lead to Error 500 and how to avoid them.

One of the most common mistakes that lead to Error 500 is a coding error. This can occur when the website code is not properly written or when there is a syntax error. To avoid this, it is important to ensure that the website code is properly written and that all syntax errors are fixed before the website is launched.

Another mistake that can lead to Error 500 is a server overload. This can occur when the server is unable to handle the amount of traffic that is being generated by the website. To avoid this, it is important to ensure that the server is properly configured and that it has enough resources to handle the traffic.

A third mistake that can lead to Error 500 is a plugin or theme conflict. This can occur when a plugin or theme is not compatible with the website code or with other plugins or themes that are being used. To avoid this, it is important to ensure that all plugins and themes are properly tested before they are installed on the website.

In conclusion, Error 500 can be a frustrating issue for website owners and users alike. However, by avoiding common mistakes such as coding errors, server overloads, and plugin or theme conflicts, website owners can ensure that their website runs smoothly and that their users have a positive experience.

Error 500 is a common issue that website owners face. It occurs when the server is unable to process a request due to an internal error. This can be frustrating for users and can lead to a loss of traffic and revenue for the website owner. However, regular maintenance can help prevent Error 500 from occurring.

Regular maintenance involves checking the website for any issues and fixing them before they become a problem. This includes updating software, checking for broken links, and optimizing the website for speed. By doing this, website owners can ensure that their website is running smoothly and efficiently.

One of the main causes of Error 500 is outdated software. As technology advances, software needs to be updated to keep up with the latest trends and security measures. Failure to update software can lead to compatibility issues and security vulnerabilities, which can result in Error 500.

Another cause of Error 500 is broken links. Broken links can occur when a page is deleted or moved, and the link to that page is not updated. This can lead to a 404 error, which can then lead to Error 500. Regular maintenance involves checking for broken links and updating them to ensure that users can access all pages on the website.

Finally, website speed is also a factor in preventing Error 500. Slow loading times can lead to users leaving the website, which can result in a loss of traffic and revenue. Regular maintenance involves optimizing the website for speed, which can improve user experience and prevent Error 500.

In conclusion, regular maintenance is essential in preventing Error 500. By updating software, checking for broken links, and optimizing the website for speed, website owners can ensure that their website is running smoothly and efficiently. This can lead to a better user experience, increased traffic, and higher revenue.

Debugging tools are essential for any developer to solve errors in their code. Error 500 is a common error that occurs when there is an issue with the server. It can be frustrating to encounter this error, but with the right debugging tools, it can be easily resolved.

One of the most popular debugging tools is the Chrome DevTools. It allows developers to inspect the code, debug JavaScript, and analyze network traffic. To use this tool, simply open the Chrome browser, right-click on the page, and select “Inspect.” From there, navigate to the “Console” tab to view any errors that may be causing the Error 500.

Another useful tool is the PHP error log. This tool logs any errors that occur in the PHP code, making it easier to identify and fix the issue. To access the PHP error log, simply open the file in the server’s directory and look for any errors that may be causing the Error 500.

Lastly, the Apache error log is another useful tool for debugging Error 500. This log records any errors that occur in the Apache server, making it easier to identify and fix the issue. To access the Apache error log, simply open the file in the server’s directory and look for any errors that may be causing the Error 500.

In conclusion, debugging tools are essential for any developer to solve Error 500. By using tools such as Chrome DevTools, PHP error log, and Apache error log, developers can easily identify and fix any issues that may be causing the error. So, the next time you encounter Error 500, don’t panic, just use these debugging tools to solve the issue.

Third-party plugins have become an integral part of website development. They offer a wide range of functionalities that can enhance the user experience and improve the overall performance of a website. However, these plugins can also cause errors, particularly the dreaded Error 500. This error occurs when the server encounters an unexpected condition that prevents it from fulfilling the request made by the user.

The impact of third-party plugins on Error 500 can be significant. When a plugin is poorly coded or conflicts with other plugins, it can cause the server to crash, resulting in the Error 500 message. This can be frustrating for users who are trying to access the website, and it can also have a negative impact on the website’s reputation.

To avoid this issue, it is essential to carefully evaluate the plugins you use on your website. Make sure they are from reputable sources and have been thoroughly tested. It is also important to keep your plugins up to date and to remove any that are no longer necessary.

In addition, it is important to monitor your website regularly for any errors, including Error 500. This will allow you to quickly identify and resolve any issues before they have a significant impact on your website’s performance.

In conclusion, third-party plugins can be a valuable asset to your website, but they can also cause errors such as Error 500. By carefully evaluating and monitoring your plugins, you can ensure that your website runs smoothly and provides a positive user experience.

Error 500, also known as the Internal Server Error, is one of the most common errors that can occur on a website or application. It can be frustrating for both the user and the developer, but there are best practices that can help handle this error effectively.

Firstly, it is important to understand the root cause of the error. It could be due to a coding error, server overload, or a problem with the database. Once the cause is identified, it is easier to find a solution.

One of the best practices for handling Error 500 is to provide a clear and concise error message to the user. This message should explain what went wrong and what steps the user can take to resolve the issue. It is also important to apologize for the inconvenience caused and assure the user that the problem will be resolved soon.

Another best practice is to log the error and monitor it regularly. This will help identify any recurring issues and allow for quick resolution. It is also important to have a backup plan in case of a server crash or other technical issues.

In addition, it is recommended to have a custom error page that is visually appealing and provides helpful information to the user. This can include links to other pages on the website or application, contact information for support, and a search bar to help the user find what they are looking for.

In conclusion, handling Error 500 requires a proactive approach and a focus on user experience. By following these best practices, developers can minimize the impact of this error and ensure a smooth and seamless experience for their users.

In conclusion, Error 500 is a common issue that can occur on any website. It can be frustrating for both website owners and users, but understanding the causes and solutions can help alleviate the problem. Some of the common causes of Error 500 include server errors, coding errors, and plugin conflicts. To solve this issue, website owners can try troubleshooting steps such as checking server logs, disabling plugins, and updating software. It’s important to note that Error 500 can also be a sign of a more serious issue, so seeking professional help may be necessary. By following the tips and tricks outlined in this ultimate guide, website owners can ensure their website runs smoothly and efficiently, providing a positive user experience for all.

This article incorporates information and material from various online sources. We acknowledge and appreciate the work of all original authors, publishers, and websites. While every effort has been made to appropriately credit the source material, any unintentional oversight or omission does not constitute a copyright infringement.

All trademarks, logos, and images mentioned are the property of their respective owners. If you believe that any content used in this article infringes upon your copyright, please contact us immediately for review and prompt action.

This article is intended for informational and educational purposes only and does not infringe on the rights of the copyright owners. If any copyrighted material has been used without proper credit or in violation of copyright laws, it is unintentional and we will rectify it promptly upon notification.

Please note that the republishing, redistribution, or reproduction of part or all of the contents in any form is prohibited without express written permission from the author and website owner. For permissions or further inquiries, please contact us.

More stories

Leave a reply Cancel

Your email address will not be published. Required fields are marked

Save my name, email, and website in this browser for the next time I comment.

What Is a 500 Internal Server Error, and How Do I Fix It?

How do you go about fixing a server error? You wouldn’t use the same steps as troubleshooting a Microsoft SQL Server Error 18456 . But, with any error you receive, you first need to know why the error occurred before you can attempt to fix it.

Suppose you see an error message that reads 500 Server Error or something similar (Error Code 500, Temporary Error (500), HTTP Error 500, 500 Internal Server Error, etc.). In that case, something has gone wrong with the website you are trying to view.

The 500 internal server error message indicates that something has gone wrong on the server side of the website. While various issues can cause this error, it's usually related to a problem with the website's code or server configuration.

What Causes a 500 Internal Server Error?

The cause of a 500 internal server error can be either very simple or very complicated. If you are a website visitor, something is wrong, and your best option is to simply try again later.

A 500 internal server error could be very complex if you are expected to fix it. That’s because the server gives a generic message when it cannot tell what’s wrong.

All you know is that the web page that was supposed to be displayed isn’t working. You may have a long troubleshooting journey ahead of you or something a simple server reboot can solve. 

Solutions to 500 Internal Server Error 

Finding a solution to a 500 internal server error is challenging due to the sheer uncertainty of the error. Until you know exactly what went wrong, there isn’t much you can do to fix it or make it less likely to happen again. 

Consider looking at the permissions on the files and folders on the server, among other tools for troubleshooting server connection errors , to discover and fix the problem. This guide provides a list of places to begin your troubleshooting journey.

How to Fix a 500 Internal Server Error on a Website

If you are the owner or developer of a website, you or one of your users may have faced a 500 Internal Server Error. This error is bothersome since it prohibits users from accessing your website. However, it is not the end of the world because there are various solutions.

1. View Relevant Server Logs 

The first thing you should do when you encounter a 500 Internal Server Error is to check the server logs. The logs will provide you with more information about the error, which will help you to determine the cause. You can access the logs through your server control panel or by contacting your hosting provider.

2. Check Your .htaccess File

If the server logs don't provide helpful information, the next thing to check is your .htaccess file. A misconfigured .htaccess file can cause the error. Try renaming the file to see if the error goes away. If it does, create a new .htaccess file and add the necessary code or edit the existing file if you can locate the issue.

3. Ensure PHP Is Configured Properly

If your website runs on PHP, you may need to increase the memory limit, as a low memory limit can cause a 500 Internal Server Error. You can increase the limit by adding the following code to your wp-config.php file:

4. Deactivate a Plugin or Theme

A plugin or theme incompatibility issue may be the source of the 500 Internal Server Error, and you may need to disable one or both of them. Try turning off your plugins and themes individually to determine which ones, if any, are the culprit.

5. Contact the Server Admin

If the server is a part of your organization, but you are not the server admin, it’s a good idea to reach out to them. Inform them immediately so they can begin troubleshooting as soon as possible.

What To Do if It Starts Showing a Different Error Entirely

If your website shows a different error, such as an HTTP response code , the steps to fixing it may vary depending on the code thrown. Checking the logs is still a great place to start, but you must research the code to determine how you troubleshoot the issue.

How to Contact the Webmaster in Case of 500 Internal Server Error

Assuming you need access to this page and the webmaster isn’t a part of your organization, all is not necessarily lost. The person responsible for keeping a website healthy and happy is often a matter of public record. 

Many websites offer a convenient Contact Us section. More often than not, this will be a link to someone who hopes you want to buy something, but if you can get through to a human, they can pass the information along. 

If you cannot view the Contact Us page, use your favorite web search engine and search the phrase: whois for (URL). If you are trying to access a site's subdomain, use the main domain, not the subdomain.

The whois result will usually include an email address for the website owner. This might be labeled as the Administrative Contact, Registrant Email, or something similar.

You can inform them of the error via that email. However, be aware that the email address listed could be old and might not be monitored. There’s no guarantee that anyone will read or act on your email. 

A 500 Internal Server Error can be frustrating, but it's not the end of the world. Following the steps outlined in this guide, you should be able to fix the error and get your website back up and running quickly. If you are not in control of the website, your only option is to attempt to contact the hosting provider or website admin and try back another time.

For server administrators having issues troubleshooting with their servers, there is still hope. Liquid Web offers 24/7/365 support to assist you with server-side issues. Contact Liquid Web and find out if our managed hosting is the right solution to keep your server and website live.

Join our mailing list to receive news, tips, strategies, and inspiration you need to grow your business

Keep up to date with the latest Hosting news.

How To Get Rid HTTP Error 500?

How do i fix a http 500 error how to troubleshoot 500 internal server error.

Have you got the HTTP error 500 while you browse for a website? This error usually means that there is an issue on the website’s backend. Usually, this error occurs temporarily because of a glitch in the website’s programming. Let’s learn how to fix HTTP Error 500  using these solutions.

Table of Contents

Top 5 Ways To Fix the HTTP Error 500

Go back to the previous page and refresh it.

This may sound simple, but if the problem is a quick loading issue, refreshing the page may help. Reload the page and see what happens before attempting anything else on this list.

You can simply click the F5 key on your keyboard to refresh the page or simply press Ctrl + R.

Return after sometime

If the fault occurs on the server side, the website owners are probably working to rectify the problem as soon as feasible. Reload the URL and see if the development team has fixed the problem after a few minutes or wait up to an hour.

Clear the cookies in your browser

The HTTP 500 error is sometimes caused by cookies associated with a website. As a result, deleting them and refreshing the browser often resolve the issue. To clear cookies, follow these steps:

1. First, select “Settings” from the drop-down menu.

2. Next, select “Privacy and security” from the menu.

3. Next, go to “Advanced” and choose “Clear browsing data.”

4. Finally, select “clear data.”

Check your URL on “Down for Everyone or Just Me”

How To Split Screen On iPad?

How To Purchase Kindle Books On iPad, iPhone?

‘Down for everyone or just me’ This site will help you find out if the URL is not working on your browser or for others. All you have to do is enter the URL of the website that isn’t working.

Contact the website

If the website is down for everyone then you can try reaching out to the website administrator. The team might be working on fixing the issue if they are aware of the error. But if they aren’t aware of the error then you are actually helping everyone!

Now that you know how to get rid of the HTTP Error 500, try these fixes to solve the issue. Learn how to fix other 5xx errors .

Frequently Asked Questions

Q1. how do i fix an http 500 error.

Ans. Follow these steps to fix the HTTP 500 error:

1. Go back to the previous page and refresh it

2. Return after sometime

3. Clear the cookies in your browser

4. Check your URL on “Down for Everyone or Just Me”

5. Contact the website

Q2. Is a 500 error my fault?

Ans. The 500 Internal Server Error is a general HTTP status code that indicates that something has gone wrong on the website’s server, but the server is unable to provide more precise information about the issue.

Q3. What are the top reasons why you get HTTP 500 errors?

Ans. 1. Server Issue

2. Coding error or CGI/PERL syntax

3. PHP timeout error

Q4. What does error 500 mean on Google?

Ans. It is a general error from the server that means something has gone wrong. This could happen because of the corrupted or outdated cookies and cache. Also, there could be a problem with the server request.

Is Samsung Smart Tv Introducing NFTs?

How To Clear Cookies On Android Phone?

How To Redeem Genshin Impact Codes Livestream Codes? (2023 Update)

How To Screenshot On Windows 11?

• Security Education
• Website Security
• WordPress Security

What is a 500 Error & How to Fix It

• September 1, 2022

A frustrating interruption to anyone’s day is the infamous 500 error .

When it happens not only do you lose traffic or potential site revenue, but it can also reflect badly on your site’s reputation and even affect your Google rankings. Furthermore, 500 errors can sometimes be an indicator of compromise — the result of unsuccessful malware, damaged .htaccess files, or broken script injections nestled somewhere on the site.

In this article, we’ll explain more about 500 internal server errors , what they mean for you and your website visitors, and how to troubleshoot these errors to get your website back online again.

What is a 500 error?

How are 500 errors different from other internal server errors.

• What are the most common causes of a 500 internal server error?

Can a 500 error be caused by malware?

• How do I fix a 500 internal server error on my site?

Do 500 errors impact SEO?

• Resolving 500 errors due to malware

The Internet Engineering Task Force defines the 500 Internal Server Error as follows:

“The 500-error status code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.”

A 500 error is a server-side error that indicates that something went wrong on the website’s server, but the server is unable to provide specific details about the problem. It’s is a generic message displayed when no other message is suitable for the situation.

Something has gone wrong with the website, but the problem is not with your browser, your internet connection, or your computer. It’s a message that indicates there is a general problem with the site you’re trying to access or the server where the site resides, as seen below.

500 error messages can come in all sorts of flavors, but they all mean the same thing. Here are a few variations of 500 errors you might encounter in your browser:

• 500 Internal Server Error
• HTTP Error 500
• Temporary Error (500)
• The website cannot display the page – HTTP 500.
• Is currently unable to handle this request. HTTP ERROR 500.

These are only a handful of the possible messages you might find when encountering a 500 error. In fact, some websites even have their own custom internal server error messages.

But if you receive this message, you can be sure that an unexpected problem has been detected by the server.

There are many types of internal server status error codes and they all mean different things.

To help you understand the difference between generic 500 errors and other types of internal server errors, we’ve outlined some of the common types of 5xx responses you might encounter on your site.

• 500 error: indicates that the server encountered an unexpected problem. This error code comes up when something unexpected happens on the server which prevents it from completing the request, but no additional information is shown.
• 501 error: HTTP status code for not implemented. This indicates that the server is unable to execute the request and is either unable to identify the goal of the request, or does not have enough power to execute the request.
• 502 error: bad gateway. Essentially, an invalid response was detected. The server was doing a job as a proxy or a gateway and received an invalid response from a different upstream server. If you are using a WAF, this could indicate a problem with your server.
• 503 error: a service is unavailable. This occurs when the server gets too many tasks and is overloaded, down due to maintenance, or has been taken down by malware.
• 504 error: Gateway timeout. The server, which was performing as a proxy or a gateway, wasn’t able to identify the request within the fixed time limit.
• 505 error: HTTP version not supported by server. The server isn’t able to identify the HTTP protocol used in the request.
• 511 error: network authentication . The server requires user authentication to access the request.

With the exception of a 500 error, the majority of server errors provide clear reasons for the status response that can help you pinpoint the issue and resolve it.

But don’t despair; there are a number of potential causes for the vague and generic 500 server error. Let’s examine some of these sources before we move on to possible solutions.

What are the most common causes of a 500 error?

As the name suggests, a 500 internal server error is a general issue with a webserver. They can be caused by a plethora of issues ranging from relatively benign to serious.

And unlike 503 or 504 errors, a 500 server error won’t clearly outline how to fix the problem nor what the problem is in the first place.

So, let’s take a look at some examples of elements that could be causing the problem.

• Your browser cache needs to be cleared
• Incorrect database login credentials have been used
• The website’s database is corrupt
• WordPress core files have become corrupted
• Issues exist within the database server
• PHP memory limit is exhausted
• The server has run out of disk space
• .htaccess file is corrupt or broken
• Issues exist with third-party plugins and themes
• There could be PHP timing out or errors with third-party plug-ins
• There are incorrect file/folder permissions
• There are CGI or Perl script errors
• Your hosting company made a change

Furthermore, many of these issues can arise due to a malware infection. Let’s explore how these issues could be indicators of compromise.

Hackers often make modifications to compromised sites — anything ranging from injecting extra code into existing files to creating thousands of malicious files and posts. These can result in 500 errors.

The following scenarios can seriously affect website functioning and result in server errors:

• Injected malicious code contains bugs
• Injected malicious code interferes with your website’s functionality
• Malicious code is injected into the wrong location, breaking legitimate code
• Hackers completely replace legitimate code their own, breaking any site functionality that depended on the original legitimate file
• Hackers delete entire files or directories from the server
• Hackers encrypt legitimate files
• Too many malicious files (ie. doorways) exhaust disk quota
• The database becomes corrupted during compromise
• An attacker runs their own tools on the server, exhausting available resources required for site functionality (ie. cryptominers, DDoS bots, spam servers)

Example of how malware can cause 500 errors

Here’s an excerpt of a decoded black hat SEO doorway script that can lead to 500 errors on your website.

Since this code works for search engine crawlers, under certain conditions it can cause search engines and security scanners to return 500’s for your website.

Fortunately, there are a few ways to troubleshoot and resolve 500 internal server error notifications. Let’s dive in!

How do I fix a 500 error on my site?

Here are a few ways to troubleshoot 500 errors to get your site back up and running.

1. Clear your browser cache

This is a good troubleshooting step. This is done before looking for more debugging on your site to confirm that the issue isn’t cached on your end.

Below are instructions on how to clear cache on Google Chrome.

• Open Chrome.
• Click on the icon with the three dots icon at the top right of the browser window.
• Go to More tools then select Clear browsing data .
• Select the Time Range field, then choose one of the options that appear. To delete everything, select All time .
• Select Clear data to clear the cache.

You can opt to clear only your browsing history, or you can choose a more thorough clearing of your cache by including cookies and other site data in the cache clearing.

2. Reload the page

When you receive the 500 error, wait a minute and then try reloading the page (F5/Ctrl + F5). It is possible that the host or server is overloaded, and the site should come back shortly. You could also try a different browser to rule out the issue.

To ensure that you are not seeing a cached page on the website, try loading the website with an appended variable like this: example.com ?nocache

Another option to try is to paste the website into: downforeveryoneorjustme.com

This website can confirm if the problem is on your side, or the website is actually down. If you’re a Sucuri client, you can leverage our uptime monitoring to identify if your site is up and running or problems are detected there.

Something to note is that 500 server errors can happen immediately after you update a plug-in or theme on your WordPress site, but these are usually resolved after a refresh.

3. Check for recently installed or updated software

Investigate to see if any recently installed or upgraded software on your website failed to install or upgrade. To refresh your software, check the vendor’s website for specific instructions.

You’ll also want to audit your website for any new and unfamiliar plugins or themes. If you find anything unusual, this may be an indicator of compromise.

Investigate further to pinpoint:

• What the unfamiliar software or component is
• How long it’s been installed on your site
• Whether or not it’s legitimate

If you encounter anything that looks suspicious, remove the component and scan your website for malware .

4. Check your server logs

Make use of your website monitoring and error logs . Server errors are usually logged in error.log and will contain any important information about what’s broken.

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

Be sure to disable these WordPress debugging options as soon as you’re done troubleshooting. Any error messages found there may disclose sensitive information about your server and website, making it easier for a bad actor to hack it.

5. Check your plugins, extensions or themes

Extensible components like plugins and themes can often cause 500 internal server errors.

Most times you’ll see the error immediately after doing an update or installing something new. It’s advisable to do updates one at a time, otherwise it may become difficult to determine which update caused the internal server error.

You can again use the debug mode to coax your website into providing a specific error that will reference the broken component. As described in the last step, debug mode can be enabled in WordPress by adding the following line to your website’s wp-config.php file:

If you can get a specific error referencing a specific plugin or theme, try disabling that component and see if your website comes back online.

If not, continue troubleshooting. You can also check the error_log file in your website’s docroot to see if you can find the specific issue.

Another option is to try troubleshooting by deactivating all your plug-ins and testing them individually. We’ll outline a few options depending on whether you can access your Admin panel or not.

If you are still able to access your Admin panel in WordPress:

• Navigate to Plugins > Installed Plugins
• Select the checkbox at the top of the list to select all plugins
• Open Bulk Actions and select Deactivate .
• Click Apply to disable all your plugins to start troubleshooting.

If you are unable to access your WordPress Admin panel, try using sFTP to disable plugins:

• Connect to your server using your sFTP client.
• Navigate to the wp-content folder.
• Right-click on plugins and select Rename .
• Enter a new name for the folder. (ie. deactivated-plugins )
• Your WordPress site won’t be able to locate the folder and all plugins will be deactivated.

And if you find disabling all our plugins does in fact fix the issue, you’ll have to determine one caused the problem. Activate each of them one at a time and then reload the site after each activation. When you see the 500 internal server error return, you will know which one caused the error. Then reach out to the plugin developer for assistance.

6. Check for errors establishing a database connection

500 internal server errors can also occur from a database connection error.

Depending on your browser you might see a number of different errors, but both generate a 500 HTTP status code in your server logs. With this error, your entire page will appear blank as no data can be retrieved to render the page because the connection is not working properly. This will break the front-end of your site and will also prevent you from accessing your WordPress dashboard.

A few reasons why this happens:

• One of the most common reasons is that your database login credentials are incorrect.
• Your database could be corrupt. With a lot of moving parts with themes, plugins, and users constantly deleting and installing them, databases occasionally get corrupted. This could be due to a missing or individually corrupted table, or perhaps some information was deleted by accident.
• There are issues with your database server. A number of things could be wrong on the web hosts end. The database could be overloaded from a spike in traffic, or it could be unresponsive from too many concurrent connections.

To troubleshoot a database connection error, first take a backup of your website. Then run through the following steps:

• Check your database login credentials. This is a common issue that should be ruled out before troubleshooting further, so make sure details in your wp-config.php file are accurate.
• Check for a corrupted database. If your database has become corrupted, WordPress has a database repair mode you can initiate. Add the following to your wp-config.php file: define(‘WP_ALLOW_REPAIR’, true); then navigate to https://yourdomain.com/wp-admin/maint/repair.php . From here, you’ll have the option to repair and optimize your database.Be sure to remove the WP_ALLOW_REPAIR statement from wp-config once you’re done to ensure nobody else can access the page on your site.
• Check with your hosting provider. Too many concurrent connections can cause database connection errors and many hosts limit the number of connections that are permitted for any given server.
• Restore a backup . If you aren’t worried about losing any data, try restoring a backup of your website files and database.

7. Check for problems with your .htaccess file

The .htaccess is a crucial file for Apache server environments. If you are using WordPress with Apache and have recently started encountering 500 errors, your .htaccess file could be corrupt or damaged.

Moreover, the .htaccess file is notorious for being targeted during a compromise. Attackers can use the file to conceal malware, redirect search engines to spam websites , inject malicious content into a website, modify php.ini values , or even conceal backdoors .

To begin, you’ll want to assess if any problems with your .htaccess are the result of a hack or an update to your .htaccess file.

You can locate your .htaccess file by accessing your website files through a file manager like cPanel or via FTP/SFTP. The file will probably be located in your public_html directory. There’s a good chance your server will hide this file from view by default and you’ll need to toggle hidden files to see it.

8. Check for permissions errors

A permissions error for an important file can also result in 500 internal server errors.

You can refer to the WordPress Codex article on changing file permissions for more details.

9. Check for PHP memory limit on your server or website

A 500 internal server error could also be caused by exhausting the PHP memory limit on your server. Try increasing the limit.

PHP timeouts can also occur from the lack of PHP workers , although these typically cause 504 errors — not 500 errors. These determine how many simultaneous requests your site can handle at any given time. Simply put, 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.

Follow the instructions below on how to change this limit in cPanel or Apache.

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 .
• To choose the PHP version, select Switch to PHP Options .
• Click on the memory_limit attribute and change its value.
• Click Save .

Increase PHP Memory Limit in Apache

You can modify server behavior from your .htaccess file right down to a directory specific level:

• Log into your site via FTP or SSH.
• Locate your .htaccess file.
• Add or replace the following line in your .htaccess file, modifying xxx with the new memory limit value in megabytes that you want to set: php_value memory_limit xxx
• Save the changes.

You can verify that the new setting is active by creating a PHP test file containing the following code in the same directory as your .htaccess file:

Simply load your new test file in a browser and the Local Value should display the value that you set in your .htaccess file.

Increase PHP Memory Limit in WordPress

Sometimes, all that needs to be done is to increase the amount of memory that WordPress itself is able to consume. This can be done by adding the following line to wp-config.php :

10. Check for server issues with your host

Sometimes these errors can be difficult to troubleshoot without an expert, so you can always check with your host. Ask your service provider to access your error logs and help you pinpoint the issue.

500 errors can have a negative impact on SEO if not addressed.

Googlebot will typically retry pages that are serving 500 errors. If they persist, Googlebot will reduce the crawl frequency and over time eventually drop the URLs from the index.

Moreover, if the 500 errors are happening due to a malware infection and Google identifies that your website has been hacked or is serving malicious content, the infection could result in blocklisting — and this can significantly impact your search rankings and organic traffic.

So, the first step is to determine why the 500 errors are occurring and address them to mitigate risk for your SEO.

Resolving a 500 error due to malware

500 internal server errors are extremely frustrating, but after these troubleshooting tips you should be able to get your website back up and running in no time.

Keep in mind that these types of errors can be caused by the plethora of issues outlined in this post, but sometimes malware infections can also result in 500 errors.

• It’s in malware’s best interest to keep the victim website online, but if a malware injection is buggy and breaks the code on the website it can result in a 500 error.
• Malware like cryptominers can eat up resources on the server, causing timeouts, slow performance and 500 errors.
• In the wake of a blackhat SEO infection, thousands of spam pages can be generated on a website. Search engines will continue to try to crawl these pages even after they’ve been removed, and result in degraded performance and sometimes server timeouts or 500 errors.

Rianna MacLeod

Rianna MacLeod is Sucuri’s Marketing Manager who joined the company in 2017. Her main responsibilities include ghost-writing technical content, SEO, email, and experimentation. Rianna’s professional experience spans over 10 years of technical writing and marketing. When Rianna isn’t drafting content or building templates, you might encounter her hiking in the forest or enjoying the beach. You can find her on Twitter and LinkedIn .

Related Tags

• Website Monitoring ,
• WordPress Plugins and Themes

Related Categories

You may also like.

• Sucuri Labs
• Website Malware Infections

“Free” Symchanger Malware Tricks Users Into Installing Backdoor

• December 1, 2020

Ask Sucuri: How to Stop Brute Force Attacks?

• December 14, 2016

The Dangers of Hosted Scripts – Hacked jQuery Timers

• November 10, 2014

Public Service Annoucement: LinkedIn Users Change Your Passwords

• June 6, 2012

APRIL FOOLS: No Serious Security Vulnerability on WordPress 3.x – Remote Command Execution

• April 1, 2011

Uncommon Radixes Used in Malware Obfuscation

• March 15, 2019

Sucuri Cookie Policy See our policy>>

Our website uses cookies, which help us to improve our site and enables us to deliver the best possible service and customer experience.

• Free hosting
• Shared hosting
• LiteSpeed hosting
• Semidedicated hosting
• Reseller hosting
• LiteSpeed reseller hosting
• UnManaged VPS cloud
• Managed VPS Cloud
• Dedicated servers
• SSL certificates
• Domain registration
• Change hosting
• Why SupportHost
• Client area
• Request support
• Password reset

500 error: how to solve

The error 500 can prevent you from accessing a page or website. When this error occurs, in fact, the server sends an HTTP error 500 status code to the browser to communicate a generic problem that prevents you from reaching the requested address.

When error 500 prevents you from reaching a site, the solution is to try again later when the problem has been resolved.

But what if error 500 occurs on your site ? There are several checks you can do to try and fix it as soon as possible, so you won't have a negative impact on your site visits and, more importantly, sales.

In this article,500 error: how to solve it, we'll see what kind of problem is behind a 500 error. We'll look at the possible causes and see what solutions you can implement to quickly fix the error and get your site back online.

To top it off, we will also see how to get around the error 500 in case you are not the owner of the site, but just want to access a temporarily unreachable resource.

Table of Contents

What is Error 500?

The definition of Error 500 given by the IETF (Internet Engineering Task Force) is as follows:

Status code 500 (Internal Server Error) indicates that the server encountered an unexpected condition that prevented it from fulfilling the request. ( RFC7231 )

So let's start in order, what is an HTTP status code?

To allow us to reach an address, the browser must send a request to the server on which the site is hosted. The server, in response, returns a code to communicate the outcome of the request.

HTTP status codes are composed of 3 digits, the first of which indicates the category:

1XX : status codes starting with 1 are the informational ones. They indicate that the request has been received and they have yet to process it.

2XX : these codes are the confirmation codes, meaning that the request has been received and processed.

3XX : these are the redirection codes that are used when a resource has been moved temporarily (redirect 302) or permanently (as in the case of redirect 301 )

4XX : these codes indicate client errors, such as error 403 and error 404 indicating a resource not found.

5XX : this is the category of server errors. It includes error 502 bad gateway , 504 gateway time-out and error 508 , as well as error 500.

So these are the five categories of standard HTTP status codes. Then there are other codes that are always in decimal form and provide further details about the status of the request.

An example is given by Microsoft IIS (Internet Information Services) servers which in the case of error 500 allow getting more specific about the causes of the error.

• 500.0 : the error is in a module or in ISAPI
• 500.11 : one of the applications on the server is about to be stopped.
• 500.12 : an application is about to restart.
• 500.13 : server overload
• 500.15 : request for global.asax file not allowed
• 500.19 : configuration data is not valid
• 500.21 : one of the modules was not recognized
• 500.22 : the configuration of an HTTP module of an ASP.NET web application is not valid in Managed Pipeline mode
• 500.23 : the configuration of an HTTP handlers element of an ASP.NET web application is not valid in Managed Pipeline mode
• 500.24 : problems with the configuration of an identity change in Managed Pipeline mode
• 500.50 : there was a rewrite error when processing the RQ_BEGIN_REQUEST message
• 500.51 : there was a rewrite error while processing GL_PRE_BEGIN_REQUEST message
• 500.52 : there was a rewriting error while processing the message RQ_SEND_RESPONSE
• 500.53 : there was a rewriting error while processing the message RQ_RELEASE_REQUEST_STATE
• 500.100 : the error occurred within the ASP application.

Error 500 can occur in a number of ways, here are some of the most common variations you may come across:

• 500 Internal Server Error
• HTTP 500 Internal Error
• HTTP Error 500
• Internal Server Error
• The website cannot display the page
• HTTP 500 - Internal Server Error
• Internal Server Error 500
• 500 Server Error
• 500 Internal Server Error. Sorry something went wrong.
• Temporary Error (500)
• Server Error 500 internal
• Error 500 HTTP
• Error 500 Internal Server Error
• An error occurred during data request (500)

The error message can change from one server to another and on different browsers. In the screenshot below you can see an example of the error on Google Chrome.

Other browsers, such as Firefox, however, may also simply show you a white screen like this.

Causes of error 500

Error 500 can result from several causes ranging from an error in the .htaccess file to server unavailability due to maintenance. In this paragraph, we will examine some of the most common causes that can generate this type of error. In the next one, instead, we're going to see how to proceed step by step to solve it.

Errors in the file .htaccess

The .htaccess file is used to insert directives for Apache servers. For example, you can use the .htaccess file to implement 301 redirects.

The presence of an error, such as an incorrect command or even a syntax or writing error, within this file, can cause the server to respond with an error 500.

Permissions errors

Permissions can be set for all files and folders on the server. This determines which users are granted permissions to read, write and execute files.

For example regarding permissions for WordPress files and folders you should use the following permissions:

• 644 or 640 for files
• 755 or 750 for folders.

An error in permissions can be the cause of a 500 error.

Problems with a script

An error in the syntax or code of a script, but also in the path setting can cause a 500 error. Also, you may have problems with Perl scripts if they were loaded in binary mode instead of ASCII , or if the necessary modules were not installed.

Problems with the server

Error 500 may be due to problems with the server, for example, if there is an overload on the server or due to maintenance . In these cases, you can wait and try to reload the page after some time or contact your provider.

Compatibility problems with plugins and themes

When using a CMS with extensions, plugins, or themes, a common situation you might find yourself in is a 500 error right after installing one of these components.

To quickly figure out if the cause of the 500 error is a plugin you can disable all of them temporarily. You can do this directly from the dashboard, but if you can't log in, there are other methods as well, which we'll see later in the section on Error 500 solutions.

Problems with WordPress core files

Although error 500 is not directly related to the platform you're using, there are cases where the problem can stem from the CMS files.

For example, in the case of WordPress, it is possible that the core files have been damaged and need to be restored. In this case, you'll have to proceed to reinstall WordPress without losing the content you've created so far.

Keep in mind that it is essential to make a backup before proceeding, to avoid losing your content.

Database problems

A 500 error can result from a problem with the database. Among the most common causes for which you may find yourself having your site down are:

• wrong credentials to access the database
• corrupted database
• database server overload.

PHP memory limit

If a script exceeds the memory threshold, the process is inhibited and you may be faced with a 500 error.

500 error: how to solve it

In addition to looking at the possible causes, we just saw there are other checks we can do to determine the origin of error 500. First, let's start by analyzing the log files , and then see how to practically fix the common problems we saw earlier.

Check the log files

The cause of error 500 may not fit into the list of common causes we just reviewed. That's why one of the first things to do is to go and check the server's error logs or logs.

Access the site's files, for example through the cPanel file manager, and look for a file like this "error_log":

With WordPress you can also enable debug mode by adding this code to the wp-config.php file:

Check file and folder permissions

You should make sure that files and folders on the server have proper permissions. For example in the case of WordPress, files should have permissions 644 or 640, while folders should be 755 or 750.

You can check and possibly change the file permissions in several ways. For example, you can use the cPanel file manager. With all our shared hosting plan , WordPress hosting , VPS cloud hosting and dedicated servers you can conveniently manage your site files from the file manager.

Next to each file, you'll see a column that says Permissions and indicates the permissions of the file. In this example, all files are set to 644 and folders to 755.

If you want to change the permissions just click on the number corresponding to the file you want to change, type the new code and click on Save as you see in this screenshot:

You can also change file permissions with an FTP client. For example, you can see how to do it with Filezilla , in our guide dedicated to one of the most used FTP clients.

HTTP error 500 and problems with the .htaccess file

As we said before, one of the causes of an internal server error can be an error in the .htaccess file .

To check if the .htaccess file is the cause, all you have to do is rename it temporarily. You can always do this using the file manager or by accessing the server via FTP.

If you use cPanel's file manager and can't find the file, you'll have to check the settings and make sure the Show hidden files (dotfiles) option is enabled.

Once you have located the .htaccess file, simply rename it and see if the error 500 has been resolved.

If the error 500 no longer appears after renaming the .htaccess file, you will need to locate and correct the error in it. After that, you can rename the file back to its original name ( .htaccess ).

Change PHP memory limit

If one of the active processes on your site is exceeding the PHP memory limit , you may see an error 500.

In this case, you can change the memory limit to see if this is the cause of the error. There are several ways to do this, one of the easiest is to proceed directly from cPanel .

After logging into cPanel click on Select PHP version from the Software section.

This tool allows us to change the PHP version and modify the memory limit.

Click on the Options tab and scroll down to memory_limit , then set the PHP memory limit according to the options the drop-down menu allows you.

Deactivate plugins

Sometimes activating a new plugin or theme can cause a 500 error. To figure out if the cause of the error is a plugin you can temporarily disable all plugins and see if the error gets resolved.

You can deactivate WordPress plugins in several ways: from the dashboard, through the control panel (or via FTP), but also using phpMyAdmin or through WP-CLI.

After deactivating all plugins check if the 500 error has been resolved. In this case, you will have to reactivate the plugins one by one and check if the error reoccurs to find the responsible plugin.

Disable plugins from the dashboard

The easiest way to deactivate all plugins is to do it directly from the dashboard:

• check the box to select all plugins
• from the Group Actions drop-down menu choose Deactivate
• then click on Apply button and all plugins will be deactivated.

If you can't access the dashboard there are other ways to disable plugins.

Disable plugins from file manager

You can disable all plugins by simply renaming the folder that contains them. You can access your site files from cPanel file manager or by using an FTP client like Filezilla.

Usually the path to the plugins folder is this: /public_html/wp-content/plugins. Rename it, as you see in this example and check if error 500 still occurs.

After that you'll have to rename the folder again, using the original name and you'll be able to manually reactivate plugins from the WordPress dashboard.

Disable plugins with phpMyAdmin

We can use phpMyAdmin to deactivate plugins directly from the database. In this case, remember that before making changes to the database it is always wise to create a backup .

To deactivate plugins we just need to open the wp_options table and edit the active_plugins record inserting a:0:{} inside the option_value .

You can follow the procedure step by step in our guide to phpMyAdmin for WordPress .

Disable plugins with WP-CLI

WP-CLI allows us to manage our WordPress installations from the command line. With one command you can deactivate all plugins:

Also in this case you can check if the error depends on one of the plugins and go to reactivate them one by one from the dashboard.

Contact support

If you can't find the cause of the error 500, you can always contact support, indicate the checks you have already done and find a solution to the problem with support.

Alternatively, if you want to entrust the technical management of the site to a team of professionals, you can consider switching to a managed WordPress solution . In this way, the resolution of errors of this type, as well as the maintenance operations of your site will be entrusted to experienced hands.

How to solve as a user

The solutions we have seen can be applied in case the error 500 occurs on your site.

If, on the other hand, error 500 appears on the site you are trying to visit, there is little you can do.

Since this is a server-side error, it does not depend on your connection or the device you are using. In fact, if you try to it access from another device or browser, you will find yourself facing the same error.

You can try to check the status of the site with a free service like Down for Everyone or Just Me that allows you to understand if the site is online or not.

In such cases, then, you just have to wait and try to connect to the site again later. If you need to access the content of the page, you can always take advantage of the Google cache to access the version of the site stored in the search engine cache .

As we have seen in this article,500 error: how to solve it, the error 500 is a server error that occurs when something goes wrong and makes it impossible to reach the desired site.

Since it is a generic error, the browser doesn't offer more information about what caused the problem, it just shows the HTTP error 500 status code, or in other cases, it just shows you a blank screen. For this reason, the only way to solve it is to rule out possible causes one by one.

In this article, we've seen what the most common causes of error 500 are, and we've looked at possible ways to fix it in case the problem occurs on your site. If, on the other hand, you come across the error while you visit a site, there's a little trick you can use to still access the resources you were looking for.

Have you ever seen an error 500 on your site? How did you solve it? Let me know in the comments below if the solutions in this article helped you solve it or if you had to use some other method, so we can add more solutions to help out our readers.

Ivan Messina

Search the blog, popular articles.

• How to choose a web host
• Dedicated server price
• Cloud server hosting price: how much is it?
• How to transfer WordPress.com to WordPress.org
• Cloud hosting vs shared hosting: differences

Best sellers

• WordPress hosting
• WooCommerce hosting

Try our shared hosting for 14 days for free and without obligation. If you're happy with it, you can upgrade to a paid plan without losing the work you've done!

Related posts

502 bad gateway: how to solve it

508 error: how to solve it

504 gateway timeout: how to solve the error

Leave a reply cancel reply.

Your email address will not be published. Required fields are marked *

By adding my comment I declare that I have read the privacy policy and give my consent to the processing of data.

This site uses Akismet to reduce spam. Learn how your comment data is processed .

Privacy Overview

• Trending Now
• Data Structures
• Foundational Courses
• Data Science
• Practice Problem
• Machine Learning
• Web Development
• Web Browser

• Explore Our Geeks Community
• Top 7 Projects in Robotics For Beginners and Intermediates
• How to create marketing copy using ChatGPT?
• 5 Best Password Authenticator Apps
• Top 4 Blogging Platforms That You Can Consider
• Appropriate usage of social networks
• How to Join GDG(Google Developer Group)?
• Difference between Residential Proxies and Datacenter Proxies
• How to Become Member of Facebook Developer Circle and what's it's Benefits?
• 5 Best AI Image Generators in 2023
• How to Reinstall Wireless Drivers in Windows?
• Difference Between Hadoop and MapReduce
• How to Delete Google Chrome Browsing History?
• What are chrome extensions?
• How to Create a New User in Windows 10?
• Top 10 Best Linux Distros For Laptops
• 8 Most Used Data Science Tools
• How Amazon's Titan & Bedrock Will Rival ChatGPT, BARD and Other AI Chatbots?
• How to Hide a Folder in Windows?
• Top 5 Programming Languages For Ethical Hackers

How to Fix “500 Internal Server Error”?

Error codes are numerical identifiers used in computer systems and software to represent specific errors, issues, or conditions that occurred during the execution of the program. The “ HTTP 500 – internal server error ”, is one of the error codes which gives a generic response indicating the server’s failure in fulfilling the client’s request. The error code 500 is generic because it indicates that the server could not find a better 5xx code to match the response. This failure could be the result of any unexpected condition that occurred on the server side. While it may sound pretty intimidating and ambiguous at first, resolving a 500 error is often manageable with some common troubleshooting skills.

Here is a simple example of how a typical 500 error is displayed on the browsers.

HTTP error 500

5 Main Causes For 500 Internal Server Error

1. problems with database servers.

Most of the websites follow Web 2 models , meaning they rely on a database to store or retrieve the information. Error 500 in this case, can be a result of various issues with the database such as the database being slow or offline , or encountering errors while executing the queries. It can also be the result of invalid credentials, a misconfigured database server, or if the user has exceeded the total number of available requests.

2. Permission Errors

Permission error occurs when the program does not have permission to access certain resources , including read and/or write access to files or databases. When this kind of error occurs, the program is not able to perform the required action leading to a 500-server error. Making an effort to access the resources with correct permissions is a crucial part of managing the issue.

3. Large files on the websites

Large files such as videos or any other large, downloaded resources can often cause 500 errors, by overwhelming the server resources. This can occur when too many users try to access these large files simultaneously, leading to resource exhaustion. Using CDN ( Content Delivery Networks ) or optimizing file sizes can be a good way to mitigate the problem.

4. Issues with configuration

Incorrect configurations are the most common cause of the server encountering unexpected situations and thus throwing Error 500. These errors may include incorrect server configuration files , corrupted .Htaccess file or misconfigured virtual hosts. This type of issue can generally be solved by contacting the server administrator.

5. Temporary Connectivity problems

Another common cause of Error 500 is connectivity problems. Connectivity problems can lead to disruption in the communication between the client and the server. For example, if a server is relying on a database of external resources and due to some connective problems the resource is not available, it can lead to a 500 server error. An effort to pick good reliable servers or monitoring and ensuring the reliability of the server can help mitigate the problem.

Now that we have gone through some potential causes for HTTP 500 – internal server error , let’s now go through some ways on how as an end user one can fix the error.

Fix Error 500 – Internal Server Error as an End User

1. check configuration files.

If you have access to server configuration files (e.g., .htaccess for Apache ), review them for any potential issues. Syntax errors or misconfigurations in these files can lead to Error – 500. Additionally, Make sure the configuration settings align with the requirements of your website or application.

2. Turn off your 3rd party plugins

Plugins can add amazing features and functionality to your website. But, in case you’re experiencing a 500 error on a website, it might also be related to third-party plugins or extensions . In these cases, consider temporarily disabling them one by one. This can help identify if a specific plugin is causing the issue. If disabling a particular plugin resolves the error, you may need to investigate that plugin further or seek an alternative.

3. Clear browser cache and cookies

Cookies and Browser cache help websites remember information about your visit, which can make it easier to visit the site again. But in some cases, they can sometimes store outdated or corrupt data that may cause conflicts with the web server. Clearing your browser’s cache and cookies and refreshing the page again can often resolve these conflicts.

4. Try accessing the page later

Sometimes a minor glitch can be the cause of the Error 500. The error can also be the result of a temporary high server load or server maintenance. In such cases being patient and accessing the page later is the key to solving the problem.

5. Contact your server administrator

In cases where none of the above solutions work, it is highly likely that the issue is on the server side. In these cases, reaching out to the server administrator can be the best possible way to solve the problem or if necessary, get some additional guidance. In such cases, it is often required to provide the exact details of how the problem occurred and error messages if any. you can also ask the administrator/ provider to access the log files and find the exact root cause of the problem.

Error 500 can be a very frustrating barrier while navigating a website. This is a problem on the server side and can be caused due to various reasons including database issues , invalid file permissions , or even a temporary glitch . As an end user, you can also take several steps to understand and solve the problems.

In this article, we explored what Error 500 is and what it signifies. We also went through some most common causes of the error and ways through which we can solve the error.

500 Internal Server Error – FAQs

1. should i report error 500 to the server administrator.

It is absolutely safe and advisable to report any error to the server administrator. Once the issue is brought to their notice, they can promptly help resolve the error improving the experience for the users.

2. What is an Htaccess file?

The Htaccess(Hypertext access) file is a configuration file, used primarily by the Apache web server. This file can be used to make the server configurations for a specific directory. more information about the file can be found here .

3. How long should I wait before refreshing the page if I encounter an HTTP 500 error?

It is generally advisable to wait for an hour before attempting to refresh the page. Website owners are generally aware of such issues, and given a little time they’ll resolve the issue on the server side.

Please Login to comment...

Please write us at contrib[email protected] to report any issue with the above content

Improve your Coding Skills with Practice

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

HTTP Error 500.0 - Internal Server Error error when you open an IIS Webpage

• 3 contributors

This article helps you resolve the HTTP 500.0 error that occurs when you visit a Web site that is hosted on IIS.

Original product version:   Internet Information Services Original KB number:   942031

This article describes HResult codes when you encounter 500.0 error on an Internet Information Services (IIS) Web application. This article is intended for Web site administrators. These errors have many causes and can affect many different system configurations. The procedures that are described in this article must be performed by a member of the administrator group on the server.

End users that experience these errors should notify the Web site administrator of the problem.

HResult code

HTTP Error 500 message indicates that a problem has occurred on the Web server that hosts the Web site at the time the error is returned.

The following is the details of these errors.

HResult code 0x80070032

Error message:

Server Error in Application " application name " HTTP Error 500.0 - Internal Server Error HRESULT: 0x80070032 Description of HRESULT ISAPI filter drive:\FilePath\ISAPI_FLT.dll tried to register for SF_NOTIFY_READ_RAW_DATA notification.

This problem occurs because IIS 7.0 does not support the Internet Server API (ISAPI) filter that registers for the SF_NOTIFY_READ_RAW_DATA notification.

Do not use the ISAPI filter that registers for the SF_NOTIFY_READ_RAW_DATA notification in IIS.

HResult code 0x80070035

Server Error in Application " application name " HTTP Error 500.0 - Internal Server Error HRESULT: 0x80070035 Description of HRESULT The page cannot be displayed because an internal server error has occurred.

This problem occurs because the server that is running IIS 7.0 cannot access the configured root directory of the requested location.

Make sure that the server that is running IIS 7.0 can access the configured root directory of the requested location.

HResult code 0x8007000d

Server Error in Application " application name " HTTP Error 500.0 - Internal Server Error HRESULT: 0x8007000d Description of HRESULT Handler "ASPClassic" has a bad module "IsapiModule" in its module list.

This problem occurs because the ISAPIModule module is missing from the modules list for the Web site. The ISAPIModule module is in this location: drive:\Windows\System32\inetsrv\isapi.dll .

Add the ISAPIModule module to the modules list for the Web site. To do this, follow these steps:

• Click Start , click Run , type inetmgr.exe , and then click OK .
• In IIS Manager, expand <server name> , expand Web sites , and then click the Web site that you want to modify.
• In Features view, double-click Module .
• In the Actions pane, click Add Native Module .
• In the Add Native Module dialog box, click to select the IsapiModule check box, and then click OK .

HResult code 0x800700c1

Server Error in Application " application name " HTTP Error 500.0 - Internal Server Error HRESULT: 0x800700c1 Description of HRESULT The page cannot be displayed because an internal server error has occurred.

This problem occurs because a script mapping is not valid.

Make sure that the script-mapping points to the ISAPI.dll file that can process the request. To do this, follow these steps:

• In Features view, double-click Handler Mappings .
• Make sure that the script-mapping points to the correct ISAPI.dll file. For example, .asp files should map to the %windir%\system32\inetsrv\asp.dll file.

HResult code 0x80070005

Server Error in Application " application name " HTTP Error 500.0 - Internal Server Error HRESULT: 0x80070005 Description of HRESULT LoadLibraryEx on ISAPI filter "path_of_isapi" failed.

This problem occurs because an ISAPI filter that is not valid is loaded at the global level or at the Web site level.

Remove the ISAPI filter that is not valid. To do this, follow these steps:

• In Features view, double-click ISAPI Filters .
• Right-click the ISAPI filter that you want to remove, and then click Remove .

HResult code 0x8007007f

There are two possibilities for HResult 0x8007007f:

Error message 1:

Server Error in Application " application name " HTTP Error 500.0 - Internal Server Error HRESULT: 0x8007007f Description of HRESULT Calling GetProcAddress on ISAPI filter "path_of_isapi" failed.

To resolve the problem, remove the ISAPI filter that is not valid. To do this, follow these steps:

Error message 2:

Server Error in Application " application name " HTTP Error 500.0 - Internal Server Error HRESULT: 0x8007007f Description of HRESULT There is a problem with the resource you are looking for, so it cannot be displayed.

This problem occurs because the handler mapping for the requested resource points to a .dll file that cannot process the request.

To resolve the problem, edit the handler mapping for the requested resource to point to the .dll file that can process the request. To do this, follow these steps:

• Right-click the script mapping that you want to edit, and then click Edit .
• In the Edit Script Map dialog box, type the appropriate executable file in the Executable box, and then click OK . For example, .asp files should map to the %windir%\system32\inetsrv\asp.dll file.

More information

For any exception thrown from the web application code, check Application event log or your own Application log, for Exception Type, Exception Message, and Exception Call Stack. If further debugging is needed, use DebugDiag latest version to capture first chance exception dumps .

Was this page helpful?

Submit and view feedback for

Additional resources

How to fix HTTP 500 Internal Server Error in WordPress?

At some point in time, you must have encountered a 500 Internal Server Error while trying to access a particular website. As a visitor, you may ignore it, but as a website administrator, you cannot afford to ignore it and get rid of it as soon as possible.

Not only the website front end but also the WordPress administrator dashboard might not be available to access. In this article, we will walk you through some of the reasons why this error occurs, how to avoid it, and why it is important to invest in a reliable Dedicated server WordPress hosting to avoid this error and improve website uptime.

The frequent occurrence of 500 internal server errors is bad for the reputation of your business and will lead to visitors losing trust in your brand. Besides the reputation, it will also hurt your search engine rankings. Hence it is advised to avoid this error, and deeply understand what it is all about and how to troubleshoot.

Sometimes it could be due to the problem in website configuration, while sometimes it has something to do with issues at the server, which might be beyond your control.

How do we fix the “500 internal server error”?

Check out the below-listed solutions for 500 internal server errors.

• Refresh or Reload the Webpage
• Purge Browser Cache and Cookies
• Replace the Corrupt .htaccess file
• Increase the PHP Memory Limit
• Investigate Faulty Plugin or theme Issues
• Check your Error Logs
• Corrupted Core Files
• Check File Permissions
• Unsupported PHP Version
• Check that DNS entries are Correct
• Repair Corrupt Database
• Inode Limitation Reached
• Check if there are large files on your website
• Restore the Website from Backup
• Contact your Web hosting provider

1. Refresh or Reload the Webpage

The 500 Internal server error can be temporarily flashed on your screen and it might be only visible to you. It can happen due to either your poor internet connection or the location from which you are trying to access the website, which could have temporary downtime issues.

Therefore, you do not need to panic, all you have to just wait for a while and try gain reload the page. Alternatively, you can try accessing the website form a different browser or from a different device.

Also, as we have earlier said the 500 internal server error can also occur due to issues with an entire network. It means, that whatever device you use to access the internet over the same network, will show you the same error message.

To check if this is causing the issue, switch to a different network. For example, if you are currently connected to WiFi, switch to mobile data instead.

2. Purge Browser Cache and Cookies

If you have tried to reload or refresh the webpage but all in vain and returned a 500 internal error message instead. It could be possible due to an expired or corrupted browser cache and cookies.

If this is causing the issue, the best thing you can do to fix this issue is simply to Purge your Browser’s cache and cookies completely. All you need to do is to follow the steps given below:

Please note that in this step, we will focus on Google Chrome, as it is the preferred browser for the majority of users when it comes to website browsing.

Read: 🚩 Browser Market Share & Usage Statistics

Go to your Chrome Browser > Settings > Privacy and Security > Clear browsing data > You can uncheck the Browsing History and let cookies and other site data, as well as cache images, be checked > Clear data .

Alternatively, you can directly enter this address into your Chrome browser: chrome://settings/privacy. It will take you to the privacy settings where you can click on “ Clear browsing data “.

In the pop-up window, you will see plenty of other options, but you have to choose as follows:

• Select the time range as “All time”.
• Select cookies and other site data as well as Cache images (you can also select browsing history)
• Click on the Clear Data button.

3. Replace the Corrupt .htaccess file

One of the most common causes of WordPress 500 error is a corrupted .htaccess file (found in the root directory) that might arise due to a plugin update, theme update, etc., or during the migration from one server to another. To fix this error you can replace the current .htaccess file with another one.

Sometimes you might not be able to see the .htaccess file, in such cases check the hidden files in the root directory as well. Also, make sure that the file is correctly named.

Read: 🚩 WordPress .htaccess File: How to Create And Edit it?

4. Increase the PHP Memory Limit 

This could happen due to some plugin or theme consuming a lot of processing memory, or if you are using too many plugins. If your WordPress website is consuming a lot of memory to process a request you might run out of memory limit.

You can increase the memory limit to troubleshoot this problem. This could be done by making some modifications to the wp-config file or php.ini file. 

Add this code to the wp-config file:

<?php define('WP_MEMORY_LIMIT','64M');

You can increase the memory limit by changing 64M to 128M, 256M, and so on.

Alternatively, you can increase the memory limit through php.ini. Edit your php.ini, find out the line of code that defines the memory limit which will look like this:

memory_limit = 32M ;

You can increase it to 64M, 128M, 256M, and so on.

Another related issue is with Maximum Execution Time. If a request made by the user agent takes more than the time limit set for the website process request. You can increase the max execution time limit either through the wp-config file, .htaccess file, or php.ini file.

To define the Max Execution Time using wp-config, add the following code or if the code already exists increase its value:

set_time_limit(300);

To increase the time limit using the .htaccess file, add or edit the following code:

php_value max_execution_time 300

You can edit php.ini as well to increase the execution time using this code:

max_execution_time = 300

5. Investigate Faulty Plugin or theme Issues

If you have recently installed or updated a plugin you might need to investigate if that is causing an issue. If you can access the admin dashboard, you can deactivate all the plugins at once, and then refresh the website to check if it works now.

If it works reactivate the plugins one after the other and check after activating each of the plugins. That way you will be able to identify which plugin is causing the issue. If after deactivating the plugins the website is still not working then the issue is not due to any of the plugins.

If you are not able to access the admin backend you can rename the directory of each of the plugins, and while doing so you can check the website after renaming each of these and see if the problem resolves. Also, it is recommended to keep all the plugins updated.

Try updating or switching the theme of your WordPress website and see if the internal server error is gone. Sometimes outdated or corrupt scripts and codes within the theme files can lead to an internal server error. If you have encountered this error after a theme update, report this to the theme developer, and restore it to a previous version.

That is why it is recommended to take regular backups of your website , especially before making themes, plugins, or core installation updates.  Some hosting providers also provide you with Error logs that might help you further identify the cause of the error.

6. Check your Error Logs

You can also check out your error logs and find out the possible causes that trigger 500 internal server errors. All you need to do is log in to the FTP client and then navigate to the Error log Directory and either download it or directly open it in an editor.

This will help you to narrow down the issue so that you easily figure out the exact problem and you can immediately fix it. You can also read our complete guide on How to access and set up WordPress error logs ?

Hosting providers like WPOven provide you with a console within your hosting console to update the plugins, themes, core files, and many other management tools for better performance and control over your website along with regular backup and restore options.

7. Corrupted Core Files

You can upload the updated files through an FTP server to troubleshoot the internal server error on your WordPress website. You can upload the updated files from WordPress.com and upload them to the server using FTP software like FileZilla etc.

8. Check File Permissions

To make the WordPress website work perfectly fine, it is essential to have all the directory and file permissions correctly configured. The recommended file permission settings are as follows:

• 755 for all folders and sub-folders.
• 644 for all files.

Incorrect permission settings will lead to the blocking of some plugins, themes, and scripts to work. 

At WPOven you can use the “Fix Permissions” tool for fixing file permissions in Sites->Tools in the dashboard. 

9. Unsupported PHP Version

There are outdated PHP versions that are not supported by the latest WordPress version anymore. One of the latest versions 7.0, 7.1, 7.2, 7.3, and 7.4 are highly recommended. You can refer to our article on PHP Versions as well for more details.

Also, you can find the latest PHP 8 version here.   WPOVen – Managed WordPress Hosting Comes with the latest PHP Updates.

10. Check that DNS entries are Correct

If your DNS is pointing to a server other than your hosting server, the visitors will not be able to access it. Make sure that the DNS entries are accurate.

Read: 🚩 How Do I Point my Domain or DNS to WPOven?

11. Repair Corrupt Database

Another highly common issue that triggers the ‘500 Internal Server Error is a corrupted database on your WordPress site. However, you can easily fix this by repairing or restoring the database from a backup.

For WordPress sites, the error can be triggered if the website is unable to connect to the database. To learn more, please check out our detailed post on ‘ How to Fix Error Establishing a Database Connection? ‘.

12. Inode Limitation Reached

Each hosting account has a certain limitation on the number of inodes it can support, meaning the total number of files and directories you can create.

As your site keeps on growing, it will use more inodes. That is why you need to be more mindful about your inode usage.

So one of the ways you can resolve this issue is by starting to delete all the unnecessary files on your server. Here is an in-depth tutorial that will walk you through the entire process of deleting your inodes .

Check out our article on WordPress Security here

13. Check if there are large files on your website

Large files on your website can also trigger 500 internal server errors. If a file’s size exceeds the server’s permitted limit for web opening, it can lead to errors on your website.

To figure this out, you can use different tools like FTP, SSH, or File Manager to identify files that exceed the permitted size. Usually, these big files are something called PHP error logs.

14. Restore the Website from Backup

If none of the above troubleshooting methods work, or if you find it difficult to implement them, the last option left for you is to restore your website from the backup you have already created. This will revert any changes you have made that may have triggered the error.

15. Contact your Web hosting provider

If none of them work you should immediately contact the tech support team of your web hosting provider to troubleshoot. There might be a problem with either the server hardware or the software. If there are frequent outage reports at the server end you should consider switching to another company.

Tips to avoid 500 Internal Server Error and Quick Troubleshoot

• First and foremost, keep all the plugins, themes, and WordPress Core updated. The outdated versions tend to create more problems and are more prone to security threats like malware and hacking.
• Always take regular backups of your WordPress website files and database. Use a good plugin that takes regular backup and can easily restore the website to the desired version.
• Turn on ‘ Debugging ’. It is a small trick that will help you easily debug the website, by giving you vital information about the cause of the issue. It can be enabled by adding the following line of code in your wp-config file: “define( “WP_DEBUG”, true );”
• Increase your PHP Memory Limit (as explained above).
• Use a highly reliable server.
• Use security plugins to scan and audit your website regularly.
• Use reliable and trusted plugins and themes only, that provide good support.

Some of the top web server hosting companies like WPOven have a system in place to keep a close watch on the hosted WordPress websites and send out a notification to the website administrator. There are some free web-based website monitoring tools like UptimeRobot, that also send notifications in case the website is not working for any reason.

What is a 500 Internal Server Error?

In one of our previous articles about HTTP Status codes , we have covered in detail the type of errors website users might encounter. The 3-digit error status code that starts with ‘5’ and looks like 5XX indicates that there is no problem with the request made by the user agent.

However, due to some other reasons, the server is not able to process the request due to incorrect configuration of the website or due to some issue encountered within the server.

While 500 specifically indicates that the webserver is facing some kind of Internal issue due to which the request made by the user agent could not be processed at that moment. Sometimes this kind of error is momentary, which lasts for a few minutes and sometimes just a few seconds.

But if the problem persists, chances are that there is a problem with the website. Also, it is found that often the issue arises due to incorrect configuration of the website, which you can fix at your end. 

But if this is very frequent you should discuss the problem with the web server tech support team to help you troubleshoot the issue. Some other popular 5XX error codes are 502 Bad Gateway error , 504 Gateway timeout error

For a more specific kind of issue, you need to look into the specific error code using tools like MS IIS. Some of the most commonly occurring codes are as shown below:

What are the reasons that cause 500 Internal Server Error in WordPress?

If there is a 500 internal server error on your WordPress website the users will not be able to access any of its pages, which indicates that there could be a problem at the root directory. Here are some of the most common issues due to which your WordPress website has an HTTP 500 Internal Server Error.

• corrupt .htaccess file
• Corrupt browser Cache
• Syntax error in .htaccess file
• Corrupt Database
• Temporary connectivity issues
• Wrong PHP version for the website
• Large files on your website
• Exceeding PHP Memory Limit
• Faulty Plugin or theme Issue
• Incorrect DNS entries
• Problem with the Server itself

Where can you see a 500 Internal Server Error?

• HTTP 500 Error on a WordPress Website:
• 500 Error on Linux:
• 500 internal server error in NGINX

HTTP 500 internal server Error on a WordPress Website:

If your website has encountered an internal server error, you will not be able to access the website. In extreme cases, you might not be able to access even the wp-admin backend.

Typically, your browser will show any of the following messages:

• “500 Internal Server Error”
• “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. That’s 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.”

500 internal server Error on Linux:

If your website visitors are getting the 500 HTML error status you can troubleshoot it using Linux as well, especially if the error arises due to any of the CGI or PERL scripts.

Also, the error can be due to the non-compatible versions of PHP and Apache. In such a case you need to upgrade PHP or recompile Apache. In Apache you can go through the error logs in the following locations:

/usr/local/apache/logs/error_log /usr/local/apache/logs/suphp_log

You can use Linux commands to fix the errors, for example, to change the file and folder permissions you have to use the following commands:

cd public_html find . -type d -exec chmod 755 {} \; find . -type f -exec chmod 644 {} \;

500 Server Error on some Popular Websites:  

Though there are fewer instances of 500 internal server errors on the world’s most visited website, even then they have encountered the error at some point in time. Some websites have very creatively designed error pages as well. Some of the examples are shown below:

• FitBit.com:

Some of the leading Content Delivery Network providers like Amazon’s AWS offer to create a custom page when there is a 500 internal server error.

How to Fix 500 Internal Server Error in NGINX?

When there is an issue that happens on the server side, due to which NGINX is unable to return a proper response, it starts showing a 500 internal server error. The issue can happen due to multiple reasons some of the most common are, limited file permissions and errors in the script.

However, you can easily fix this error by following these simple methods:

• Force refresh or restart your webpage.
• Check out your Error logs.
• Check out the Scripts.
• Check whether adequate permission is granted to folders and files.
• Check all your redirections.

How does 500 Internal Server Error Effects your Search Engine Ranking?

Non-availability of websites, or in other terms longer and frequent downtime of the website can negatively impact your search engine rankings. Google always strives to provide a good user experience to the visitors, and hence if many visitors encounter the problem at different points in time it will downgrade the ranking of the website for sure.

Hence it is important to take these errors seriously and keep monitoring the websites. Using Google Analytics as well as Search Console you can see how many visitors faced the error. Besides the user experience, Google crawler also crawls the website regularly, and while crawling it found that the website is not available consistently which will negatively affect the rankings.

The seriousness of the 500 Internal Server Error depends on how frequently the error occurs, and the cause of the error. If the error lies with the website files or configuration then you need to fix it or get professional help.

But if errors frequently occur due to some problem with the server’s hardware or software then you need to immediately migrate to a more reliable and trusted hosting company .

Overwhelmed with too many server issues!! Choose a more reliable server instead. Host your website on WPOven now and save your time, money, and resources. Give your website a mammoth growth with  WPOven’s   Fastest, and  Fully managed Dedicated Servers .

• Fastest Private Servers
• Fully WordPress optimized Servers
• Upto 100% server uptime
• Server stack
• Hardened Servers with high-end security
• 24X7 WordPress Expert support
• Datacentres around the world, etc .

You can have all these features and much more. Plans start at $66.63 per month with unlimited Free migrations, unlimited staging, and a  14-day risk-free guarantee .  Check out our plans  or   Contact our support team  which assist you in choosing the right plan.

General FAQ

What does 500 internal server error mean.

The Hypertext Transfer Protocol (HTTP) 500 Internal Server Error response code represents that the server is unable to fulfill a particular request that was made by a user at the front end of the website.

How do I fix internal server errors?

The best and quickest ways to fix internal server errors are

• Try reloading your web pages. Do it with F2 or Ctrl+F5
•  Clear the cache of your browsers.
• Delete all browser cookies.
• You can also contact the website admin to let them know

What causes internal server errors?

500 Internal Server errors are caused due to server errors where the server may not be able to fulfill any particular request at that time. It may also be due to some policy issues with your APIs.

I am a Co-Founder at WPOven INC currently living in Vancouver, Canada. My interests range from Web Development to Product development and Client projects. I am also interested in web development, WordPress, and entrepreneurship.

Related Posts:

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

We explain and teach technology, solve tech problems and help you make gadget buying decisions.

8 Ways to Fix Outlook Error 500 ‘Something Went Wrong’

Microsoft Outlook is a widely used email client, but like any software, it can encounter errors that disrupt communication. One such error is Outlook error 500. This article will explore eight effective ways to fix Outlook error 500, ‘Something went wrong’. Before we delve into the solutions, let’s understand why this error occurs.

There are several reasons why Outlook Error 500 occurs. In addition to problems with the mail server, there may be problems with internet connectivity, firewalls, and antivirus programs interfering with Outlook’s connection to the server, and outdated login credentials can cause authentication to fail. With this understanding, let’s proceed with the fixes.

1. Check Your Subscription

Before diving into the specific steps to resolve the Outlook error 500, verifying your subscription status is crucial. Microsoft Outlook typically requires a valid subscription to access its full range of features and services. By addressing subscription concerns upfront, you can save valuable time and avoid unnecessary troubleshooting steps, ensuring a more efficient resolution to the error.

Step 1 : Go to the Microsoft 365 admin center from your preferred browser on Windows or Mac, and log in with your credentials.

Go to Microsoft 365 admin center

Step 2 : From the home screen, navigate to Subscriptions.

If you do not have an active subscription to Microsoft’s apps and services, make the payment and resubscribe. Otherwise, move on to the following method to fix this problem.

2. Check Microsoft’s Service Health

One critical aspect to examine is Microsoft’s services health to determine if external factors are causing Outlook error 500 ‘Something went wrong. Repeating redirect detected.’ The Outlook and Exchange services depend on Microsoft’s servers and infrastructure. So, any disruptions can result in error 500. Follow the instructions below.

Step 1 : Go to the Microsoft 365 admin center and sign in with your credentials.

Step 2 : Once logged in, click on Show all from the side pane. 

Step 3 : Now, click on Health and choose Dashboard from the side pane. 

There will be app and service icons, and their health will be displayed next to them. If you see any incidents or advisories, all you can do is wait until Microsoft resolves it.

Check out the following fix if you don’t see any service health issues.

3. Check User Permissions

Sometimes, the ‘User Has No Mailbox and No License Assigned Error’ occurs due to an often-overlooked aspect that can be the root cause of this issue – user permissions. In Outlook, user permissions dictate what a user can or cannot do within the application, and misconfigured or insufficient permissions can lead to various errors, including error 500.

Ensuring users have the appropriate permissions is a crucial preliminary step to rule out access-related issues. Proper user permissions involve setting up roles and access rights, including sending and receiving emails, accessing specific folders, and managing calendar events.

4. Troubleshoot Your Internet Connection

Ensuring you have a stable and reliable internet connection is crucial. Outlook error 500 often occurs when Outlook struggles to communicate with the email server due to connectivity issues. Slow or intermittent internet connections can disrupt the synchronization process, leading to this error.

We have already covered articles on the same; check it out:

• How to fix Windows 10 network connection issues
• Ways to fix slow internet speed on Windows 11
• Best ways to fix Mac Wi-Fi connected but not working
• How to troubleshoot and reset Wi-Fi settings on Mac

If your internet connection is functioning well with other services, check out the next fix.

5. Clear Browser Cookie and Cache or Disable Extensions

Outlook operates seamlessly through web browsers for many users, making it an integral part of their daily workflow. However, errors like Outlook error 500 can sometimes stem from browser issues. Before moving on to more complex troubleshooting steps, it’s essential to rule out browser-related problems.

This method involves checking for  browser extensions or plugins  that might conflict with Outlook, clearing cache and cookies, or trying to access Outlook in different browsers. Addressing browser-related issues often provides a quick and effective solution to Outlook error 500, saving users time and frustration. You may want to read;

• How to clear cookies and cache in Chrome for one site
• How to clear cache and cookies in Firefox
• How to clear cache and cookies in Safari
• Best ways to clear cookies and cache in Microsoft Edge Chromium
• How to clear cache in Opera and Opera GX

The following method may fix the issue if this error is not fixed. 

6. Remove User Roles

The Global Administrator role grants you access to all settings, so you don’t need to assign multiple admin roles. If you aren’t the global admin, you must contact someone who can reassign your roles. 

Step 1 : Head to the Microsoft admin center, enter your credentials, and log into your account.

Step 2 : Click on Users from the side pane and choose Active Users from the drop-down menu.

Step 3 : Choose the name of the affected user account from the list of active users.

Step 4 : In the modal, click on Manage roles.

Step 5 : Now, uncheck all roles except Global Administrator and click the Save Changes button at the bottom. 

The changes will take effect after a few minutes. If you are already logged in from that account, sign out and try logging in again. If this method didn’t fix the issue, check out the following method. 

7. Enable Outlook On the Web

If you receive the protocol disabled message or Outlook error 500, enabling Outlook web access (OWA) might fix the issue. This error occurs when an administrator removes your permission to access Outlook web.

Note : The below steps can only be executed by an administrator. If you are not the administrator, reach out to the concerned person.

Step 1 : Go to the Exchange admin center from your preferred browser on a Windows or Mac computer and log in with your credentials.

Go to Exchange admin center

Step 2 : Click on Recipients on the left pane and choose Mailboxes from the drop-down menu.

Step 3 : Now, select the user account for which you want to enable Outlook web.

Step 4 : From the right pane, under ‘Email apps & mobile devices’, click on ‘Manage email apps settings.’

Step 4 : In the ‘Manage settings for email apps’ screen, toggle on ‘Outlook on the web.’ Finally, click the Save button.

That’s it. You should be able to access Outlook web on your computer error-free. If you cannot fix the issue, the following method will help.

8. Use Microsoft’s Diagnostics Tool

Microsoft provides a diagnostic and troubleshooting tool called the Microsoft Support and Recovery Assistant (SaRA). This tool helps users diagnose problems with Office apps, including Outlook. Follow the below steps.

Step 1 : First, download SaRA from Microsoft’s official site.

Download Microsoft Support and Recovery Assistant

Step 2 : Once downloaded, click Install and open the tool. 

Step 3 : Select the ‘Outlook on the web’ option and click Next.

Step 4 : In the ‘Select the problem you’re having’ screen, choose ‘I can’t run Outlook on the web’ and click Next.

From here on, follow the instructions and troubleshoot your connectivity issues. Once you finish the steps, restart or refresh your Outlook account by logging out and logging in. This would fix the error and get you going. 

FAQs on Fixing Outlook 500 Error

No, the Outlook 500 error can occur in various versions, including Outlook 2016, 2019, and Microsoft 365.

If the error continues, it’s advisable to contact your IT department or email service provider for further assistance. They can diagnose and resolve server-related issues causing the error.

Fix the Outlook Error

Now that we have explored the common causes of Outlook error 500 and provided eight effective ways to fix it, you can quickly fix Outlook error 500 to ensure uninterrupted communication and a smooth experience.

Last updated on 12 November, 2023

The above article may contain affiliate links which help support Guiding Tech. However, it does not affect our editorial integrity. The content remains unbiased and authentic.

DID YOU KNOW

Atish Rajasekharan

Atish is a seasoned tech enthusiast, blogger, and content creator with a degree in Computer Science engineering. He began blogging in 2015. With over 2000+ articles covering tech news, tech breakdowns, and comprehensive smartphone and PC reviews, his work has graced the pages of reputable sites such as Gizbot, Firstpost, PhoneArena, GSMArena, and IBTimes. Atish covers a wide range of topics at GT, including how-tos, invaluable tips, and troubleshooting guides. He carries certifications in digital marketing and content strategies, ensuring he remains on top of tech trends while maintaining the highest ethical standards.

More in Internet and Social

How to Change Gmail Password If You Forgot It: A Complete Guide

Can an App from Disney Replace iMessage for Kids Everywhere

Join the newsletter.

Get Guiding Tech articles delivered to your inbox.

How to Fix Outlook Error 500 Mailbox not Found

This article explains how to resolve the Outlook error 500, which prevents users from accessing their mailboxes. If you are getting a mailbox not found error in Outlook on the web, we will show you the steps to resolve this error.

When you have a large organization with 1,000 or more users, mailbox access issues are common. Exchange administrators are responsible for making sure mailboxes are online and reachable by users. However, 500 error message may appear for Outlook users in some cases due to repeating redirects detected issue or licensing issues.

Recently, one of our clients contacted us to report that one of the Intune users had been denied access to the mailbox. The outlook webmail was not working and this account was newly created in Intune. When the user attempted to sign in to Outlook on the web, the following error occurred:

Error 500. Something went wrong. We couldn’t find a mailbox for this account. Either they don’t have a mailbox or they don’t have a license assigned. To fix it, contact your email admins and ask them to assign a valid licence for your user account using the M365 admin portal per instructions.

Note that when you encounter an Outlook web error, “ We couldn’t find a mailbox for this account “, email access is also restricted using the Outlook app installed as part of Microsoft 365 apps . In other words, you cannot access your emails via Outlook on the web via a browser or the Outlook app installed on your PC. The Outlook app on a Windows PC displays a mailbox disconnected error.

Fix Outlook Error 500 – We couldn’t find a mailbox for this account

While using Outlook on the web, you encounter the error 500 and ‘ We couldn’t find a mailbox for this account ‘. This happens because the account that you used to connect to Outlook on the web doesn’t have an Exchange Online license, and therefore, no mailbox is associated with the account. To resolve this error, you must assign an exchange online license to the user.

Solution 1: Assign Exchange Online license to your account

The Outlook error 500 can be resolved by assigning an Exchange Online license to the user account in Microsoft 365 admin center. Your admin can assign a license to your account by following these steps:

1. Sign in to the Microsoft 365 admin center . In the left navigation pane, in the Users section, select Active users , and then select the user who is seeing the error.

2 . On the user page that opens, go to the Licenses and Apps section, select the appropriate location value, and assign a license that contains Exchange Online (Plan 1 or Plan 2) . In the below screenshot, the account is assigned an Exchange Online license. When you’re finished, click Save Changes .

3 . After performing the above steps, request the user to sign out and then sign in back to the account. Now, the error 500 will no longer appear while accessing the mailbox via Outlook on the web.

Note : It takes at least 10-20 minutes to apply for the license after you have added the Exchange online license (Plan 1 or Plan 2) to the user account. To prevent Outlook error 500 from appearing in the browser session, you may need to request that the user clear the browser cache in some cases. Cookies stored in the browser must also be cleared as they contain user session information.

Solution 2: Monitor Exchange Online Service Health Status

If multiple users in your organization are receiving Outlook error 500, you should check the service health of the Exchange online server in the Microsoft 365 admin center.

In our previous article, we showed you how to check the Windows release health page in the Microsoft 365 admin center , which enables you to view the latest information on known issues for Windows monthly and feature updates.

If there are any issues with the Exchange online service, users will be unable to access their mailboxes or send and receive emails via the Outlook web and Outlook app. Sign in to the Microsoft 365 admin center to check the status of the exchange online service. In the left navigation, select Health > Service Health . Under Service Status , you find the health status of Exchange Online.

If the Exchange Online service is down or experiencing issues, that would be shown under Service Status . Click on the Advisories link to find out the current issues with the service.

Troubleshoot Error 500 Outlook Mailbox not found

In the below screenshot, we see the error 500: Something went wrong when the mailbox was accessed via the Outlook web app. If you click on the ‘ More Details ‘ link, it shows additional troubleshooting information such as:

• ClientIPAddress
• X-OWA-Error Microsoft.Exchange.Data.Storage.InvalidLicenseException

The information provided above will assist exchange administrators in resolving the Outlook error 500 mailbox not found error. In the screenshot below, the X-OWA-Error clearly shows that it’s a Microsoft Exchange InvalidLicenseException error. In your case, the error description could be different.

Resolve Repeating Redirects Detected for Outlook Web

What’s interesting is that the error 500 is related to “ Repeating redirects detected ” while accessing the mailbox using Outlook on the web. In the screenshot below, we see the user is unable to access the mailbox using Outlook on the web. The browser reports the error 500, something went wrong along with the error “ Repeating redirects detected .”

The Outlook web error repeating redirects detected error occurs for two reasons:

• When a Microsoft 365 user account has recently been unblocked.
• When too many roles are assigned to the user account.

Let us go over the solutions for resolving the detected repeating redirect issue in the Outlook web app.

Too many admin roles assigned to account

If a user account is assigned too many roles in the Microsoft 365 admin center, the user may experience the repeating redirects detected error in the Outlook web app. Microsoft 365 administrators can resolve this issue by removing unnecessary roles from an account and assigning only those that are required. An unwanted role here indicates that the user doesn’t need that role but has been assigned due to some reason.

To remove the unnecessary admin roles for users in Microsoft 365, follow these steps:

• Sign in to the Microsoft 365 admin center.
• In the left navigation pane, in the Users section, select Active users , and then select the user who is seeing the error.
• Under Roles , select Manage Roles .

On the Manage admin roles page, go through the list of roles that are assigned to the selected user. Uncheck any unnecessary roles assigned to the user, and then click Save Changes .

Microsoft 365 User Account Unblocked from sign-in

If the Microsoft 365 user account is recently unblocked from sign-in, the user may encounter the repeating redirect errors while accessing the mailbox Outlook web.

Let’s say that an administrator has prevented a user account from logging in to the Microsoft 365 services due to security concerns. When you block someone, it immediately stops any new sign-ins for that account, and if they’re signed in, they’ll be automatically signed out of all Microsoft services within 60 minutes .

If the user account is now enabled for sign-in, the user will have access to Microsoft Services in 30-60 minutes. Meanwhile, if the user attempts to access the mailbox via Outlook web during this time, the user will encounter the repeating redirects detected error. So, the solution here is to advise the user to wait 30-60 minutes after the account has been enabled for sign-in.

We hope the steps outlined in this article assist you in resolving the Outlook error 500. As previously stated, error 500 is a generic error that occurs when users access their mailbox through the Outlook web app, and it can be resolved by assigning an exchange online license to the account. We also covered the solution to Outlook error 500: repeating redirects detected. The solution to this problem is to wait 30-60 minutes after the user account has been unblocked. For more such articles, consider booking this website.

Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

subscribe to newsletter

Get Access to latest articles on configmgr, intune, windows 365, Azure and much more.

What is 500 Error

Definition:

Error 500 means that something has gone wrong on the website. It is not a problem with the user’s browser, computer or Internet connection, but it is a problem with the site you are trying to visit.

Keep in mind that this error can appear in different forms, although they always mean the same thing. Depending on the website, “500 Internal Server Error”, “500 Error”, “ HTTP Error 500″, etc. may appear.

Table of Contents

• 1 What is Error 500 for?
• 2 How to Fix Error 500

What is Error 500 for?

Error 500 is a generic message that appears when something unexpected happens on the web server and the web server cannot offer more specific information about it.

How to Fix Error 500

The truth is that Error 500 being a web server problem, is not something that the user can solve by himself. Sometimes, it is fixed quickly, in a few seconds or minutes.

Normally, it is useful to reload the page, then the error should disappear. It is important to keep in mind that it is not advisable to recharge the website when you are sending an online payment or some type of transaction, as you can send the same payment twice.

Related Terms

• Crawl Error
• Response code 200 Ok

Digital Marketing, Analytics and Marketplaces Agency

• Digital Marketing
• Web Positioning
• Marketplaces

MADRID OFFICES

• Ferrocarril, 18. 28045 Madrid
• +34 91 060 64 28
• [email protected]
• Marketing Digital
• Arimetrics © 2022
• Legal Notice

¿Quieres suscribirte a nuestra Newsletter?

¡Mantente al día con noticias del sector!

Privacy Overview