+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Usage (/forum-34.html)
+--- Thread: ispcp "custom" virtualhost and NameVirtualHost (/thread-10279.html)
ispcp "custom" virtualhost and NameVirtualHost - Boter - 04-07-2010 12:32 AM
Hey! I was just wondering... Where is the "template" that ispcp builds apache's virtualhosts?
On some ubuntu ispcp server I would like to have added virtualhosts as
*:80 and ufcorse NameVirtualHost as *:80
I was changing /root/ispcp-omega-1.0.5/configs/ubuntu/apache/parts/*_entry.tpl
files and manually wrote *:80 for each virtualhost/namevirtualhost, restarted daemon, but hosts are stil generated as SOME_IP:80 and
NameVirtualHost SOME_IP:80
Any idea?
RE: ispcp "custom" virtualhost and NameVirtualHost - gOOvER - 04-07-2010 12:44 AM
Please Post the nextime into the correct Forum
=> moved
RE: ispcp "custom" virtualhost and NameVirtualHost - Boter - 04-07-2010 12:48 AM
Sorry, noticed
Any solution yet?
RE: ispcp "custom" virtualhost and NameVirtualHost - Jadawin - 04-07-2010 02:59 AM
(04-07-2010 12:32 AM)Boter Wrote: I was changing /root/ispcp-omega-1.0.5/configs/ubuntu/apache/parts/*_entry.tpl
It would be more useful if you change the right configs
/etc/ispcp/apache/parts/*_entry.tpl
RE: ispcp "custom" virtualhost and NameVirtualHost - Boter - 04-07-2010 02:59 AM
Hm, will check. Thanks!
Actually that don't work. Is there anything else to do? I edited /etc/ispcp/apache/parts/*_entry.tpl
I changed as I need, but no changes (when I add subdomain it still generates old configs), restarted apache and ispcp daemon.
Any idea?
RE: ispcp "custom" virtualhost and NameVirtualHost - pgentoo - 04-07-2010 04:45 AM
If you update the templates, it should apply to newly added domains/subdomains, but if you are trying to update existing domains/subdomains, you'll need to rebuild your config (see the documentation section of the website).
You should be able to change /etc/ispcp/apache/parts/{dmn_entry.tpl, als_entry.tpl, sub_entry.tpl) to to for example:
<VirtualHost {DMN_IP}:80>
to
<VirtualHost *:80>
I don't fully understand why you want to do this though. Doing this removes the ability to seperate domains onto seperate IP's, which is something that is required for SSL sites for instance. Is this some work around in an attempt to do load balancing or something?
Also, if you manually update apache (or other) configs which are maintained by ispcp, you need to overwrite the "working" copy with your updated copy. Example here would be to update /etc/ispcp/apache/working/ispcp.conf if you change vhosts manually. Otherwise, your manual changes will be overwritten next time ispcp modifies the config file.