Internal Server Error / Internal server error

One of the errors that gives less information at the time of showing itself, and consequently more scare, is the terrifying one Server internal error or, if it leaves in English, Internal Server Error .

One would think that, being the server, the only solution is, then, to call server, the provider of your hosting, and is not badly thought.

In any case is a bloody mistake, because you know that something is not right, but it gives you no clue what is broken

But in reality does not have to be an error of your hosting, they can be many things so we are going to see the possible culprits of an internal error of the server and how to fix it in our web WordPress.

What causes an internal server error?

There are several po sibles culprits namely:

  • Plugins
  • Topic
  • WordPress installation
  • File .htaccess
  • PHP memory
  • Your hosting

To know what is the culprit my advice is to follow this sequence of actions:

Regenerate the file .htaccess

To eliminate the biggest suspect of an internal error of the server, Not the only one, I always start reviewing the file .htaccess .

The problem with this file is that there are many plugins that add lines so that sometimes guess what could have caused the problem is complicated especially if you have no knowledge of servers.

So the easiest, and sure, is to do the following:

  1. Access via FTP or the cPanel of your hosting and rename the current file .htaccess to something else, for example antigua.htaccess
  2. If you go to your site and the internal error of the server has been fixed, access your WordPress desktop, that is, at
  3. Ve a Settings> Permanent links and Saves changes without modifying any settings.

What you have done is force WordPress to generate a new file .htaccess ] clean only with the WordPress rules, and by the way you know it was something in the old.htaccess what caused the error.

Now you have to check what was in that file , that's why you have the copy, which caused the error.

Disable the plugins

The next possible culprit is the plugins simply because can load functions that insert lines in the file .htaccess or break WordPress and all your installation if there is a problem of pr o

As we will not have access to the administration, access your installation of WordPress by FTP or cPanel and rename the folder plugins that is, change the folder that is in the path / wp-content / plugins / to something else, for example / wp-content / plugins_rotos /

What you do with this is disable all plugins automatically ]well you do not, WordPress, not finding the standard path where the plugins are installed.

Visit your site, and if the server's internal error has been fixed, rename the plugins folder to its original name. [19659006] Now you can access the WordPress desktop again, but with all the plugins inactive.

The following you already know, or imagine, right? You have to activate plugins one by one and checking which is causing the internal server error or Internal Server Error .

Once located, to deactivate it, rename your folder or delete it directly by FTP or the panel of your hosting, get in touch with the developer to let them know and offer you a solution, and look for an alternative plugin that offers the same functionality but without errors.

Changes theme … temporarily

If the plugins are not, also the active theme could cause an internal error of the server .

And it is that the themes not only make your web look beautiful and functional, also include (increasingly) internal functions, practically plugins which like your plugins can cause an internal server error.

Here the solution is similar to the previous one, and we will take advantage of ] a trick not very known WordPress, at least not as well known as I would like .

Again, access your installation via FTP or cPanel and check if, in addition to the currently active topic, you have installed a recent default theme of WordPress; I mean the Twenty Something .

If you do not have any of these installed download it from the official WordPress themes directory and upload it to your WordPress installation themes folder ( / wp-content / themes / ).

Once this is done rename the current theme folder to whatever you want . For example, from / wp-content / themes / my-theme / to / wp-content / themes / my-theme-broken / .

In a few seconds WordPress will detect that the current theme is not available in the path stored in the database and it will change to the first default theme that it finds installed, pure WordPress magic .

Now visit your site to check if this has managed to fix the server's internal error.

If so, talk to the developer, get a clean copy of your favorite theme or look for another that offers the same but without errors.

Upload the memory of PHP

] Another possible culprit can be that you have little memory for PHP a directive that is usually marked by default by hosting companies, but that we can manipulate to a certain extent.

If none of the above has worked this could be the problem, so we will try to force r memory available for PHP the programming language used by WordPress, its plugins and issues massively.

This is so because they can match processes on your website at a given time that exceed that available memory, and force a internal error of the server.

It can be, for example, an automated task of a plugin that coincides with the publication of an entry or go to know.

Whatever it is, we will increase the limit of the memory of PHP to check if it was that. To achieve this we have to try to bypass the limits imposed by the server, which we can achieve in several ways.

Increase the PHP memory limit from .htaccess

Add to the file .htaccess the following line :

Save the changes and check to see if the server's internal error was fixed.

Increase the PHP memory limit from wp-config.php

If the above does not work for you, delete that line and add this one to your file wp-config.php :

Again, save the changes and check your website to see if you no longer have the Internal Server Error of the noses.

Increase the memory limit to PHP from php.ini

If you have full access to all the routes of your hosting, locate the PHP parameter configuration file, called php.ini and change the PHP memory limit line to these values:

If not you have access to the file path php.ini original you can create yourself one in the folder wp-admin and add the following:

And if all else fails … call your hosting

If none of the above solves the problem talk to your hosting provider, with your hosting and inform them. They have access to all your server, to the error logs and can more easily determine what caused the problem .

In addition, you can increase, even temporarily, the available memory, so you can review the steps that we have seen previously.

I hope this guide has helped you solve some Internal Server Error or internal server error . If that's the case, share how you managed it with everyone, so you'll help others too.

Loading …

That may also help you:

Causes, solutions to error Are you sure you want to do this?

