Parallels Plesk Panel Versions

The currently supported Parallels Plesk Panel versions are:

• Parallels Plesk Panel 11
• Parallels Plesk Panel 10
• Parallels Plesk Panel 9

Lifecycle Policy:

• A major version is defined as any change in the first number of the version number. For example, Plesk 9 and Plesk 10 are different major versions whereas Plesk 10.2 and 10.3 are not different major versions.
• Parallels will always provide software patches and accept technical support requests for the latest Parallels Plesk Panel major version and the immediately preceding major version.
• Each major version will be fully supported for at least a period of four (4) years after release.
  • Extended Support: After this 4 year period, the product will no longer be available for new purchases and will continue to receive patches only for critical issues. This will last for a period of six (6) months.
  • End-of-Life: Once the Extended Support period is over, the product will no longer receive further development and technical support requests will no longer be accepted.
• In order to ensure stable operation, it is required to be on the latest update / patch within a major version. For example, this means the latest 9.5.x version in the Plesk 9 series, the latest 10.4.x in the Plesk 10 series, or the latest 11.0.x in the Plesk 11 series.
• Support for a particular instance is also dependent on using a currently supported operating system. This policy is described in the relevant section below.
• Even for unsupported instances, Parallels will continue to accept technical support requests that are related to updating to a supported version or environment.

The below tables describe when specific versions of Parallels Plesk Panel will enter the Extended Support phase and when patches / support will no longer be available for them. If affected by one of the below dates, customers are encouraged to upgrade to a supported Parallels Plesk Panel version.

Version Lifecycle Dates:

Re: ImageMagick on a Plesk Server

ImageMagick is not installed on your Plesk server by default. However, the installation is quite simple using the yum repositories and packages.

# yum install gcc
# yum install ImageMagick
# yum install ImageMagick-devel
# yum install php-pear
# yum install php-devel
# pecl install imagick
# echo "extension=imagick.so" > /etc/php.d/imagick.ini
# service httpd restart

To test it is working, try the following:

# php -i | grep imagick
imagick
imagick module => enabled
imagick module version => 3.0.1
imagick classes => Imagick, ImagickDraw, ImagickPixel, ImagickPixelIterator
imagick.locale_fix => 0 => 0
imagick.progress_monitor => 0 => 0

This output confirms that the imagick.so module is operating and active. That completes this ImageMagick installation tutorial, we hope you found it useful.

Re: Backup Manager Not Working in Plesk

If you get the following message when trying to run a backup in Plesk using the Backup Manager then it is likely that a previous upgrade or installation of the Backup Manager did not complete and so there will be some missing tables.

0: common_func.php3:206
db_query(string 'select `value` from `BackupsSettings` WHERE `param` = 'backup_ftp_settinghost' AND `id` = 6 AND `type` = 'domain'')
1: common_func.php3:253
db_query_ex(string 'select `value` from `BackupsSettings` WHERE `param` = '?(paramName)' AND `id` = ?(objectId) AND `type` = '?(objectType)'', array)
2: BackupFTPRepositorySettings.php:205
BackupFTPRepositorySettings->getRepositorySettingsValue(string 'backup_ftp_settinghost')
3: BackupFTPRepositorySettings.php:43
BackupFTPRepositorySettings->init()
4: BackupFTPRepositorySettings.php:25
BackupFTPRepositorySettings->__construct()
5: BackupFTPRepositorySettings.php:283
BackupFTPRepositorySettingsDomain->__construct(integer '6')
6: client.domain.backup.php:8
plesk__client__domain__backup->getBackupFTPRepositorySettings()
7: backup.ftp-repository.php:35
__backup__ftp_repository->getDumpsStorageCredentials()
8: backup.ftp-repository.php:29
__backup__ftp_repository->getRepositoryList()
9: backup.abstract-repository.php:44
__backup__abstract_repository->accessItemsList(string 'GET', NULL null)
10: backup.abstract-repository.php:26
__backup__abstract_repository->accessItem(string 'GET', NULL null)
11: UIPointer.php:596
UIPointer->access(string 'GET')
12: plesk.php:38

The Plesk Backup Manager needs the following tables in the PSA database:

• BackupsSettings
• BackupsScheduled
• BackupsRunning

Execute the following SQL in phpMyAdmin to create the missing tables:

