How to run the Admin panel in a Subdomain?

[dragnovich]

Hello I had some customers that can't access their control panel, because they are behind a firewall or proxie, but they ABSOLUTELLY CAN'T CHANGE/MAP/FORWARD/GRANT/GET access to the 8443 port... the only solution is. Mapping the Control Panel to a subdomain of my site...

like:
https://cp.myhost.com/

This means i need it TO RUN in the standard https: port 443 in the cp subdomain in the myhost.com domain

I search the forum and DID NOT see any instructions about how to do it ... just some persons saying I DO IT!

but HOW!! ??

So how can I do that!
(preferebly ADD it as an option to access the Admin Panel, I mean left the actual 8443 port for the other sites, but this is not totally necesary , if cant be mixed I prefer to use the subdomain option and stop using the 8443 port)

better yet add it as the WEBMAIL.<domain> subdomain on all sites, that will be added in all sites. (cp.<domain>

Thanks!.

 

[dragnovich]

so no body have any a clue??

 

[eth4n]

you need to proxy HTTP requests from your client to your admin panel. google for mod_proxy (apache module). put mod_proxy directive in the virtualhost of your subdomain.

 

[dragnovich]

I had installed the proxy module but I can't make it work it gives me a forbidden error.. so what's wrong?? Or what do I need to add/remove??

I had added the "cp" A record in the domain DNS, and this configuration, to the SERVER /etc/httpd/conf/httpd.conf file...

<IfModule mod_proxy.c>
   ProxyRequests Off

   ProxyRemote https ://cp.myhost.com/ https ://www.myhost.com:8443

   <Proxy *>
      Order deny,allow
      Deny from all
      Allow from .myhost.com
   </Proxy>
</IfModule>

The MOD_PROXY is working because If I remove it it sends me an 404 error, and when Active I got a Forbidden error (403) error

Regards!

Note: I added the spaces between the http to avoid the forum program to add the URL links.

 

[eth4n]

You need ProxyPass and ProxyPassReverse. Check http://httpd.apache.org/docs/2.2/en/mod/mod_proxy.html.

Is your apache version matching 2.2? If not check the appropriate manual.

Proxying to https (SSL) might not work. So try http (Non-SSL) first.

About the SSL-issue check http://httpd.apache.org/docs/2.2/en/ssl/ssl_faq.html#vhosts and http://httpd.apache.org/docs/2.2/en/ssl/ssl_faq.html#vhosts2.