Facebook
Twitter
A
andrewatopenads
Guest
Hi,
I am trying to install Plesk 8.2 on an Amazon EC2 server. After finding that Plesk 8.2 will not install on a base installation of CentOS 4.4, I have managed to install on a base install of Fedora Core 4.
However, whenever I try to go to log into the Plesk control panel to complete the installation (ie. connect to port 8443 as described in this page of the installation guide),
I am re-directed to a domain name that is only suitable for DNS resolution inside the Amazon EC2 network; and as such, I cannot log into the Plesk control panel.
I presume that during installation, or possibly at run time, Plesk has grabbed / grabs the domain name of the server via a reverse lookup of the IP address of the server.
Can someone please explain where Plesk stores the domain name that it believes it is installed on, or, alternatively, how I can alter the behaviour of Plesk so that it does not perform a lookup of the domain name at run time? This does not seem to be mentioned anywhere in the installation guide or the administrator's guide.
I am trying to install Plesk 8.2 on an Amazon EC2 server. After finding that Plesk 8.2 will not install on a base installation of CentOS 4.4, I have managed to install on a base install of Fedora Core 4.
However, whenever I try to go to log into the Plesk control panel to complete the installation (ie. connect to port 8443 as described in this page of the installation guide),
I am re-directed to a domain name that is only suitable for DNS resolution inside the Amazon EC2 network; and as such, I cannot log into the Plesk control panel.
I presume that during installation, or possibly at run time, Plesk has grabbed / grabs the domain name of the server via a reverse lookup of the IP address of the server.
Can someone please explain where Plesk stores the domain name that it believes it is installed on, or, alternatively, how I can alter the behaviour of Plesk so that it does not perform a lookup of the domain name at run time? This does not seem to be mentioned anywhere in the installation guide or the administrator's guide.
