This error indicates that the number of incoming concurrent requests exceeded the number that your IIS application can process. This could be. The HTTP error, in particular, indicates that the server encountered an unexpected condition that prevented it from fulfilling the request. In other words. The Internal Server Error is a very general HTTP status code that means something has gone wrong on the website's server, but the server.
Thematic videoFixed 500 Internal Server Error - HTTP
Congratulate: 500 internal server error 1c iss
|500 internal server error 1c iss|
|STEAM APPLICATION LOAD ERROR 65432|
|500 internal server error 1c iss|
500 internal server error 1c iss - thought differently
Are your website visitors only seeing the 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 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:
- Read (r)
- Write (w)
- Execute (x)
These permissions can be assigned for three different user types:
- Owner of the file
- Group of users
- All others
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 . This configuration () should be the default setting. If the permission assignment is set differently, an error may occur. You can change this with a command:
A Guide to HTTP Server Error Codes
HTTP status codes are the conversation between your web browser and the website’s server. In most cases, you as the user will not see the code generated unless there is an issue.
Error messages, or HTTP status codes, are displayed when an internet browser can’t reach a page that was requested by a user. These codes are categorised into five groups, numbered from 1XX to 5XX, each indicating a different problem or error.
What is a 5XX Error?
Error codes that fall into the 5XX range specify problems with the server.
When you visit a website, your browser issues a request to that website’s server. If there is an issue with the site’s server, a 5XX error code is often returned.
These errors occur when the server realises it has come across a problem or is unable to carry out a request. Clarification should be provided, explaining why the error has occurred and whether it is a permanent or temporary issue.
5XX error messages indicate server-side errors where your website’s server has been unsuccessful in performing a request, for whatever reason. Generally, this suggests that the problem does not lie with your website, internet connection or computer, and more often than not it can be safe to assume server maintenance is being carried out to solve the issue.
A Guide to HTTP 5XX Server Errors
There are a number of different 5XX server errors, numbered with their own response codes so that the problem can be identified. It is important to familiarise yourself with the varying 5XX status codes and their meanings. Some of the most common of these are listed below.
- Internal Server Error
Perhaps the most common message encountered, this indicates a generic server error that’s displayed when the server cannot determine the exact problem.
- Not Implemented
The server cannot distinguish the request made, or is unable to perform the request for whatever reason. This typically suggests future accessibility.
- Bad Gateway
This occurs when the server is operating as a gateway or proxy server and the upstream server returns an invalid response.
- Service Unavailable
This signifies that the server is unavailable at the present moment, usually due to maintenance or overloading. It is generally a temporary issue and the user should try again later.
- Gateway Timeout
Like the status, the server was functioning as a gateway or proxy server. This error occurs when the upstream server fails to respond in a timely manner.
What do 5XX Errors Look Like?
A 5XX Error is an error generated by the server, not the website. They are visible in any operating system so you may see this type of error message when using a desktop computer, tablet or smartphone. Server errors are often displayed inside the internet browser window just as web pages appear.
3 Simple Steps to Clearing a 5XX Error
5XX Errors are server-side meaning the problem is not likely to lie within your internet connection or device. There will be an error with your website server.
In the unlikely event that there is an issue with something your end, there are a few simple steps you can take before seeking further help and advice.
1. Refresh your browser
The problem may only be temporary, reloading the page will often prove successful. You can do this by resubmitting the URL from the address bar, pressing F5 or Ctrl-R on your keyboard.
2. Remove cookies
Sometimes 5xx errors are due to the cookies related to the website, so deleting these and refreshing the browser can often solve the problem. To do this, enter your web browsers History and select Delete. To remove the cookies from some devices you may need to check the box next to Cookies before hitting delete. Refresh your page and check to see if the error code represents itself.
3. Contact your host/server
If the problem continues, the best step is to contact your host or server directly to find out what the problem is. Chances are they are already on top of it or undergoing maintenance, but this will help put your mind at ease and give an idea of when it may be up and running again.
It is important not to ignore 5XX error messages when they appear. Not only do they have an adverse effect on the user’s experience but they aren’t bot-friendly either. Search engine robots like well-maintained websites so it’s important to investigate and fix site errors as you discover them.
For more information on our business hosting and IT support services, please contact a member of our technical team and discover how Blue Frontier can support you.
Troubleshooting an HTTP 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 internal server error, let's go over what it exactly means and its most common causes and solutions.
What is an HTTP internal server error?
An HTTP internal server error means your web server is experiencing problems, but it can't pinpoint the specific error or its root causes. When this happens, your website will serve up a general internal server error web page to your site's visitors.
Here's what your error page might look like in your browser:
How to Fix a Internal Server Error
Unlike other server-side errors like a code or a code, a 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 a few potential causes of the error. Then, we'll present some solutions so you can try to fix the issue.
Potential Causes of a Internal Server Error
A 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 internal server error include:
- Corrupted or broken .htaccess file
- A permissions error
- Faulty third-party plugins or themes
- The PHP memory limit being exceeded
Fortunately, there are a few effective solutions for fixing most of these problems.
If You're Trying to Load a Page with a 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 sprers.eu 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 it's a problem with your server, this should help assuage any concerns that it's an issue with your own computer.
If the 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.
You might find that having fewer active plugins on your site helps things run more smoothly.Alternatively, if you just upgraded your software, your current plugins or themes might not be compatible with the new upgrade. Deactivating plugins or themes one at a time until the error disappears is the best way to find the root cause of your problem.
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 sprers.eu directives to configure your PHP setup.Additionally, wrong permissions on a file or folder that has a script, like a PHP or CGI script, won't allow the script to run. Check your permissions and make sure you set them correctly on your server.
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 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 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 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 internal server error, you should read about the most common causes for this type of issue in your server's documentation — an HTTP 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 for 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 and has been updated for comprehensiveness.
Internal Server Error
For every request from a web browser the server responds with a status code . Out of various status code, 5xx are the codes related to Web Server. A first digit of 5 represents a server side error, with the most common codes in the range of to They indicate that the server failed to complete the request because server encountered an error. When you try to visit a website and see error " Internal Server Error" message, it means something has gone wrong with the website. This is a "catch all" status for unexpected errors. The error is particularly frustrating because it gives you no information about what specifically caused the server error. 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.
Error Status : Internal Server Error
The first thing you need to know about an "Internal Server Error" is that the error can only be resolved by fixes to the Web server software. It is not a client-side problem meaning that the problem is not with your browser, your computer, or your internet connection. There are a number of causes for a Internal Server Error to display in a web browser. The Internal Server Error message might be seen in any number of ways because each website is allowed to customize the message. Here are some common ways you might see this error:
- Internal Server Error
- HTTP - Internal Server Error
- Internal Server Error
- HTTP Internal Error
- HTTP Error
What causes a Internal Server error
This error means there is a problem on the server side. A server error can be caused by any number of things from uploading the incorrect file to as bug in a piece of code. This error response is a generic "catch-all" response. The web server is telling you that something went wrong, but it's not sure exactly what that is. If you have root access, you should review your web server’s error logs to get more information about this. If you are using shared hosting plan, you should contact your host to get more information. The best way to debug the error depends upon the server and what's actually running at the time. Consider some debugging tips to help diagnose and fix common causes of this problem.
How to Fix the Internal Server Error
When you hit an internal server error it usually means some parts of your web server is not configured correctly or the application is trying to do something and the server is failing to carry out the request due to a conflict or restriction. This error can only be resolved by fixes to the Web server software . It is up to the administrators of the Web server site to locate and analyse the logs which should give further information about the error. However, there are often ways to quickly get around the problem:
Backing Up Your Site
These solutions require making a lot of changes in your site's root directory . It's highly recommended that you backup your site prior to trying any of these solutions in case something goes wrong.
Very commonly, incorrect permissions on a file or folder that contains one of the scripts causes this this error. The script isn't throwing the error because the server can't even run the script. Check to see what the permissions should be and ensure that's how they are set on the server.
Sometimes the Internal Server error is because the server timed out, or a script you're running timed out . You can increase the Apache server timeout in sprers.eu by changing TimeOut If the server was busy, needed to be rebooted, or the connection was lost, the script might still report a Internal Server Error.
Sometimes the Internal Server error is because the script you're running timed out . If your website relies on scripts (such as Perl or CGI files), there are a number of things that can go wrong. A PHP or other server-side script may have timed out. This could be because of a programming error that put the script in an endless loop or a resource that wasn't available. If you're running a script, like PHP for example, you can increase the time out of this as well. For PHP this would mean changing the max_execution_time from the default of 30 (seconds) to something longer:
If a script times out during testing, it's likely to do it again during production when it’s accessed by more users.
Errors in .htaccess files
Occasionally, an error in the coding of an .htaccess file may cause this error. The .htaccess on your site might interfere with the web page that you are tying to load. Please double check the .htaccess configuration for any possible syntax error that could render a Internal Server Error. To confirm whether a misconfiguration .htaccess is the cause of the Internal Server error , either remove or rename the .htaccess file temporarily and then try to reload the page.
Check the Error Logs
You should check Apache and PHP error logs for your server. It will provide valuable information regarding any code failures or reasons for a site failure.
If you are a web visitor and want to rule out whether the problem is on your end:
Clear your browser cookies and cache
This is the one of the first things and tech support will advise, and while the server errors are not caused by either cookies or the cache , it might be that the error has been fixed and you are viewing the wrong version of the site because of them. It's worth doing as it only takes a few minutes in your browser's settings.
Reload or Refresh the Webpage
Most of the time, the issue is only temporarily and can be corrected by trying the page again. You can use the refresh/reload button, pressing F5 , or by trying the URL again from the address bar. Sometimes this error is caused when a service restarts, and you happen to catch it at exactly the wrong time.
If you've tried to troubleshoot your server error and still can't fix it, then you may need to speak to your web host and see if they are able to find what process or script is causing the error. If you are using a commercial web hosting company their customer support should be able to provide information on how to fix the error and in many cases they will apply the fix for you at no cost .
NEXTOTF vs TTF Fonts: Which One Is Better
Your key to European statistics
The rules applied for errors handling are the same for SDMX and SDMX
SDMX defines three classes of errors:
- Client caused errors ()
This kind of error message is returned when the client makes a mistake in the query, for example makes a syntax error.
- Server caused errors ()
This kind of error message is returned when the server causes an error, for example unavailability of the server
- Custom messages (+)
This kind of error is specific to each web service. DSWSv2 has only one error message of this kind which is the = "Application error". It is returned when application encounters and unexpected problem.
SDMX standard provides a table of error mapping:
|SDMX error||HTTP error usage in REST||SOAP usage|
|No results found||Not found||SOAP Fault|
|Response too large due to client request||Request entity too large||SOAP Fault|
|Syntax error||Bad syntax||SOAP Fault|
|Semantic error||Bad syntax||SOAP Fault|
|Internal Server error||Internal server error||SOAP Fault|
|Not implemented||Not implemented||SOAP Fault|
|Service unavailable||Service unavailable||SOAP Fault|
|Response size exceeds service limit||Request entity too large||Payload|
|+||Internal server error||SOAP Fault|
How to Fix a Internal Server Error on Your WordPress Site
The dreaded 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 WordPress 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 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.
Internal Server Error (Most Common Causes):
Internal server error in WordPress can be caused by many things. If you’re experiencing one, there’s a high chance one (or more) of the following elements is causing the issue:
- Browser Cache.
- Incorrect database login credentials.
- Corrupted database.
- Corrupted files in your WordPress installation.
- Issues with your database server.
- Corrupted WordPress core files.
- Corrupted .htaccess file and PHP memory limit.
- Issues with third-party plugins and themes.
- PHP timing out or fatal PHP errors with third-party plugins.
- Wrong file and folder permissions.
- Exhausted PHP memory limit on your server
- Corrupted or broken .htaccess file.
- Errors in CGI and Perl script.
Check Out Our Ultimate Guide to Fixing the Internal Server Error
What is a Internal Server Error?
The Internet Engineering Task Force (IETF) defines the Internal Server Error as:
The (Internal Server Error) status code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
When you visit a website your browser sends a request over to the server where the site is hosted. The server takes this request, processes it, and sends back the requested resources (PHP, HTML, CSS, etc.) along with an HTTP header. The HTTP also includes what they call an HTTP status code. A status code is a way to notify you about the status of the request. It could be a status code which means “Everything is OK” or a status code which means something has gone wrong.
There are a lot of different types of status error codes (, , , , , etc.) and they all mean something different. In this case, a internal server error indicates that the server encountered an unexpected condition that prevented it from fulfilling the request (RFC , section ).
Internal Server Error Variations
Due to the various web servers, operating systems, and browsers, a 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:
- “ Internal Server Error”
- “HTTP ”
- “Internal Server Error”
- “HTTP – Internal Server Error”
- “ Error”
- “HTTP Error ”
- “ – Internal Server Error”
- “ Internal Server Error. Sorry something went wrong.”
- “ That’s an error. There was an error. Please try again later. That’s all we know.”
- “The website cannot display the page – HTTP ”
- “Is currently unable to handle this request. HTTP ERROR ”
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, [emailprotected] 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 internal server errors, this is actually quite common in browsers like Firefox and Safari.
Bigger brands might even have their own custom internal server error messages, such as this one from Airbnb.
Here is another creative server error example from the folks over at readme.
Even the mighty YouTube isn’t safe from internal server errors.
If it’s an IIS (Windows) or higher server, they have additional HTTP status codes to more closely indicate the cause of the error:
- – Module or ISAPI error occurred.
- – Application is shutting down on the web server.
- – Application is busy restarting on the web server.
- – Web server is too busy.
- – Direct requests for sprers.eu are not allowed.
- – Configuration data is invalid.
- – Module not recognized.
- – An sprers.eu httpModules configuration does not apply in Managed Pipeline mode.
- – An sprers.eu httpHandlers configuration does not apply in Managed Pipeline mode.
- – An sprers.eu impersonation configuration does not apply in Managed Pipeline mode.
- – A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
- – A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
- – A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
- – 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.
– Internal ASP error.
Errors Impact on SEO
Unlike errors, which are used for WordPress maintenance mode and tell Google to check back at a later time, a 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 error as a site level issue that needs to be addressed. This could impact your rankings. If you’re worried about repeat errors you should figure out why they are happening to begin with. Some of the solutions below can help.
How to Fix the Internal Server Error
Where should you start troubleshooting when you see a internal server error on your WordPress site? Sometimes you might not even know where to begin. Typically errors are on the server itself, but from our experience, these errors originate from two things, the first is user error (client-side issue), and the second is that there is a problem with the server. So we’ll dive into a little of both.
Check out these common causes and ways to fix the 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 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 sprers.eu 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 “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 WordPress site. Typically this is on hosts that aren’t set up properly. What happens is they experience a temporary timeout right afterward. However, things usually resolve themselves in a couple of seconds and therefore refreshing is all you need to do.
2. Clear Your Browser Cache
Clearing your browser cache is always another good troubleshooting step before diving into deeper debugging on your site. Below are instructions on how to clear cache in the various browsers:
3. Check Your Server Logs
You should also take advantage of your error logs. If you’re a Kinsta client, you can easily see errors in the log viewer in the MyKinsta dashboard. This can help you quickly narrow down the issue, especially if it’s resulting from a plugin on your site.
Want to know how we increased our traffic over %?
Join 20,+ others who get our weekly newsletter with insider WordPress tips!
If your host doesn’t have a logging tool, you can also enable WordPress debugging mode by adding the following code to your sprers.eu 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/sprers.eu
- Nginx: /var/log/nginx/sprers.eu
If you’re a Kinsta client you can also take advantage of our analytics tool to get a breakdown of the total number of 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 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 sprers.eu file with the following:
4. Error Establishing a Database Connection
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 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 WordPress site uses separate login information to connect to its MySQL database.
- Your WordPress database is corrupted. With so many moving parts with themes, plugins, and users constantly deleting and installing them, sometimes databases get corrupted. This can be 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 in WordPress.
5. Check Your Plugins and Themes
Third-party plugins and themes can easily cause 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 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 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:
7. Permissions Error
A permissions error with a file or folder on your server can also cause a 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 (-rw-r–r–) or
- All directories should be (drwxr-xr-x) or
- No directories should ever be given , even upload directories.
- Hardening: sprers.eu could also be set to or to prevent other users on the server from reading it.
See the WordPress Codex article on changing file permissions for a more in-depth explanation.
You can easily see your file permissions with an FTP client (as seen below). You could also reach out to your WordPress host support team and ask them to quickly GREP file permissions on your folders and files to ensure they’re setup properly.
8. PHP Memory Limit
A 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 sprers.eu file, and file.
Increase PHP Memory Limit in cPanel
If you’re running on a host that uses cPanel, you can easily change this from the UI. Under Software click on “Select PHP Version.”
Click on “Switch to PHP Options.”
You can then click on the attribute and change its value. Then click on “Save.”
Increase PHP Memory Limit in Apache
The file is a special hidden file that contains various settings you can use to modify the server behavior, right down to a directory specific level. First login to your site via FTP or SSH, take a look at your root directory and see if there is a file there.
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 sprers.eu File
If the above doesn’t work for you might try editing your file. Log in to your site via FTP or SSH, go to your site’s root directory and open or create a file.
If the file was already there, search for the three settings and modify them if necessary. If you just created the file, or the settings are nowhere to be found you can paste the code below. You can modify of course the values to meet your needs.
Some shared hosts might also require that you add the suPHP directive in your file for the above file settings to work. To do this, edit your file, 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 files. To edit your file, login to your site via FTP or SSH, go to your site’s root directory and open or create a file. You can then paste in the following code:
Increase PHP Memory Limit in sprers.eu
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 sprers.eu file, which is typically in the root of your site.
Add the following code to the top of your file:
You can also ask your host if you’re running into memory limit issues. We utilize the Kinsta APM tool and other troubleshooting methods here at Kinsta to help clients narrow down what plugin, query, or script might be exhausting the limit. You can also use your own custom New Relic key from your own license.
9. Problem With Your .htaccess File
Kinsta only uses Nginx, but if you’re using a WordPress host that is running Apache, it could very well be that your file has a problem or has become corrupted. Follow the steps below to recreate a new one from scratch.
First, log in to your site via FTP or SSH, and rename your file to .
Normally to recreate this file you can simply re-save your permalinks in WordPress. However, if you’re in the middle of a internal server error you most likely can’t access your WordPress admin, so this isn’t an option. Therefore you can create a new file and input the following contents. Then upload it to your server.
See the WordPress Codex for more examples, such as a default file for multisite.
Coding or Syntax Errors in Your CGI/Perl Script
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 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.
Server Issue (Check With Your Host)
Finally, because internal server errors can also occur from PHP timing out or fatal PHP errors with third-party plugins, you can always check with your WordPress host. Sometimes these errors can be difficult to troubleshoot without an expert. Here are just a few common examples of some errors that trigger HTTP status codes on the server that might have you scratching your head.
We monitor all client’s sites here at Kinsta and are automatically notified when these types of errors occur. This allows us to be pro-active and start fixing the issue right away. We also utilize LXD managed hosts and orchestrated LXC software containers for each site. This means that every WordPress site is housed in its own isolated container, which has all of the software resources required to run it (Linux, Nginx, PHP, MySQL). The resources are % 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 errors, not 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 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 sprers.eu to monitor and notify you immediately if they occur. It periodically sends an HTTP HEAD request to the URL of your choice. You can simply use your homepage. The tool allows you to set check frequencies of:
- 15 seconds
- 30 seconds
- 1 minute
- 2 minutes
- 5 minutes
- 10 minutes
It will send you an email if and when your site goes down. Here is an example below.
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 a managed WordPress host. Make sure to check out our post that explores the top 9 reasons to choose managed WordPress hosting.
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 internal server errors. If so, let us know below in the comments.
Save time, costs and maximize site performance with:
- Instant help from WordPress hosting experts, 24/7.
- Cloudflare Enterprise integration.
- Global audience reach with 34 data centers worldwide.
- Optimization with our built-in Application Performance Monitoring.
All of that and much more, in one plan with no long-term contracts, assisted migrations, and a day-money-back-guarantee. Check out our plans or talk to sales to find the plan that’s right for you.