CREATE TABLE IF NOT EXISTS `BackupsSettings` (
`id` int(10) unsigned default NULL,
`type` enum('domain','client','server') NOT NULL default 'domain',
`param` varchar(255) NOT NULL default '',
`value` varchar(255) character set utf8 default NULL,
UNIQUE KEY `index1` (`id`,`type`,`param`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

CREATE TABLE IF NOT EXISTS `BackupsScheduled` (
`id` int(10) unsigned NOT NULL auto_increment,
`obj_id` int(10) unsigned NOT NULL,
`obj_type` enum('server','reseller','client','domain') NOT NULL,
`repository` enum('local','ftp') NOT NULL default 'local',
`last` datetime default NULL,
`period` int(10) unsigned NOT NULL,
`active` enum('true','false') NOT NULL,
`processed` enum('true','false') NOT NULL,
`rotation` int(11) NOT NULL default '0',
`prefix` varchar(255) character set utf8 default NULL,
`email` varchar(255) character set utf8 default NULL,
`split_size` int(10) unsigned NOT NULL default '0',
`suspend` enum('true','false') NOT NULL default 'false',
`with_content` enum('true','false') NOT NULL default 'true',
`backup_day` int(10) unsigned NOT NULL default '0',
`backup_time` time NOT NULL default '00:00:00',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=17 ;

CREATE TABLE IF NOT EXISTS `BackupsRunning` (
`sessionId` varbinary(250) NOT NULL,
`param` varchar(250) character set ascii NOT NULL,
`val` varbinary(255) default NULL,
PRIMARY KEY (`sessionId`,`param`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

This will resolve the problem, the Backup Manager will now work correctly!

To parse PHP code inside a .html file you will need to a create a .htaccess file in your document root directory /httpdocs and insert the following code:

RemoveHandler .html .htm
AddType application/x-httpd-php .php .htm .html

You will need to ensure that PHP is running as Apache, to check  this in Plesk you will need to login to your client account, select the domain name and go to Web hosting settings.

Re: validity period of domain, validity period is prolonged, extend the validity period

If you get this message then do not worry about the expiry of your domain name or hosting account. This message relates to the period you applied when you added the domain name to your Plesk panel.

The messages usually contain:

• validity period of domain
• validity period is prolonged
• extend the validity period

This problem occurs if you missed out Step 12 in “How to add a domain to multi-domain hosting“.

To resolve, simply log in to your Plesk control panel, select the appropriate domain name, go to Resource Usage and ensure that the “Expiration date” is set to “Never Expires“.

Re: Insufficient storage for Plesk  9.5.4 Migration Manager (even though there is)

If you are having problems using the Plesk Migration Manager, one of the first problems you need to solve is the insufficient space problem. There are many problems with the PMM but that’s another story, you’re probably here because you really need to get it working.

You may get a failed migration due to this issue, or a constant hang at 50% completion without any error.

Even though you get the opportunity to set a data dump location (default within /var) and you have likely carefully ensured that there is another psace storage on that device, what you don’t know is an intermediate storage space is also required in /usr/local/psa/PMM.

Luckily this problem is easily dealt with by creating a symbolic link for the PMM directory.

The examples below move the PMM directory to a secondary drive namely /backup.

1. Let’s create the new PMM directory on a drive with plenty of free space.

# mkdir /backup/PMM

2. Now we will copy the PMM directory and its contents to the new PMM directory whilst preserving the ownership and permissions.

# cp -Rp /usr/local/psa/PMM/* .

3. Set the current PMM directory aside

# mv /usr/local/psa/PMM /usr/local/psa/PMM.old

4. Now we create the symbolic link

# ln -s /backup/PMM /usr/local/psa/PMM

The PMM directory is now symbolically mapped to a drive with suffienct space for your migration to complete. You may need to abort any previous migrations and restart as often they do not restart once stopped due to an insufficient storage space problem.

See this entry on Parallels KB: http://forum.parallels.com/showthread.php?t=100327

Re: Upgrade Plesk 9.5.4, Install micro-updates Plesk 9.5.x

If you are still running Linux Plesk 9.5.4 you may think that because 9.5.4 is the latest (and last) 9.5.x version that there are no new patches or upgrades available. If so, you are dangerously wrong.

Parallels regularly release “Micro Updates” which resolve recently discovered vulnerabilities, and there are plenty of them. The latest update is 9.5.4 MU 18.

You can find which version you are running like this:

# cat /root/.autoinstaller/microupdates.xml

You can see here that “patch version=18″ which means micro updates up to  (MU) 18 are installed.

Upgrading to Plesk 9.5.4 and installing the Micro Updates

We recommend that you install any new micro updates as soon as possible, it takes only a few minutes and can be run from the command line:

/usr/local/psa/admin/sbin/autoinstaller –select-product-id plesk –select-release-current –reinstall-patch –install-component base

If you are not running Plesk 9.5.4, use the following command to upgrade to latest 9.5.4:

/usr/local/psa/admin/bin/autoinstaller –select-release-id=PLESK_9_5_4 –upgrade-installed-components –ignore-key-errors –notify-email=your@emailaddress.com

If you haven’t already, go to Parallels and subscribe for the panel update notifications:

http://kb.parallels.com/

For further information see Parallels KB Article http://kb.parallels.com/en/9294

Re: Can’t install Wordpres, Joomal or other Database Application

The error message “Database required (mysql, version >= 5.0) (not available, please check domain or client limits)” is usually returned when there are no spare databases left to install the application.

To resolve, try the following:

• 1) Within Plesk, Database, delete any unwanted databases to free up your allocation
• 2) Upgrade your Hosting account so that you have a greater database allocation

To import a MySQL database you can use phpMyAdmin which is available in your Plesk control panel.

1) Firstly, you will need  to create the database in Plesk that you would like to import the SQL file to.

- Video tutorial: How to create a database in Plesk

2) Open up phpMyAdmin inside Plesk

- Go to Databases

- Select the Database

- Go to Webadmin

3) Once you are in phpMyAdmin, Select the Database on the left hand bar.

4) Go to import

5) Click the ‘Choose’ button to browse the location of the text file

6) Click “Go” to import the SQL file

If you experience any problems, please log a ticket with our Help Desk.

Re: Upgrade features on Plesk to latest offering

The range of features on offer today may be more than when you purchased your account. There is no need to lose out. This is not a new customers only offer.

We are now offering more hosted domains on all accounts to new cutomers however if you are an existing customer, don’t worry – you can upgrade to the latest offering for free!

Here is what you need to do:

• Look at the Hosting page for your plan current feature list
• The multiple domain allowances have increased for all accounts
• The database allowances have in some cases been reduced
• Log a ticket with the Helpdesk asking for a “feature update”
• Include your clientXXXXX Plesk login within the ticket for a fast upgrade
• Your existing data will not be affected and will remain intact

If you provide the correct clientXXXXX ID and your domain name from the outset in your ticket, your upgrade may be completed within an hour. The ticket will be updated once the upgrade is complete.

Re: What to do with your new web hosting account

1. Login to your Plesk Control Panel to gain access to all the features and resources provided with your account.
2. Set up your first email address and start using email services with your domain
3. Start collecting web visitor statistics and monitor visitors activity around your site
4. Launch more sites with multi domain hosting to get the most from your web presence
5. Install and Connect FileZilla FTP to upload files to your personal web space
6. Install a Web Application such as WordPress and get a professional site online straight away

You are now well on the way to making the most of your new hosting account. For further information and advise search the knowledgebase or contact the Helpdesk.

Re: How to enable visitors stats collection in Plesk hosting

Your Plesk Hosting account now comes with 2 options for viewing detailed visitor and traffic statistics concerning your website.

1) AWStats – Get advanced graphical web, ftp or mail statistics
2) Webalizer – statistics for user agents (browsers) and referrers

Visitor statistics collection is not enabled by default. You need to enable this feature as follows:

Simply login to your Plesk Control Panel, select your domain name and click “Web Hosting Settings”, scroll down and select which statistics package you wish to use for this domain.

To be able to view your statistics directly from your domain name (eg. www.yourdomain.com/plesk-stat/webstat) ensure you have a tick in the box that says “(accessible via password protected directory ‘/plesk-stat/webstat/’ )”, this will allow external direct URL access via your FTP password.

Once enabled, your visitor stats will be compiled everyday at 0400 so do not expect to see anything straight away. Simply check the next day and your visitor stats and charts will be available.

For professional high level statistics and analysis we highly recommend using Google Analytics in your website code, you can set up a free account here:

http://www.google.co.uk/analytics

Re: Set up a cron job in Plesk, Plesk crontab, Create a PHP cron job in Plesk

Setting up a cron task or scheduled job within Plesk is a piece of cake – once you know how.

First, find your way in to the Plesk Control Panel and hit the “Scheduled Tasks” button, then “Schedule New Task”. The example below will show a working task executing a PHP file named cronjob.php located in /httpdocs (your document root) at 01:00 every morning of every day:

The form looks pretty straight forward however there are some points to note.

• If you want to run every hour, put an asterisk “*” in the Hour field
• If you want to run every day, put an asterisk “*” in the Day of Month field
• If you want to run every month, put an asterisk “*” in the Month field
• If you want to run everyday, put an asterisk “*” in the Day of Week field

If you have problems, check your asterisks are in the right places and that you cron PHP file is in the right location. Compare the schedule task dialogue boxes carefully and you won’t have any problems.

Trying to export a database but getting the error “No web page was found for the web address: “https://server.domain.com:8443/domains/databases/phpMyAdmin/export.php”

Given that error message, you’d be excused for thinking that the file export.php was missing or your pypMyAdmin installation was messed up – but you’d be wrong!

This error is not intuitive, the file export.php is actually there, the problem is this.

1. Your database is on the large side
2. Your php memory limit is set too low

To fix, simply increase your memory_limit as follows:

# vi /etc/php.ini

Find the line that says “memory limit = (some)mb”

Change the value to something considerably bigger, usually 512mb will do the trick.

For example:

memory_limit = 128M      ; Maximum amount of memory a script may consume

You will now be able to export your mysql database without further ado.

Some applications require open_basedir to be “loosened” a little, if you are installing an application such as ClickCart Pro then the open_basedir will need to be changed so that the installation can create the required sub directories and then complete.

Let’s assume your domain name is domain.com (no such luck, I know!)

# vi /var/www/vhosts/domain.com/vhost.conf

Add the following lines:

<Directory /var/www/vhosts/domain.com/httpdocs>
php_admin_value open_basedir “/var/www/vhosts/domain.com”
php_admin_flag safe_mode off
</Directory>

Now we need to rebuild the apache configuration:

# /usr/local/psa/admin/sbin/websrvmng -u –vhost-name=domain.com

Job done, your open_basdir setting has been moved up one level (from /httpdocs to /) within your domain name sub folder.