Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

ISPConfig 500 internal server error – Resolve it now

by | Feb 3, 2021

Wondering how to fix the ‘ISPConfig 500 internal server error’? We can help you in fixing it.

Usually, the ISPConfig web panel users face this error when the MaxRequest value exceeds.

Also, this error can occur due to PHP-fpm issues.

ISPConfig is an open-source hosting control panel for Linux. Which is capable of managing multiple servers from one control panel.

Here at Bobcares, we have seen several such ISPConfig related errors as part of our Server Management Services for web hosts and online service providers.

Today, let us see how our Support Engineers fix this ISPConfig error for our customers.

 

How we fix ISPConfig 500 internal server error?

Recently one of our customers approached us with this ISPConfig internal server error. When he tried to access the panel it returned 500 internal server errors. The sample error is as below.

ISPConfig 500 internal server error

Now let us see how our Support Engineers fix this ISPConfig error for our customers.

 

1. Modify the MaxRequest value

Here are the steps we follow to increase the MaxRequest value.

1. First, we log into the server via SSH.

2. Next, we open the file: etc/apache2/mods-available/fcgid.conf. For that, we run the below command.

vi /etc/apache2/mods-available/fcgid.conf

3. After that, we add or edit the line “MaxRequestLen 15728640″ in the file /etc/apache2/mods-available/fcgid.conf, to set the Request Limit to 15MB.

At last, the file should contain the below settings.

AddHandler fcgid-script .fcgi
FcgidConnectTimeout 20
MaxRequestLen 15728640

Note: We can change the value MaxRequestLen as per our requirements.

4. Lastly, we save the changes and restart the Apache.

/etc/init.d/apache2 restart

Finally, this fixes the ISPConfig error.

 

2. Restart the PHP-fpm service

To resolve this error we also restart the PHP-fpm service as well. Here is the command we run to restart it.

# service php-fpm restart

[Still, not able to fix the ISPConfig error? – We’d be happy to help you]

 

Conclusion

In short, the ISPConfig internal server error occurs mainly due to exceeded MaxRequest value or PHP-fpm issue. Today, we saw how our Support Engineers fix this error for our customers.

PREVENT YOUR SERVER FROM CRASHING!

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

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

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

2 Comments

  1. Hi, I have the same error, I have done the steps that you say and the error keep. My fcgid.conf look like it:

    FcgidConnectTimeout 30

    AddHandler fcgid-script .fcgi

    MaxRequestLen 20728640

    The web sites continue working some hours after the ISPConfig error 500, but the error is show in all web sites finally.

    Reply
    • Hi there,

      We are happy to help you. To contact our support team, please initiate a chat from the icon at right-bottom.

      Reply

Submit a Comment

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

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF