Quote:
Originally Posted by till
If you want to use customports, then you have to configure them in the vhost file like I explained above and like it is explained in other threads here in the forum as well. If you dont configure your custom ports, then it wont work of course  |
Till, my master template looks also like tio289. But I did the change that you said and it worked for ssl/non-ssl sites thanks
, now is something like this (I needed to re-save the vhosts):
Quote:
<tmpl_loop name="vhosts">
<tmpl_if name='ssl_enabled'>
<VirtualHost {tmpl_var name='ip_address'}:443>
<tmpl_else>
<VirtualHost {tmpl_var name='ip_address'}:81>
</tmpl_if>
|
However, really to implement a custom port by vhost in the Control Panel is a too hard task?
I think that modify templates should be an "exception" action, what happens with that templates when ispconfig is upgraded? Would be needed to re-apply the changes to the templates? Also exists the problem with choose a different port/IP for different vhosts (maybe only some vhosts run with a reverse-proxy and not all of them)
I understand that you may have other priorities but don't forget this please =)
Thanks