HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

If you want to run ISPConfig behind a proxy, because you don't want to run SSL on port 81, but also don't want to change the ISPC code, you might want to run a proxy to redirect e.g. https://ispc.example.tld to https://server.example.tld:81.
You can setup an Apache configuration like for the ispc website (you can put this in the Apapche directives of an ISPconfig website if you like):

Quote:

ProxyRequests Off
SSLProxyEngine on
<Proxy https://ispc.example.tld/>
Order deny,allow
Allow from all
</Proxy>
<Location />
Order deny,allow
Allow from all
</Location>
ProxyPass / https://server.example.tld:81/
ProxyPassReverse / https://server.example.tld:81/

I did find some errors in the ISPC2 code unfortunately. Some parts of the code use a statement like:

Code:

<?echo $go_info["server"]["server_url"]?>

to generate the URL. I believe this is wrong. You should leave it to the webserver to stick to its website. In order to solve this, I had to edit three files to make ISPC2 work correctly behind a proxy:

Code:

/home/admispconfig/ispconfig/web/admin/lib/admin.inc.php

/home/admispconfig/ispconfig/web/isp_kunde/lib/admin.inc.php

/home/admispconfig/ispconfig/web/isp_manager/lib/admin.inc.php

and remove the redirect link code per above for every entry which begins with

Code:

menuDaten.neu(new LinkEintrag

Perhaps this can be changed in the standard codebase of ISPConfig 2? :cool: