Is there any "technical" problem if i put a global alias /admin pointing to the ispconfig folder on the main apache (port 80)? Some clients argue they cant get port 81 because o proxys, i know you will say something about keeping ispconfig isolated, but its really a mess to me... plus, they used to get the control panel by /admin address.
You don't want to do this. You could try using mod_proxy and mod_proxy_html and set up a vhost in your apache on port 443 using the same cert as ISPC. Not sure if it will work, but its definitely in a much much MUCH safer vein than what you are suggesting.
Yes, its more safer to fax a requirement a do it manually over a intranet, but its not what i need. I need to access ISPConfig panels from http://mysite.com/admin
Again, why not try a reverse proxy using mod_proxy and, if necessary, mod_proxy_html? Use the same certs for https and bind to port 443 and you should be fine. Your clients' firewalls are not blocking 443.
Because ill loose the https ability for my sites. And they should enter the panel with "https://www.mydomain.com". Thanks for your help, but im not asking for options, im asking for something particular. My clients used to get into the panel by http://www.domain.com/admin i want to keep this. My question is: "Is there any problem doing that?" anyway ill test it first.
I believe he say to put ispconfig over https over my domain, so i can get it with something like: https://www.mydomain.com but thats not what i want.
You want http://www.mydomain.com instead of https://www.mydomain.com. But you can also do it with mod_proxy...
I want to know if using: http://www.mydomain.com/admin load ISPConfig, not a redirect, not a local alias, not diferent port. ISPConfig, will still works? ill try it on a dev server today..
Have a look here: http://httpd.apache.org/docs/2.0/mod/mod_proxy.html http://www.apacheweek.com/features/reverseproxies
