Change HTTPS from 81 to 443

Hello all,

I want to change the ISPConfig 2 portal from https://server:81 to https://server.

This because there are firewalls by some customers that block port 81.

What is the best solution for this problem?

My O.S. Centos 5.3

 

Hi,

You change port 81 to 443 in the file /root/ispconfig/httpd/conf/httpd.conf

And restart ispconfig

 

Sorry, but i had tried that already. It won't work.

 

You must also change the port in /home/admispconfig/ispconfig/lib/config.inc.php.

 

I have changed:

/root/ispconfig/httpd/conf/httpd.conf
from Port 81 to Port 443
from Listen 81 to 443
from <VirtualHost _default_:81> to <VirtualHost _default_:443>

/home/admispconfig/ispconfig/lib/config.inc.php
$go_info["server"]["server_url"] = "https://web1.domain.com:81"; to $go_info["server"]["server_url"] = "https://web1.domain.com:443";

and restart the ispconfig server. nothing worked when i go tp https://web1.domain.com only the default apache page.....

 

Is it possible that your main Apache is already listening on port 443? What's the output of

Code:

netstat -tap

?

 

yes is does.

 

Hello,

i did the above and when igo to https://[url]www.sieliakus.nl[/url] i get nothing

the netstat tap shows 443 is available??

what do i do wrong?

replacing 443 for 8080 does work? standard 443 wil not work??

 

proxy option

you can also place ispc behind a proxy website. Create a "normal" site site and add the proxy commands in the configuration.

You can then access ispc as it it was a normal site. I have done experiments to proxy either the 80 or 443 ports. Both works, although for https there's a small bug preventing some graphics to come through (you will have to accept both the ispc:81 as well as the proxy:443 certs.

I have opened a bugreport to fix this.

 

Above is a no solution for me

The question remains, with or without proxy Why can't i connect through port 443? other ports work except 443?? What do i do wrong??

Or is that the bug??

 

Like Till said, there's no bug in this regard.
You have to run ispc on port 81 and your normal websites on 443. You can then create a proxy as a normal website (+ DNS entry), which redirects to port 81. This way you can keep ispc running on port 81, and still access ispc via port 443 for locations where port 81 is blocked.

 

Ok, enlighten me.

create new site
then proxy trough that ssl site to the ispconfig site.

via cURL? or is there a standard script for that. There are proxy scripts but have not seen one which works perfect.

wil a iframe work? you wil keep firewall issues

reply may in dutch

If it works we can translate it.

groet
Roy

 

Simplified rulebook

It's via the standard apache directives, which you can specify in ispconfig. Short rulebook:

1. setup ispconfig on port 81 on a dedicated IP address
2. Create a normal site in ispconfig (site in example below)
3. Create both dns entries for your your ispc (on port 81) and your normal ssl site
4. enable ssl and create a certificate. Make sure it works. You will have to use another IP (so you're now using two ip addresses)
5. Add the below in the Apache Directives box. Mind you have to change the domain names to whatever suits you.
   Code:

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

 

Thanks for your reply, i understand it

But i only have one dedicated IP
So i guess it wil not work.

i am experimenting with cgiproxy, a bit of a workaround.

again thanks