Problems resolving https://IP-Address:81 into https://domain.net:81

[chillifire]

Hi,

I have ISPConfig successfully installed with the domain www.chillifire.net given during the installation procedure. I have now also created a website on ISPConfig www.chillifire.net (http://www.chillifire.net), which work fine on ports 80 (http://www.chillifire.net) and 443 (https://www.chillifire.net), including a signed certificate.

Unfortunately https://www.chillifire.net:81 did not bring up the ISPConfig admin console, but an 'website cannot be found' error. I have looked at file /root/ispconfig/httpd/conf/httpd.conf had a line ServerName www.chillifire.net whcih was commneted out. In uncommented, restarted ispconfig_server and look there, https://www.chillifire.net:81 suddenly worked - well most of the time. Sometimes, the 'website cannot be found' error does still come up, and one has to reload the webpage. Then the ISPConfig site definitely comes up. I cannot seem to discover any consistent pattern, when this does happen though.

Any suggestions, how the resolving of https://IP-Address:81 into https://domain.net:81 can be reliabley achieved?

Any thoughts welcome.

chillifire

[till]

I dont think its a resolving issue. Have you changed the hostname of your server ? Then it might be that you missed some places e.g. /home/admispconfig/ispconfig/lib/config.inc.php

[chillifire]

Hi,

thanks for your support.

I suspect your refer to these lines:
[...]
f(isset($_SERVER['HTTP_HOST'])){
$go_info["server"]["server_url"] = 'https://'.$_SERVER['HTTP_HOST'];
} else {
$go_info["server"]["server_url"] = "https://www.chillifire.net:81";
}
[...]
They are what I expected, right?. So I guess the problem has not been resolved yet.

I have not changed domain name - it was always chillifire.net. But I did have chillifire.net hosted on a differet server recently with a different IP address.

Any more ideas what might be going awry?

Cheers

chillifire


PS: Why was that line ServerName www.chillifire.net in /root/ispconfig/httpd/conf/httpd.conf commented out, when ISPConfig appears to require it? Would you have expected it to be commented out?