Cpanel workaround to MaxClient setting not being saved

The questions posed was “CPanel wont allow me to set MaxClients of apache to a number greater than 300. Even if the changes are made directly to the httpd.conf, and then distilled, the changes will not be saved once CPanel rebuilds the apache configuration using /usr/local/cpanel/bin/build_apache_conf. How can we make this change permanent?”

In the latest release of cPanel, the value for MaxClients is set in
Main >> Service Configuration >> Apache Configuration >> Global Configuration
which corresponds to the file —

More specifically, when rebuilding the httpd.conf, WHM will use the default values set in that file when doing a rebuild (/usr/local/cpanel/bin/build_apache_conf). This file does not exist by default, and is only present when the default values are saved within
Main >> Service Configuration >> Apache Configuration >> Global Configuration.
To change this setting, go to the Global Configuration and change the settings there from 150 (default) to whatever you would like and then click “Save”. Now when the


command is run, and the settings in;


will be used to rebuild the httpd.conf with the correctly modified changes. This should work for now. But this is still buggy in the sense that WHM (WHM >> Apache Configuration) will still only allow values no greater than 256.

If you go there, and apply the 300 setting, you will see this message displayed in red font: “Value (300) is over the limit (256), using previously saved value (if any) or default (150)”

Cpanel is working on this and will have an answer soon but in the meantime, the changes mentioned above will work.


I am a g33k, Linux blogger, developer, student and Tech Writer for My passion for all things tech drives my hunt for all the coolz. I often need a vacation after I get back from vacation....

Leave a Reply

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