Platform: Plesk 7.5.4 Reloaded, CentOS 4
If you need to make changes to Apache’s httpd.include file on Plesk, your changes will get overwritten. This was driving me mad as I needed to make changes globally, not just on a per-domain vhost.conf basis as is recommended by Plesk. I sent an email to the support department of my hoster, Knownhost, asking where the “raw version” of the httpd.include file was — meaning where was the data for which Plesk was overwritting my changes? My logic was that if I could find where Plesk was pulling this data to overwrite httpd.include, I could modify it to my liking. Andrew from Knownhost told me that the data that overwrites the Plesk config files is hardcoded into the websrvmng binary (this is a utility Plesk uses). Also, Plesk data is strewn about in various databases. Ugh! But, he did offer insight into how to get what I wanted.
The trick is to put your changes in the httpd.conf file which will take precedence over httpd.include (be sure to put it before the httpd.include directive). Well, that was simple. Thanks Andrew and Knownhost!
NOTE: I wrote this post months ago and forgot to post it. In that time I’ve upgraded to Plesk 8.0.1 and I’m really liking it. The above information still applies to Plesk 8, except they’ve moved and renamed httpd.include. No matter, as that file will just be overwritten anyway.
4 thoughts on “Plesk, httpd.include, httpd.conf, and you”
Or you could use a vhost.conf or vhost_ssl.conf file which does not get overwritten by plesk – this is the recommended way of doing per virtual host configuration.
Check out http://www.gadberry.com/aaron/2006/02/09/plesk_vhost/ for a good description of this.
@Nick: You must have overlooked the second sentence of my post which states: “… I needed to make changes globally, not just on a per-domain vhost.conf basis …”
vhost.conf is a per-domain change, which is not what I needed to do.
Thx for the explaination .. i was looking for the vhost.conf settings a long time.
You rock! Old post but very useful. I have been trying to get a shared cert to work with Fcgi and SuExec and wasn’t having any luck with those useless vhost.conf files. This was WAY more helpful than anything on the Plesk forums.
BTW to overcome 403 Permission errors for shared ssl certs on a subdomain (mycart.com = mycart.securecheckout.com) use the below and replace “ftpuser” with your ftp user name:
SuexecUserGroup ftpuser psacln