Plesk Expand 2.1.3-4 Release Notes. ************************************************************************** * Please read chapter "Known Problems and Limitations" attentively * * prior to starting any install/upgrade routines * ************************************************************************** Table of contents ================= Introduction Requirements Plesk Expand Installation Instructions PSA API RPC Installation Instructions What's new Known Problems and Limitations License Installation Centralized DNS Centralized Mail Contact Information Introduction ============ Plesk Expand is the hosting automation software that unites multiple Plesk servers on a single hosting platform. It centrally manages all of your customers, domains, IP pools, provides centralized log-in across Plesk servers, implements intelligent provisioning according to the server load rules and more. Plesk Expand can be easily integrated with provider's infrastructure through a set of special APIs. Plesk Expand can be installed over a Plesk for Linux/Unix server (see "Software Requirements" topic for a list of Plesk version supported), or on a clean Linux server (i.e., with no Plesk installed). Before starting the installation or upgrade process, we strongly recommend that you create a full system backup of the entire server. Plesk Expand requires the PSA API RPC software to be installed on every managed Plesk Server. PSA API RPC is included in the Plesk for Linux software as an optional package and must be installed prior to connecting Plesk server to Plesk Expand. PSA API RPC for FreeBSD is included in the base Plesk for FreeBSD distribution. No additional steps are required. For Windows servers, no additional steps are required as well; all components are included in the base distribution package. Plesk Expand software is available on the SWsoft website: http://www.swsoft.com/products/plesk/expand This SOFTWARE is provided on an "AS IS" basis, without warranty of any kind, including without limitation the warranties of merchantability, fitness for a particular purpose and non-infringement. The entire risk as to the quality and performance of the SOFTWARE is borne by the USER. Should the SOFTWARE prove defective, you and not SWsoft assume the entire cost of any service and/or repair. All warranties, either express or implied, are disclaimed. Requirements ============ Hardware Requirements --------------------- Plesk Expand installation requires an IBM PC-compatible computer with the following hardware configuration: - I586-compatible CPU (Intel Celeron, Pentium II, Pentium III, Pentium 4, or AMD Athlon); - At least 256 MB of RAM; - Hard drive(s) with at least 1 GB of free disk space; - A network card. Software Requirements --------------------- Plesk Expand 2.1.3 can be installed either in standalone mode or over existing Plesk for Linux installation. In both modes Plesk Expand can be installed on the server configuration of the following operating systems: - RedHat Enterprise Linux 3 - RedHat Enterprise Linux 4 - Fedora Core 2 - Fedora Core 3 - Fedora Core 4 - CentOS 3.4 or higher - CentOS 4.3 or higher Plesk Expand can be installed over following Plesk server installations: - Plesk 8.1 for Linux Make sure you've chosen proper Plesk Expand distribution prior to starting installation. See the "Centralized Mail" topic for Centralized Mail specific requirements. See the "Centralized DNS" topic for Centralized DNS specific requirements. Special Requirements to Plesk Expand installation inside Virtuozzo. ------------------------------------------------------------------- We recommend that you use the following VPS configuration: - AS3/AS4/FC2/FC3/FC4/CE3/CE4-based VPS - DISKSPACE="1048576:1153434" - DISKINODES="200000:220000" - PRIVVMPAGES = "250000:250000" You can use the 'unlimited' template for VPS creation. Be sure that VPS has no MySQL template installed. Incompatible Software --------------------- none known; Plesk Requirements ------------------- Plesk Expand supports the following Plesk versions: * Plesk 8.1.x for Linux/Unix * Plesk 8.1.x for Windows Plesk servers for Linux platforms must have the psa-api-rpc package installed. See the 'PSA API RPC Installation instructions' topic for details. Plesk Expand Installation Instructions ====================================== You can select one of the following Plesk Expand installation methods: - Use web-based installer; - Use console-based interactive autoinstaller; - Perform manual installation. Web-based Installation ---------------------- 1. Run a web browser and open the page https://expand-webinstall.swsoft.com/wui/ 2. Follow the on-screen instructions. Console-based Installation -------------------------- 1. Download the expand_installer-2.7.1-3.sh file to your server. 2. Run the installer by issuing the following command: # sh expand_installer-2.7.1-3.sh 3. Follow the on-screen instructions. Manual Installation ------------------- A. Additional Software Requirements The following packages need to be pre-installed: - Apache web server (httpd) at least version 2.0.46; - Apache SSL module (mod_ssl) at least version 2.9.0; - Xerces-C XML engine (xerces-c) version at least 2.5.0; - Curl transport engine (curl) version at least 7.10.6. All the above packages can be installed from a distribution CD for an appropriate OS. For Your convenience, we provide them along with Plesk Expand. The rest of the packages archived in the tarball cannot be substituted for packages of other vendors because they contain patched code to meet the requirements of Plesk Expand. - mysql++; - expand (Plesk Expand itself). Additionally, if Plesk Expand is to be installed on a clean server (i.e. with no Plesk installed), the following packages are required: - php; - php-mysql; - php-domxml (for Fedora Core and Enterprise Server 3 only). B. Installation Procedure Plesk Expand and required software are distributed in the RPM packages rolled into a single tarball: For Fedora Core 2: expand_2_1_3-4.fc2.tar For Fedora Core 3: expand_2_1_3-4.fc3.tar For Fedora Core 4: expand_2_1_3-4.fc4.tar For CentOS 3.x: expand_2_1_3-4.co3.tar For CentOS 4.x: expand_2_1_3-4.co4.tar For Redhat Enterprise Linux 3: expand_2_1_3-4.el3.tar For Redhat Enterprise Linux 4: expand_2_1_3-4.el4.tar For installation on top of Plesk 8.1: expand_2_1_3-4_psa8.1.tar This set of files is sufficient for the installation of Plesk Expand. The tarball contains the following RPM packages: For Fedora Core 2: * expand-2.1.3-4.i586.rpm * expand-dist-repository-2.1.3-4.i586.rpm * expand-locale-base-en_US-2.1.3-070410.noarch.rpm * expand-selinux-support-1.17.30-2.126-2.1.3-4.noarch.rpm * expand-selinux-support-1.17.30-2.19-2.1.3-4.noarch.rpm * expand-selinux-support-1.23.16-6-2.1.3-4.noarch.rpm * expand-selinux-support-1.27.1-2.28-2.1.3-4.noarch.rpm * cerberus-helpdesk-3.0-swsoft-plugin-1.0.0-070410.tgz * kayako-supportsuite-3.0-swsoft-plugin-1.0.0-070410.tgz * mysql++-1.7.19-8.sw.i586.rpm * xerces-c-2.5.0-6.sw.i586.rpm * boost-1.32.0-3.i386.rpm * libssh2-0.14-2.sw.i586.rpm * swagent-2.6.1-124.swsoft.i386.rpm * mysql-3.23.58-4.i386.rpm * mysql-server-3.23.58-4.i386.rpm * perl-DBD-MySQL-2.9002-1.i386.rpm * perl-DBI-1.37-1.i386.rpm * zziplib-0.12.23-0.9.0.i586.rpm * libmcrypt-2.5.2-1.9.0.i586.rpm * libmcal-0.6-3.9.0.i586.rpm * libidn-0.5.6-1.i386.rpm * php-4.3.10-2.4.fc2.sw1.i386.rpm * php-domxml-4.3.10-2.4.fc2.sw1.i386.rpm * php-mbstring-4.3.10-2.4.fc2.sw1.i386.rpm * php-mysql-4.3.10-2.4.fc2.sw1.i386.rpm * php-pear-4.3.10-2.4.fc2.sw1.i386.rpm * php-ssh2-4.3.10-2.4.fc2.sw1.i386.rpm * aspell-en-0.51-6.i386.rpm * aspell-0.50.3-16.i386.rpm * mod_ssl-2.0.47-2.9.0.i586.rpm * apr-0.9.4-11.i386.rpm * apr-util-0.9.4-14.i386.rpm * httpd-2.0.49-4.i386.rpm * libxslt-1.1.5-1.i386.rpm * sendmail-8.12.11-4.6.i386.rpm * curl-7.11.1-1.i386.rpm For Fedora Core 3: * expand-2.1.3-4.i586.rpm * expand-dist-repository-2.1.3-4.i586.rpm * expand-locale-base-en_US-2.1.3-070410.noarch.rpm * expand-selinux-support-1.17.30-2.126-2.1.3-4.noarch.rpm * expand-selinux-support-1.17.30-2.19-2.1.3-4.noarch.rpm * expand-selinux-support-1.23.16-6-2.1.3-4.noarch.rpm * expand-selinux-support-1.27.1-2.28-2.1.3-4.noarch.rpm * cerberus-helpdesk-3.0-swsoft-plugin-1.0.0-070410.tgz * kayako-supportsuite-3.0-swsoft-plugin-1.0.0-070410.tgz * mysql++-1.7.19-8.sw.i586.rpm * xerces-c-2.5.0-6.sw.i586.rpm * boost-1.32.0-3.i386.rpm * libssh2-0.14-2.sw.i586.rpm * swagent-2.6.1-124.swsoft.i386.rpm * mysql-3.23.58-4.i386.rpm * mysql-server-3.23.58-4.i386.rpm * perl-DBD-MySQL-2.9002-1.i386.rpm * perl-DBI-1.37-1.i386.rpm * curl-7.13.2-3.i386.rpm * php-4.3.10-3.2.fc3.sw1.i386.rpm * php-domxml-4.3.10-3.2.fc3.sw1.i386.rpm * php-mbstring-4.3.10-3.2.fc3.sw1.i386.rpm * php-mysql-4.3.10-3.2.fc3.sw1.i386.rpm * php-pear-4.3.10-3.2.fc3.sw1.i386.rpm * compat-libstdc++-8-3.3.4.2.i386.rpm * php-ssh2-4.3.10-3.2.fc3.sw1.i386.rpm * libxslt-1.1.11-1.i386.rpm * libidn-0.5.6-1.i386.rpm * aspell-0.50.5-3.fc3.i386.rpm * aspell-en-0.51-11.i386.rpm * apr-0.9.4-23.i386.rpm * apr-util-0.9.4-17.i386.rpm * httpd-2.0.52-3.i386.rpm * mod_ssl-2.0.52-3.i386.rpm * distcache-1.4.5-6.i386.rpm * httpd-suexec-2.0.52-3.i386.rpm * selinux-policy-targeted-sources-1.17.30-2.19.noarch.rpm * sendmail-8.13.1-2.i386.rpm For Fedora Core 4: * expand-2.1.3-4.i586.rpm * expand-dist-repository-2.1.3-4.i586.rpm * expand-locale-base-en_US-2.1.3-070410.noarch.rpm * expand-selinux-support-1.17.30-2.126-2.1.3-4.noarch.rpm * expand-selinux-support-1.17.30-2.19-2.1.3-4.noarch.rpm * expand-selinux-support-1.23.16-6-2.1.3-4.noarch.rpm * expand-selinux-support-1.27.1-2.28-2.1.3-4.noarch.rpm * cerberus-helpdesk-3.0-swsoft-plugin-1.0.0-070410.tgz * kayako-supportsuite-3.0-swsoft-plugin-1.0.0-070410.tgz * mysql++-1.7.19-8.sw.i586.rpm * xerces-c-2.5.0-6.sw.i586.rpm * boost-1.32.0-3.i386.rpm * libssh2-0.14-2.sw.i586.rpm * swagent-2.6.1-124.swsoft.i386.rpm * mysql-3.23.58-4.i386.rpm * mysql-server-3.23.58-4.i386.rpm * perl-DBD-MySQL-2.9002-1.i386.rpm * perl-DBI-1.37-1.i386.rpm * curl-7.13.2-3.i386.rpm * php-4.3.10-3.2.fc3.sw1.i386.rpm * php-domxml-4.3.10-3.2.fc3.sw1.i386.rpm * php-mbstring-4.3.10-3.2.fc3.sw1.i386.rpm * php-mysql-4.3.10-3.2.fc3.sw1.i386.rpm * php-pear-4.3.10-3.2.fc3.sw1.i386.rpm * compat-libstdc++-8-3.3.4.2.i386.rpm * php-ssh2-4.3.10-3.2.fc3.sw1.i386.rpm * libxslt-1.1.11-1.i386.rpm * libidn-0.5.6-1.i386.rpm * aspell-0.50.5-3.fc3.i386.rpm * aspell-en-0.51-11.i386.rpm * apr-0.9.4-23.i386.rpm * apr-util-0.9.4-17.i386.rpm * httpd-2.0.52-3.i386.rpm * mod_ssl-2.0.52-3.i386.rpm * distcache-1.4.5-6.i386.rpm * httpd-suexec-2.0.52-3.i386.rpm * selinux-policy-targeted-sources-1.17.30-2.19.noarch.rpm * sendmail-8.13.1-2.i386.rpm For CentOS 3.x: * expand-2.1.3-4.i586.rpm * expand-dist-repository-2.1.3-4.i586.rpm * expand-locale-base-en_US-2.1.3-070410.noarch.rpm * expand-selinux-support-1.17.30-2.126-2.1.3-4.noarch.rpm * expand-selinux-support-1.17.30-2.19-2.1.3-4.noarch.rpm * expand-selinux-support-1.23.16-6-2.1.3-4.noarch.rpm * expand-selinux-support-1.27.1-2.28-2.1.3-4.noarch.rpm * cerberus-helpdesk-3.0-swsoft-plugin-1.0.0-070410.tgz * kayako-supportsuite-3.0-swsoft-plugin-1.0.0-070410.tgz * mysql++-1.7.19-8.sw.i586.rpm * xerces-c-2.5.0-6.sw.i586.rpm * boost-1.32.0-3.i386.rpm * libssh2-0.14-2.sw.i586.rpm * swagent-2.6.1-124.swsoft.i386.rpm * mysql-3.23.58-4.i386.rpm * mysql-server-3.23.58-4.i386.rpm * perl-DBD-MySQL-2.9002-1.i386.rpm * perl-DBI-1.37-1.i386.rpm * php-4.3.6-1.3.co3.sw1.i386.rpm * php-mysql-4.3.6-1.3.co3.sw1.i386.rpm * php-domxml-4.3.6-1.3.co3.sw1.i386.rpm * libidn-0.5.6-1.i386.rpm * php-ssh2-4.3.6-1.3.co3.sw1.i386.rpm * libxslt-1.0.33-5.i386.rpm * httpd-2.0.46-44.ent.centos.2.i386.rpm * curl-7.10.6-4.2.i386.rpm * mod_ssl-2.0.46-44.ent.centos.2.i386.rpm * sendmail-8.12.11-4.RHEL3.1.i386.rpm * perl-CGI-2.89-90.4.i386.rpm For CentOS 4.x: * expand-2.1.3-4.i586.rpm * expand-dist-repository-2.1.3-4.i586.rpm * expand-locale-base-en_US-2.1.3-070410.noarch.rpm * expand-selinux-support-1.17.30-2.126-2.1.3-4.noarch.rpm * expand-selinux-support-1.17.30-2.19-2.1.3-4.noarch.rpm * expand-selinux-support-1.23.16-6-2.1.3-4.noarch.rpm * expand-selinux-support-1.27.1-2.28-2.1.3-4.noarch.rpm * cerberus-helpdesk-3.0-swsoft-plugin-1.0.0-070410.tgz * kayako-supportsuite-3.0-swsoft-plugin-1.0.0-070410.tgz * mysql++-1.7.19-8.sw.i586.rpm * xerces-c-2.5.0-6.sw.i586.rpm * boost-1.32.0-3.i386.rpm * libssh2-0.14-2.sw.i586.rpm * swagent-2.6.1-124.swsoft.i386.rpm * mysql-3.23.58-4.i386.rpm * mysql-server-3.23.58-4.i386.rpm * perl-DBD-MySQL-2.9002-1.i386.rpm * perl-DBI-1.37-1.i386.rpm * php-4.3.6-1.3.co3.sw1.i386.rpm * php-mysql-4.3.6-1.3.co3.sw1.i386.rpm * php-domxml-4.3.6-1.3.co3.sw1.i386.rpm * libidn-0.5.6-1.i386.rpm * php-ssh2-4.3.6-1.3.co3.sw1.i386.rpm * libxslt-1.0.33-5.i386.rpm * httpd-2.0.46-44.ent.centos.2.i386.rpm * curl-7.10.6-4.2.i386.rpm * mod_ssl-2.0.46-44.ent.centos.2.i386.rpm * sendmail-8.12.11-4.RHEL3.1.i386.rpm * perl-CGI-2.89-90.4.i386.rpm For Redhat Enterprise Linux 3: * expand-2.1.3-4.i586.rpm * expand-dist-repository-2.1.3-4.i586.rpm * expand-locale-base-en_US-2.1.3-070410.noarch.rpm * expand-selinux-support-1.17.30-2.126-2.1.3-4.noarch.rpm * expand-selinux-support-1.17.30-2.19-2.1.3-4.noarch.rpm * expand-selinux-support-1.23.16-6-2.1.3-4.noarch.rpm * expand-selinux-support-1.27.1-2.28-2.1.3-4.noarch.rpm * cerberus-helpdesk-3.0-swsoft-plugin-1.0.0-070410.tgz * kayako-supportsuite-3.0-swsoft-plugin-1.0.0-070410.tgz * mysql++-1.7.19-8.sw.i586.rpm * xerces-c-2.5.0-6.sw.i586.rpm * boost-1.32.0-3.i386.rpm * libssh2-0.14-2.sw.i586.rpm * swagent-2.6.1-124.swsoft.i386.rpm * mysql-3.23.58-4.i386.rpm * mysql-server-3.23.58-4.i386.rpm * perl-DBD-MySQL-2.9002-1.i386.rpm * perl-DBI-1.37-1.i386.rpm * aspell-0.50.3-16.i386.rpm * aspell-en-0.51-6.i386.rpm * php-4.3.4-1.4.fc1.sw.i586.rpm * php-domxml-4.3.4-1.4.fc1.sw.i586.rpm * php-mysql-4.3.4-1.4.fc1.sw.i586.rpm * php-ssh2-4.3.4-1.4.fc1.sw.i586.rpm * libidn-0.5.6-1.i386.rpm * httpd-2.0.46-25.ent.i386.rpm * mod_ssl-2.0.46-25.ent.i386.rpm * sendmail-8.12.10-1.1.1.i386.rpm * libxslt-1.0.33-5.i386.rpm * curl-7.10.6-7.fc1.i386.rpm For Redhat Enterprise Linux 4: * expand-2.1.3-4.i586.rpm * expand-dist-repository-2.1.3-4.i586.rpm * expand-locale-base-en_US-2.1.3-070410.noarch.rpm * expand-selinux-support-1.17.30-2.126-2.1.3-4.noarch.rpm * expand-selinux-support-1.17.30-2.19-2.1.3-4.noarch.rpm * expand-selinux-support-1.23.16-6-2.1.3-4.noarch.rpm * expand-selinux-support-1.27.1-2.28-2.1.3-4.noarch.rpm * cerberus-helpdesk-3.0-swsoft-plugin-1.0.0-070410.tgz * kayako-supportsuite-3.0-swsoft-plugin-1.0.0-070410.tgz * mysql++-1.7.19-8.sw.i586.rpm * xerces-c-2.5.0-6.sw.i586.rpm * boost-1.32.0-3.i386.rpm * libssh2-0.14-2.sw.i586.rpm * swagent-2.6.1-124.swsoft.i386.rpm * mysql-3.23.58-4.i386.rpm * mysql-server-3.23.58-4.i386.rpm * perl-DBD-MySQL-2.9002-1.i386.rpm * perl-DBI-1.37-1.i386.rpm * aspell-0.50.3-16.i386.rpm * aspell-en-0.51-6.i386.rpm * php-4.3.4-1.4.fc1.sw.i586.rpm * php-domxml-4.3.4-1.4.fc1.sw.i586.rpm * php-mysql-4.3.4-1.4.fc1.sw.i586.rpm * php-ssh2-4.3.4-1.4.fc1.sw.i586.rpm * libidn-0.5.6-1.i386.rpm * httpd-2.0.46-25.ent.i386.rpm * mod_ssl-2.0.46-25.ent.i386.rpm * sendmail-8.12.10-1.1.1.i386.rpm * libxslt-1.0.33-5.i386.rpm * curl-7.10.6-7.fc1.i386.rpm For installation on top of Plesk 8.1: * expand-dist-repository-2.1.3-4.i586.rpm * expand-locale-base-en_US-2.1.3-070410.noarch.rpm * expand-selinux-support-1.17.30-2.126-2.1.3-4.noarch.rpm * expand-selinux-support-1.17.30-2.19-2.1.3-4.noarch.rpm * expand-selinux-support-1.23.16-6-2.1.3-4.noarch.rpm * expand-selinux-support-1.27.1-2.28-2.1.3-4.noarch.rpm * cerberus-helpdesk-3.0-swsoft-plugin-1.0.0-070410.tgz * kayako-supportsuite-3.0-swsoft-plugin-1.0.0-070410.tgz * mysql++-1.7.19-8.sw.i586.rpm * xerces-c-2.5.0-6.sw.i586.rpm * boost-1.32.0-3.i386.rpm * libssh2-0.14-2.sw.i586.rpm * compat-libstdc++-8-3.3.4.2.i386.rpm * openssl097a-0.9.7a-3.i386.rpm * mysqlclient10-3.23.58-4.RHEL4.1.i386.rpm * mysqlclient10-3.23.58-6.i386.rpm * libidn-0.5.6-1.i386.rpm To install Plesk Expand, follow these instructions: 1. Log in as 'root' to your system. 2. Decompress an appropriate Plesk Expand archive: # tar xf expand_2_1_3-4*.tar 3. Install the extracted RPM packages: # cd expand_2_1_3-4* # rpm -Uhv *.rpm NOTE: After the Plesk Expand package is installed, you will be notified of your login details for the Plesk Expand control panel (URL, login and password). The message of the following kind will appear: ***************************************************************** * Congratulations! You have just installed Plesk Expand v.2.1.3 * You can access the system at https://expandhost.domain:8442 * Use 'root@expandhost.domain' as e-mail and * 'setup' as password to connect to the Plesk Expand frontend. * You can change this login data after logging into the frontend. ***************************************************************** C. Upgrade Procedure The upgrade procedure is rather straightforward. 1. Log in as 'root' to your system. 2. Decompress an appropriate Plesk Expand archive: # tar xf expand_2_1_3-4*.tar 3. Upgrade Plesk Expand using the extracted RPM packages: # rpm -Uvh expand-2.1.3*.rpm expand-dist-repository*.rpm expand-locale-base-en_US-2.1.3*.noarch.rpm NOTE: After the Plesk Expand package is upgraded, the message of the folllowing kind appears: ************************************************************************* * Congratulations! You have just upgraded your Plesk Expand to v.2.1.3 ************************************************************************* D. Deinstallation Procedure To deinstall Plesk Expand, issue the following command (being logged in as 'root'): # rpm -e expand expand-dist-repository expand-locale-base-en_US This will erase the Plesk Expand installation files from the /usr/local/expand directory and drop the 'expand' MySQL database. However, the /usr/local/expand directory will not be erased and the following files will be left for post-mortem reviews: * License files * Config files * Log files Upon the installation, all configuration files being patched by Plesk Expand will be pre-saved as '.exp_bak'. However, these files will NOT be reverted to their previous copies upon deinstallation. PSA API RPC Installation Instructions ==================================== Installation on a Plesk Server with Linux OS -------------------------------------------- A. Software Requirements The PSA API RPC package (psa-api-rpc) is included in the Plesk for Linux distribution as an optional package and is located in the opt/api directory. The following software is required to be installed prior to the installation of PSA API RPC: - Plesk 7.5.3 (or higher) for Linux B. Installation/Upgrade Procedure To install/upgrade PSA API RPC, issue the following shell commands (being logged in as 'root'): # rpm -Uvh psa-api-rpc* psa-agent* You can find these packages in the opt/api directory of your Plesk distribution. C. Deinstallation Procedure To uninstall PSA API RPC, use the following command (again, under the 'root' account): # rpm -e psa-agent psa-api-rpc Installation on a Plesk Server with FreeBSD 4.9/5.3 OS ------------------------------------------------------- PSA API RPC is included in the base distribution of Plesk for FreeBSD. No additional steps are required. Installation on a Plesk Server with Microsoft Windows OS --------------------------------------------------------- PSA API RPC is included in the base distribution of Plesk for Windows. Choose to install it when installing a Plesk server. Installation on a Plesk Server with Debian 3.1 OS -------------------------------------------------- # dpkg -i psa-api-rpc* You can find these packages in the opt/api directory of your Plesk distribution. Or you can add Plesk Debian repository to your sources.list file and install PSA API RPC using apt-get: # apt-get update # apt-get install psa-api-rpc License Installation ==================== A purchased license key may be installed through the Plesk Expand control panel or manually. To install a license key manually, follow the instructions below: 1. Copy the key file to /usr/local/expand/etc/expand.key if the license is of the BASE type (look into the license key file to check this out) 2. restart Plesk Expand Task Manager using the following command (being logged in as 'root' or 'apache'): # /etc/init.d/expandtm restart Centralized DNS ================ You may skip this step if you are not going to provide the Centralized DNS service. But if you choose to provide it later, you need to go back and complete this step. The centralized DNS software can be installed on one machine with Plesk Expand, but cannot be installed on one machine with Plesk (or with a Centralized Mail server). The Centralized DNS feature allows to process all DNS requests from the outside by a pool of dedicated DNS servers. Currently, the Centralized DNS server is available for the following OSes: * Redhat Enterprise Linux 3 * Redhat Enterprise Linux 4 * Fedore Core 2 * Fedore Core 3 * Fedora Core 4 * CentOS 3.x * CentOS 4.x It is possible (but not guaranteed) that it will also run on another Linux platform. Proven support of more OSes will be provided in future versions of Plesk Expand. Requirements: 1. Make sure that bind 9.2.1 or higher is installed on the host that you are going to make a dedicated DNS server. 2. Make sure that bind is running properly (see item 4.1 of the list below). Now you can go to the Plesk Expand Control Panel and register a Centralized DNS server in Plesk Expand. The DNS controller software is required to manage your DNS server, so it will be installed on your server automatically (unless you decline this option). The DNS controller software can also be installed manually. To install it, follow these steps: 1. Prepare a Unix server (see supported OSes above) with bind 9.2.1 (or higher) installed. 2. Go to your Plesk Expand distribution and upload the following files to your server: * dnscontroller/dnscontroller-2.0.0-*.i586.rpm 3. Now log in to your server and install the packages uploaded: # rpm -Uhv dnscontroller/dnscontroller-2.0.0-*.i586.rpm 4. After the installation is complete, ensure that dnscontroller is configured properly. 4.1. Check that your bind installation works properly, try # /etc/init.d/named status # /etc/init.d/named stop # /etc/init.d/named start # /etc/init.d/named restart All these commands must succeed. 4.2. Check if your bind installation is running in a 'chroot' mode or not. Typically, it is not, unless you (or some software) have changed this option. If you do not know how to check your bind configuration, you can follow these instructions: 4.2.1 start the bind server (if it is not started yet) # /etc/init.d/named start 4.2.2 look at its options: # ps -ax | grep named 31200 ? S 0:30 /usr/sbin/named -u named -n1 -c /etc/named.conf -u named -t /var/named/run-root If you found a '-t' option, then the parameter following it is a chroot directory and your bind server is running in a ‘chroot’ mode. 4.3. If you found that your bind server is running in the 'chroot' mode, then you need to open the dnscontroller.conf file: # vim /usr/local/dnscontroller/conf/dnscontroller.conf and change line #chroot_dir = /var/named/run-root to chroot_dir = /your/chroot/dir 4.4. Since dnscontroller-2.0.0 there is a /usr/local/dnscontroller/conf/hosts.allow file which is used to restrict unauthorized access to your DNS server. DNS controller software won't accept any connections from hosts which IPs are not included to hosts.allow file. Thus you need to open it and add IP of your Plesk Expand host to this file (each host should be on separate line, line break is a delimiter). 4.5. If you prefer UNIX Timestamp SOA serial to YYYYMMDDnn format, change "serial_type" parameter in /usr/local/dnscontroller/dnscontroller.conf to "unix_timestamp" value: serial_type = unix_timestamp It is recommended to choose SOA serial type BEFORE Central DNS server keeps any DNS zones. If you change SOA serial format having any DNZ zones already configured in DNSController,then you will have problems with updating your DNS zone content by outer DNS servers because new serial is lower than previous one (being compared as positive integer numbers). Note: Exact versions of packages may differ from one release to another. Centralized Mail ================= You may skip this step if you are not going to provide the Centralized Mail service. But if you choose to provide it later, you need to go back and complete this step prior to registering the Centralized Mail server in Plesk Expand. The Centralized Mail server is configured on the basis of a regular Plesk server. Just like a regular Plesk server, it can be installed either standalone (on a separate host) or on one host with Plesk Expand. You can use the following Plesk versions (among versions available on the moment of the release notes publication) as Central Mail server: * Plesk 8.1.x for Linux/Unix * Plesk 8.1.x for Windows You see, both Linux/Unix- and Windows-based hosts can be used as Central Mail server. Any Central Mail server (Linux/Unix- and Windows-based) can serve for any Plesk server (Linux/Unix- and Windows-based). But there are some limitations, see them below: ATTENTION: You CAN NOT migrate mail (mailing lists and their content, mail boxes and their content, mail groups, autoresponders, etc) from Plesk for Windows server to Central Mail server. You also can not migrate mail to Windows-based Central Mail server. Only clean Plesk servers can be connected to Central Mail servers in these cases. Otherwise, Plesk users will loose their mail. See the Plesk Installation Guide for instructions on how to install the Centralized Mail server (the installation of PSA API RPC is a mandatory step). Then return back to follow the instructions below: 1) Complete the Plesk postinstallation process. 2) Make sure that you have added a SHARED default IP address to the Centralized Mail server IP Pool. 3) Make sure that you have removed all clients (including the one named 'My Domains') from the Centralized Mail server. 4) Install the proper Plesk license key on the Centralized Mail server. It should allow to create as many domains as this server is going to serve. 5) It is highly recommended to switch the Cenrtalized mail server to using full POP3/IMAP mail accounts names. Login to the Centralized mail server, go to "Server > Mail" page and enable the "Only use of full POP3/IMAP mail accounts names is allowed" option. Unless this option is enabled, there might be a situation when one mail user can read mail of another mail user (if they have the same password). When this feature is activated (a Plesk server is assigned to the Centralized Mail Server), the 'Remote Mail' button appears in the Plesk Control Panel of each domain user residing on the assigned Plesk server. By clicking this button in the Plesk control panel, users can open a special page where they can manage their remote mail settings. Migrations ========== After a migration is finished, source objects are not deleted. You need to check that the migration is done properly and then delete the objects manually. What's new in Plesk Expand 2.1.3 ===================================== Plesk Expand 2.1.3 includes the following fixes: [-] Disabled automatic removing of migrated account. Provider shall manually check that migration was succesfull and then remove source account [+] Upgraded SSH tranport to resolve rare error with migrating mail content Legend: [+] new feature [-] bug fixed or removed [*] bug fixed and improvements made Known Problems and Limitations ============================== - [B92045] If you have Plesk and Plesk Expand installed together in one Virtuozzo VE, then you need to change /etc/hosts file. Open it and find a line like that: 127.0.0.1 your-host.com your-host localhost localhost.localdomain replace it with the following line: 127.0.0.1 localhost localhost.localdomain Otherwise you may experience problems when using CDNS feature. - Make sure you have properly configured DNS zone for all you hosts including Plesk servers, Central Mail servers, Central DNS servers, Plesk Expand host. Plesk Expand might use DNS lookup to resolve hostname to IP, and reverse lookup to resolve IP to hostname. So if the PTR record for Central Mail server IP points to wrong name - you will experience problems with "Remote Mail" button in Plesk. - It is impossible to use one Plesk host as Central Mail and as usual Plesk server, but if you did this before upgrade tp Plesk Expand 2.0, you will be able to continue such usage (issue #91532). - Only 'root' users and those belonging to the 'expand' group are allowed to execute Expand command-line tools. The reason for this is that the Plesk Expand configuration file can be accessed only by the mentioned above users. - After upgrade from version <= 1.0.1-10, the 'validity period' limit in all client and domain templates will be changed to 'unlimited'. - It is recommended that you disable the 'offline management' option for Plesk servers running in Virtuozzo VPS. Otherwise, you might have problems using features like 'Login to Plesk server', 'Centralized Mail', etc. - Do not install psa-rsession-*.rpm. The psa-api-rpc utility already has psa-rsession built-in. Forced installation of psa-rsession over psa-api-rpc will cause problems, as psa-rsession-*.rpm conflicts with psa-api-rpc-7.5.4-*.rpm. - Centralized mail: remote mail management is availble only if a SHARED IP address is used as a default one for Plesk Mail server. - Centralized mail: a custom logo and the corresponding URL (if any) will not be displayed when Plesk users manage a remote mail service. - Centralized DNS: manual installation of Bind is required in order to use a Centralized DNS server. - During the assignment of a Plesk server to a Centralized Mail server, Plesk Expand will offer you to migrate the existing mail content (content of user mailboxes and mailing list archives) from the Plesk server to a Centralized Mail server. Be careful, as the migration may take considerable time (the migration of a server with about thousand domains hosted on it may take a few days(!)). Make sure that you have enough diskspace in the /tmp folder on your Plesk server, Plesk Expand server and Centralized Mail server. - [B97028] When using PHP CLI in standalone Plesk Expand installation, you can not use "sha-bang" (#!) in your PHP scripts. Your scripts should have '<' character as a 1st symbol. So the sample below will not work #!/usr/bin/php If you definitely need to use "sha-bang" marker, then install Plesk Expand over Plesk. You do not need to buy any license for Plesk or configure it, just install a Plesk and then install Plesk Expand over it. Contact Information =================== SWsoft Headquarters 13800 Coppermine Drive Suite 112 Herndon, VA 20171 USA Phone: +1.703.815.5670, Fax: +1.703.815.5675 World Wide Web: http://www.swsoft.com E-mail: For billing information, email accounting@swsoft.com For purchasing or partnering information, email sales@swsoft.com For technical support, use our Online Support Form. To report problems with Plesk software, email bugreport@swsoft.com For information on career opportunities with SWsoft, email careers@swsoft.com For press contact information, email press@swsoft.com For general product information, email info@swsoft.com Copyright 2004-2007 SWsoft. All rights reserved.