Hello, can somebody give me an advice please? i have more IP adresses and i'd like to have one of them reserverd just for ISPConfig and Run it on port 80 together with 443 and let the customers choose if they wants to encrypt theirs connection. How should my /root/ispconfig/httpd/conf/httpd.conf look ? Or is there possibility to run two login pages thru ISPconfig apache which one of them (on port80) will have just added link "encrypt you communication" which will redirect to second one on port 443 ?
The problem is that ispconfig has it's own httpd service and runs as 'adminispconfig' user, not www/apache/nobody that most apache configs run as. The other problem is that both the real apache and ispc apache want to bind to port 80 and they can't if the other gets it first. You then have the option of either proxy forward depending on the ServerName and pass it to the real service (so real apache proxyforwards to ispconfig setup) or just use the port 443 port and begone with the port 80 idea. The example below is a port 81 non secure with a proxy from the real apache server mapping an external name of (ispconfig.yourhostingdomain.com:80) to ispconfig (remember, 81 isn't SSL as it won't work). PHP: <VirtualHost *:80>ProxyRequests Off# Port 81 is NON SSL of ispconfigProxyPass / http://localhost:81/ProxyPassReverse / http://localhost:81/ProxyPreserveHost OnServerName ispconfig.yourhostingdomain.comServerAdmin webmaster@yourhostingdomain.comCustomLog /var/log/httpd/ispc-access.log combined</VirtualHost> Otherwise, 443 is just port 81 changed in the ispconfig httpd.conf
The apache webserver allows it to bind it to a special IP. If you bind the ISPConfig webserver to one IP and your apache webserver to all other IP addresses, this should work. I dont remember the exact apache config syntax, please have a look at the apache manual for details.
I think it's something like Listen 1.2.3.4:80 Listen 2.3.4.5:80 Listen 3.4.5.6:80 Listen 4.5.6.7:80 then <VirtualHost 1.2.3.4:80> </VirtualHost> <VirtualHost 2.3.4.5:80> </VirtualHost> etc.
Yes, listen should work well. My first thought was the BindAddress syntax but Listen might be even better. Here is the apache doc as reference: http://httpd.apache.org/docs/1.3/bind.html