To what more than once you have seen in WordPress that so little explanatory error? Either when uploading an image or accessing an administration page, and some other situation, sometimes WordPress gives us an error like " Are you sure you want to do this? "

 WordPress error sure do you want to do this?

What is it and why does the error occur? Are you sure you want to do this?

This error message appears when WordPress checks the " nonces " and fails. The " nonces " are unique keys generated by a theme, a plugin or the same WordPress kernel to verify something. So if the verification fails shows you the error .

In practical terms, you'll see that error on several occasions, either uploading a new topic, trying to install a plugin, making changes to topic configurations and plugins or even uploading images and saving changes in an entry.

When you see this error you will also see a link that says " Please try again ", but you can already give it a hundred times to the link that you will always see the same error … unless you do something to fix it.

Do we see how it is fixed? There are several possible culprits and solutions.

Check the plugins

Even disabling a plugin can cause this problem, so if you really want to know if the culprit is a plugin you would actually have to physically delete it.

Now, if you do not want to delete the plugin access your physical installation of WordPress using FTP or Panel (or the file manager of your hosting) and completely renames the plugins folder, which you already know is in / wp-content / plugins / . You can change it to / wp-content / pluginsOFF / to give an example.

Once this is done WordPress deactivates all the plugins and if you access the plugins screen of your WordPress you will see a warning that there is no such folder, because it is true, it does not exist, at least not with the name it should.

Now, with all the inactive plugins really, is when you should try to do the same thing you did when you saw the error of " Are you sure you want to do this? ".

If the error does not appear then you already know that one of the plugins was responsible, so it's time to discover the culprit.

] Rename the folder of the plugins to its original name and go activating one by one, and after activating each one, try to see if the error comes out. When it comes out you know that the culprit is the one you just activated.

Review the topic

If you have not come up with the error by testing plugins, then the next possible culprit can be the active topic

First of all make a backup copy of your active theme on your computer and make sure you have installed the last default WordPress theme, the last one Twenty Loquesea .

A continued physically deletes the active theme by FTP or cPanel, deleting the subject folder . What WordPress will do is return to the default WordPress theme, which you must have installed.

Now, again, try to reproduce the action that showed the error. If you no longer see it, the culprit was the issue and you have to download a clean copy or, in the worst case, use another copy that does not get you in trouble.

Note : sometimes You may be lucky that it is a very silly mistake, but also typical, of some issues, whose folder includes spaces in its name. In this case, rename the theme folder of, for example, " / wp-content / themes / my theme folder / " a " / wp-content / themes / folder-of-my -tema / ".

Edit the file php.ini

If all the above fails I'm afraid that we have to move on to the heavy artillery and modify the file php.ini ]which contains the main PHP configurations of your web hosting.

The main problem is that php.ini is not a WordPress installation file so it can be located in some folder at that your hosting provider does not give you access.

If you do not see it, it will be your turn to talk to your provider and tell them how you can access it, or that they are the ones who make the change for you.

In any case, what would have to be done would be to modify the following values:

To something higher, like …

Once the changes are done you will have to restart the Apache server, or if you are in a shared hosting, contact your hosting provider for them to do it.

Check the security

Also if you are under attack it may not work as mentioned nonces so run to install a good security plugin and check if your site is compromised. [19659008] If that's the case, it'll be your turn to do a good cleaning.

Did it happen to you?

If you've ever seen this error, how did you solve it? Has any of these tricks served you or have you used another one?

NOTICE : This publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

How to remove the limit to WordPress menus • WordPress Help

As we saw some time ago there is a limit on the amount of items you can add to a custom WordPress menu something that is not determined by the WordPress itself but by the server where it is hosted.

This amount, in some cases can be around 50 items and in others 100 but it can vary depending of the configuration of your server, and in particular of Suhosin an advanced PHP protection system that is used in many servers.

Specifically, there is a variable determined by Suhosin that limits the maximum amount of elements that can be saved using PHP scripts, causing this limit on the number of items you can add to a menu in WordPress .

Okay you should not go crazy with the menus and add dec elements but on some websites is essential to offer visitors access to multiple sections such as on news websites, with sub-menus by provinces, categories and subcategories, so it's not that weird

As we saw some time ago, you can modify the parameter that causes this limitation by modifying the PHP.INI file but we will not always have access to this parameter, so let's see some other more accessible solution for the common mortals, especially if we are hosted on shared servers, where there is normally no access to the PHP configuration .

As usual, there is a code that we can add to the file ] .htaccess for skip the limit of WordPress menu items that the server puts us through Suhosin.

Just add this line to your file .htaccess located in the root folder of your WordPress installation:

If that was not enough you could upload it ( reasonably) up to 10,000 normally.

Now, this modification will not always work. In that case you should refer to try remove the limitation from PHP.INI or go to the next method if you have it available.

You rarely find hosting providers that offer a utility to configure the parameters of PHP If this were your case, simply access this utility and modify the values ​​of the parameter max_input_vars to a value where you will not have problems adding as many menu items as "you need".

In the case of ] CDmon you can do it from the section Configure Server of the user panel, specifically in the icon called Configure PHP . There you will find the site where to upload the parameter max_input_vars from the initial values ​​of 1,000 up to the usual limit for shared servers of 10,000, normally more than enough.

You must bear in mind that it is never good to take the limit the configurations of the server, and that increasing the benefits on the one hand can result in an unexpected loss of resources in another aspect, so use this type of tricks only if absolutely necessary, and always aware of possible side effects.

NOTICE : this publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you: