Plesk v8.2.1 build82070924.15 for FreeBSD-6.1 i386 Release Notes
Copyright (c) 2007 by SWsoft
Prior to installing or upgrading Plesk, be sure to backup your server.
Refer to the Plesk Installation Guide available at
http://download1.swsoft.com/Plesk/Plesk8.2/Doc//plesk-8.2-unix-installation-guide.pdf
to obtain instructions on installing and upgrading Plesk.
Other documentation on Plesk 8.2.1 is available at
http://www.swsoft.com/en/products/plesk/docs
Plesk 8.2.1 FAQ is available at
http://faq.swsoft.com
To install Plesk software on a server,
- Download the Auto-installer utility that suits your operating system from
http://www.swsoft.com/en/download/plesk82
and save it on your server's hard drive.
Note: to avoid any issues please use the latest version of Auto-installer.
- Change your working directory to the directory where the Auto-installer utility resides, for instance:
# cd /root/plesk
- Set the execution permission for Auto-installer:
# chmod +x plesk_auto_installer_file_name
- Run the Auto-installer:
# ./plesk_auto_installer_file_name
- Follow the instructions presented on the screen to complete the installation.
- When the installation is finished, Plesk will start automatically. Now, to complete the initial configuration,
log in to the Plesk control panel running on your host at https://machine.domain.name:8443/ or https://IP-address:8443/.
Use the username "admin" and password "setup" (both are case sensitive). For security reasons, be sure to change the password upon initial login.
Notes on upgrading:
After upgrading to Plesk 8.2, all custom (third-party) skins become unregistered.
If you wish to restore the custom skins that you used before the upgrade, run the command "/usr/local/psa/tmp/restore-custom-skins.sh",
where /usr/local/psa is your Plesk installation directory (for example, /usr/local/psa.) You can remove this file after restoring your skins.
To update or upgrade your Plesk software from the control panel:
- Log in to Plesk as administrator, and click the Server shortcut in the left-side navigation pane. The Server Administration screen opens.
- Click the Updater icon in the Services group. The control panel connects to the Plesk Update server,
retrieves information on the available releases, then analyses the components installed in your system,
and displays the lists of available releases and component updates. For each Plesk version released a brief description
of available operations is displayed.
Note: If you want to update/upgrade from a locally stored Plesk distribution or Plesk update server mirror inside your network,
click Preferences, select the "Network storage" source type, specify the URL and click OK.
ATTENTION: To upgrade to Plesk 8.2.1 from versions prior 8.1.0 you need to use upgrade through
Auto-installer Console Utility because previous versions of Plesk uses
an old version of Auto-installer which don't know about new distribution(via FreeBSD ports).
- Select the Plesk version that you want to update, or upgrade to. A list of available components appears.
- Select the checkboxes corresponding to the components you wish to install and click Install. A confirmation page appears.
- Specify your e-mail address. You will be sent a notice by e-mail once update is completed. To confirm installation of the selected components,
select the checkbox and click OK. The components/updates you selected will be downloaded and automatically installed in the background mode.
To update or upgrade your Plesk software by means of the Auto-installer utility:
- You need to obtain the Auto-installer utility version 3.2.1 or later. You can download it from
http://download1.swsoft.com/en/download/plesk82.
- Run the 'psa_autoinstaller' binary file.
- The Auto-installer will detect your existing installation of Plesk and ask if you want to upgrade it.
Read the Welcome page and press Enter.
- Specify the source of Plesk distribution package. You can choose to upgrade from a local media, the official Plesk update server,
or another Internet site. Once you have selected the source, press Enter.
- Specify the proxy server settings, if applicable, press Enter to continue.
- Select the product version that you wish to upgrade to: type the number corresponding to the product name of
your choice. Press Enter to continue.
- Auto-installer will list all components available for installation.
See the related article on
known problems with installation/upgrade of Plesk for FreeBSD.
- Auto-installer will estimate the amount of disk space required for installation of Plesk and will show you the amount of free disk space.
If you have enough free disk space, press Enter.
- Auto-installer will show the information about the packages that will be installed.
Press Enter to continue.
- Select the components that you wish to install or upgrade, then press Enter to continue.
Once the required components are downloaded, your Plesk software will be upgraded.
Note: When upgrading Plesk from Ples version prior to 8.1.0 to 8.2 using Auto-installer, be sure to upgrade the Tomcat component, otherwise,
Java applications will not be supported on your server.
Before installing Plesk 8.2.1, read the
Known problem articles.
- Log in as "root" and add the entry kern_securelevel_enable="NO" to file /etc/rc.conf, otherwise installation may fail.
- Download the tar.gz archive with distfiles and package psa-ports-8.2.1.tbz
from
http://download1.swsoft.com/en/download/plesk82
- Unpack the archive and place Plesk distfiles into /usr/ports/distfiles
- Install the package onto the system by running the command:
pkg_add psa-ports-8.2.1.tbz
,
This will install Plesk ports into
/usr/ports/swsoft
- If you are upgrading Plesk, stop its services by running the command:
/usr/local/etc/rc.d/psa.sh stop
If you have Plesk 8.0.1 or earlier version installed you should use the command:
/usr/local/psa/rc.d/psa.sh stop
- Then run the command:
cd /usr/ports/swsoft
- To select Plesk components you want to install you need to run the command:
make config
- To install/upgrade Plesk run the command:
make install
When the installation is finished, Plesk will start automatically.
In order to complete the Plesk initial configuration, you need to log in to Plesk
on your host at https://machine.domain.name:8443/ or https://IP-Address:8443/
The default username is "admin" and the default password is "setup", both are case sensitive.
For security reasons, this password should be changed upon initial login.
NOTES:
Plesk enables PHP safe_mode during installation (the directive 'safe_mode-On'
in php.ini). However, you can disable the safe_mode for individual domains if required.
To do this, you should use the vhost.conf (vhost_ssl.conf) features.
See
http://download1.swsoft.com/Plesk/Plesk8.2/Doc//plesk-8.2-unix-administrators-guide.pdf
for details.
In order to use multiple interface languages in the Webmail application, you may need to run the 'dpkg-reconfigure locales' command and choose the locales to install.
Plesk cannot enable user quotas on XFS partition during installation
because such operation requires remount of XFS partition. In order to enable
hard disk quotas on XFS partition you should manually remount it with usrquota
option (additional information can be found on 'quotaon' man page).
For managing the SiteBuilder system through Plesk, the 'remote_admin' user account with administrator's privileges is created in the SiteBuilder.
To ensure the proper work of the SiteBuilder Remote Administration module, you should not remove or block this user account.
however, if you do not use the SiteBuilder Remote Administration Module, you can remove this user account.
To make operating the SiteBuilder API (remote_admin) more secure, the
/usr/local/sitebuilder/remote_admin directory is password protected, and the following default user name and password
are stored in the .htpasswd file: radmin/sbradmin. For security reasons you must change the default password.
To do this, run the command 'htpasswd /usr/local/sitebuilder/remote_admin/.htpasswd radmin', and then enter the new password and confirm it.
[*] Security improvements and bugfixes
[*] Upgrade procedure improvements
[-] Several autoinstller utility bugs with packages checking and mirroring have been resolved
[-] Several selinux configuration issues have been resolved.
[-] Several Backup and Migration bugs have been fixed.
[-] Issue with mail stucked in qmail-queue is resolved.
[-] Issue with sending notifications about domain expiration by statistics utility is resolved.
[-] Issue with permanent Spamassassin restarting by Watchdog is resolved.
[-] Problem with incorrect message("Management of parent node is forbidden") after domain deletion is resolved.
[-] Issue with mailling lists with dot symbols is resolved
[-] Issue with php safe mode management by client is resolved.
[-] Issue with incorrect php dependences of 'coppermine' and 'gallary' packages is resolved.
[-] Several issues with MySQL packages from mysql.com compatibility have been resolved.
[-] Issue with mysqldump.sh utility is resolved.
- Client backup files are not included into Client's disk space.
- If you want to upgrade to Plesk 8.2.1 on FreeBSD platforms from Plesk version early than 8.1, during upgrade, you should select all components suggested by auto-installer.
Otherwise, the upgrade may fail.
- If You want to use tomcat, you must fetch the distribution of diablo-jdk manually because of licensing restrictions. To fetch distribution you should run
# cd /usr/ports/java/diablo-jdk15
# make fetch
- ATTENTION: during upgrade from Plesk versions prior 8.1.0 on FreeBSD systems using Plesk shell self-extracting archives, the Plesk Control Panel and all
its services are stopped for a sufficient amount of time because some of system ports required by dependencies might be built from sources.
In case of the upgrade necessity we recommend to set up a clean server with Plesk 8.2.1 and migrate all the domains to it using Plesk Migration Manager or Backup and Restore utilities to minimize the downtime.
- If you upgrade Apache through the /usr/ports system, using the FORCE_PKG_REGISTER=yes command or compiling from sources,
you should reinstall the suexec file from Plesk distribution using the command /usr/local/etc/rc.d/psa-suexec.sh restart,
otherwise it will be done automatically after the first restart of Plesk (/usr/local/etc/rc.d/psa.sh restart).
- Plesk will not work properly with AppArmor enabled. You can disable it through "/etc/init.d/boot.apparmor stop" commend. And prevent it's starting after reboot with "chkconfig --del boot.apparmor command"
- Applications written in Ruby language may not work properly on FreeBSD systems because of improperly set access permissions.
If you are going to use applications in Ruby, go to the directory where the application is placed, and run the command 'chown -R :psacln'.
- FrontPage Server Extensions are no longer shipped with Plesk. Therefore, after upgrading to Plesk 8.2, you will need to obtain and install
FrontPage Server Extensions separately.
- If you are going to install Plesk on Debian systems, make sure that openbsd-inetd package is not installed on your system. Otherwise, the installation may fail.
- Watchdog 2.0 module for Plesk does not monitor disk space usage when Plesk is installed inside Virtuozzo VPS (in Virtuozzo versions below 3.0.0)
- Watchdog 2.0 module for Plesk does not calculate the number of files on some operating systems.
- Creation utilities (aka API CLI) do not use the .sh name suffix now.
For example, the utility '/usr/local/psa/bin/domain.sh' is now named '/usr/local/psa/bin/domain'.
This can cause problems in functioning of third-party products that use these scripts.
Note: Old syntax is still supported, but the compatibilty wrappers will be removed in the next major release.
- SSH Terminal may not work properly, failing to log in, when trying to connect to Plesk. For the proper work,
modify the SSH Terminal configuration file /etc/ssh/sshd_config as follows:
- In the configuration file, find the strings:
# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication no
#PermitEmptyPasswords no".
- Remark the string "PasswordAuthentication no" by adding the # sign to the beginning of the string or change the string
"PasswordAuthentication no" to "PasswordAuthentication yes".
- Save the file.
- Plesk does not restrict access to the netinfo database for users that are logged in to the chroot account.
Thus, the chroot users have access to the general system information including the list of all users and domains existing on the server.
Be aware of the issue when you create system accounts on the server.
- Some site applications (siteapps) dependent on remote MySQL database server will not work with the MySQL server version 4 or later.
Make sure that a compatible version of MySQL server is installed before installing siteapps.
- It is best to host non-Plesk databases on remote hosts other than the Plesk-managed server to avoid performance problems caused by MySQL
workload surges. If you must host the MySQL databases on the Plesk-managed server, configure firewall and the MySQL DBMS and database
access policies to minimize potential adverse effects of malicious attacks on the Plesk-managed server performance. If you plan to use the
"Remote Database Hosting" feature of Plesk, we recommend using a dedicated server for database hosting.
- Site preview will not work for websites that have the webuser@domain.com access format enabled.
(Domains -> domain.tld -> Web users -> Preferences -> Enable webuser@domain.com)
----
Legend:
[+] new feature
[-] bug fixed or removed
[*] bug fixed and improvement made
SWsoft Headquarters
13755 Sunrise Valley Drive
Suite 600
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 information about becoming a Partner, email partners@swsoft.com
For information on translating Plesk into your language, email i18n@swsoft.com
For general product information, email info@swsoft.com
Copyright 1999 - 2007 SWsoft. All rights reserved.