Hello Is there a way to avoid https://name.tld:81 when accessing phpmyadmin and roundcubemail Now the user must enter https://name.tld:81/phpmyadmin and the same for roundcubemail. Would be nice if it was possible to change it such that they can be accessed like http://name.tld/webmail or http://webmail.name.tld. A second question is it possible to change the roundcubemail url should that it would be renamed to webmail ? Cheers Wupty Du
What i've done is created a new co-domain for my website and set it to forward to my phpmyadmin and roundcubemail Now if i go to webmail.<mydomain>.com, it automatically redirects me to https://<mydomain>.com:81/roundcubemail
till : It looks nice but i can't see how to transfer this for webmail and phpmyadmin and make it work on any site added in ISPConfig. Can you give me a hint ?
The Howto looks great, sounds exactly like what I was searching for. Question: After configuring the ProxyPass, is there a way to disable remote access to port 81?
Hi All, yesterday night I spent some time to configure my ISPConfig so that it would listen to port 80 - as described in the Howto mentioned above by Till. Some comments on that: 1. I don't know why, but I had to adjust the VirtualHost settings: Code: [...] <VirtualHost [B]111.222.333.444:80[/B]> ServerName ispconfig.example.com[B]:80[/B] [...] Maybe it's because my machine runs on a Virtuozzo virtual server? 2. The performance when addressing ISPConfig via Proxy is awful. Every now and then I get proxy errors because of failed DNS requests, etc. So it looks that I might have another problem on my system that has to do with the resolver?! 3. When it comes to system configuration, I'd rather use SSL. So did you think about adjusting the howto for a SSL configuration?! 4. Once I can reach ISPConfig through my main Apache, there is no need to have the ISPConfig-Apache publically accessible. Is there a way to make this webserver a purely internal machine that is only accessible by proxying through the main webserver? I'd love to read more about these subjects. Thanks loads in advance! Tom
Hi Falco, the reason for the performance problems were indeed a bad nameserver at 1und1. After correcting the entries in resolv.conf everything worked fabulous. Point 3 is also solved - managed to reconfigure apache2 to forward from an ssl-Connection. Point 4 is still of interest. How would you block a connect from !=localhost to access ispconfig on port 81? Regards, Tom
Simple alternative You also can use the Redirect option within your /etc/apache2/apache2.conf file like this: Redirect /webmail http://www.yourhostingcompany.com:81/roundcubemail Redirect /phpmyadmin http://www.yourhostingcompany.com:81/phpmyadmin Of course restart apache2 afterwards with /etc/init.d/apache2 restart
When i follow that guide on http://www.howtoforge.com/apache_reverse_proxy_ispconfig it does nothing good, it just makes it impossible to click on any sites in the controlpanel. I have followed the guide to the point, and only adjusted the domainname.
And as a side note, what i want is that it is possible for my clients to type: webmail.theirdomain.com or phpmyadmin.theirdomain.com so if my clients have the following domains: testdomain1.com and testdomain2.com. Then they can type http://webmail.testdomain1.com or http://webmail.testdomain2.com and somehow they will reach https://serverdomain.com:81/roundcubemail
