Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : Stupid whm/apache bug

[Klentelaris]

It seems latest version of whm have a bug.If you put a lines of apache module into httdp.conf at last line,when someone add new domain(which means adding virtual conf)it adds instead normaly after last line it add after last character of last line into same line,and that screw apache starting since it have syntax error beacuse of it.So that means if you need to put somethign into httpd.conf you need to add before end of file.Beside that,like is that not enough,it seems whm doesnt like to see anything on end of line beside it's own lines.Apache stopped again beacuse of syntax error,but this time not beauce of new added domain,its a beacuse whm
added again default lines of it to end of file and lines was already there,just not on end of file since i added lines requied for one module of apache.
So in shortly dont add anything to end of httpd.conf file.

And this is what was added and duplicated:
Include "/usr/local/apache/conf/includes/errordocument.conf"
Alias /bandwidth/ /usr/local/bandmin/htdocs/
Alias /sys_cpanel/ /usr/local/cpanel/sys_cpanel/
Alias /java-sys/ /usr/local/cpanel/java-sys/
Alias /img-sys/ /usr/local/cpanel/img-sys/
Alias /akopia/ /usr/local/cpanel/3rdparty/interchange/share/akopia/
Alias /neo-images/ /usr/local/cpanel/base/neomail/neo-images/
Alias /mailman/archives/ /usr/local/cpanel/3rdparty/mailman/archives/public/
Alias /pipermail/ /usr/local/cpanel/3rdparty/mailman/archives/public/
Alias /interchange/ /usr/local/cpanel/3rdparty/interchange/share/interchange/
Alias /interchange-5/ /usr/local/cpanel/3rdparty/interchange/share/interchange-5/
ScriptAlias /cgi-sys/ /usr/local/cpanel/cgi-sys/
ScriptAlias /mailman/ /usr/local/cpanel/3rdparty/mailman/cgi-bin/
ScriptAliasMatch ^/?cpanel/?$ /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAliasMatch ^/?securecpanel/?$ /usr/local/cpanel/cgi-sys/sredirect.cgi
ScriptAliasMatch ^/?kpanel/?$ /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAliasMatch ^/?controlpanel/?$ /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAliasMatch ^/?securecontrolpanel/?$ /usr/local/cpanel/cgi-sys/sredirect.cgi
ScriptAliasMatch ^/?webmail/?$ /usr/local/cpanel/cgi-sys/wredirect.cgi
ScriptAliasMatch ^/?whm/?$ /usr/local/cpanel/cgi-sys/whmredirect.cgi
ScriptAliasMatch ^/?securewhm/?$ /usr/local/cpanel/cgi-sys/swhmredirect.cgi

[servertechs]

Is your cpanel/Whm on stable release

[Klentelaris]

Originally Posted by servertechs

Is your cpanel/Whm on stable release

No idea but considering it is latest i presume it is.

[cPanelDavidG]

Originally Posted by Klentelaris

No idea but considering it is latest i presume it is.

There are several branches of cPanel including EDGE, CURRENT, RELEASE and STABLE. If you are using the defaults, you would be on RELEASE.

Note, modifying httpd.conf in a cPanel/WHM environment without distilling the configuration is not recommended. You may wish to review the documentation for EA3 which manages Apache in cPanel/WHM environments at:

http://www.cpanel.net/support/docs/ea/ea3/ea3.html

[Klentelaris]

Originally Posted by cPanelDavidG

There are several branches of cPanel including EDGE, CURRENT, RELEASE and STABLE. If you are using the defaults, you would be on RELEASE.

Note, modifying httpd.conf in a cPanel/WHM environment without distilling the configuration is not recommended. You may wish to review the documentation for EA3 which manages Apache in cPanel/WHM environments at:

http://www.cpanel.net/support/docs/ea/ea3/ea3.html

Well i added same lines in previous whm version and then i didnt have any problem during that time.This happened with latest whm/cpanel version

[Patrick]

Originally Posted by Klentelaris

Well i added same lines in previous whm version and then i didnt have any problem during that time.This happened with latest whm/cpanel version

With EasyApache2 (much better, IMO!), you could always make changes directly to Apache's configuration files without having to worry about them being lost. When cPanel 11 and EasyApache3 were introduced this was no longer the case and you have to modify the various Apache include files to ensure the changes are saved.

Of course you can still make changes directly to the Apache configuration files, but during the next Apache update (including PHP upgrades) they will be lost, so it's best to use the include files available within WHM or you can do it manually via SSH.

It's a PITA, but that's how it is... :/

[Klentelaris]

Originally Posted by Pat H

With EasyApache2 (much better, IMO!), you could always make changes directly to Apache's configuration files without having to worry about them being lost. When cPanel 11 and EasyApache3 were introduced this was no longer the case and you have to modify the various Apache include files to ensure the changes are saved.

Of course you can still make changes directly to the Apache configuration files, but during the next Apache update (including PHP upgrades) they will be lost, so it's best to use the include files available within WHM or you can do it manually via SSH.

It's a PITA, but that's how it is... :/

Hmm yes i think using include files will be best since that will secure possible screwups.