UKC

How to Install ImageMagick on Plesk

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.

Problems forwarding to Gmail / AOL / Other email address

Re: Forwarded emails not arriving, no bounce message

Many free email services such as Gmail, AOL, Hotmail (and ISPs) are constantly tightening up their spam systems and are being increasingly particular about which emails they allow in to their system.

If you find that forwarding email to one of these addresses is simply ‘disappearing’, ie. no bounce message then you can be safe in assuming that your email alias (address) is temporarily blocked from the target mail system.

Why does this happen?

Let’s assume you are doing all the right things. ie Your SPF record is correctly set, your MX records are correct.

When forwarding emails from your parked domain name, you are also forwarding SPAM to your destination email address. If you send enough SPAM messages then you will block your own alias. Often the block is only in place for a limited time, for example 24 hours. Then it will start working again and once you have forwarded enough SPAM the block is re-applied. Does this sound like the problem you are experiencing?

What can you do?

  • If you are receiving SPAM to your forwarding alias then try a new alias. This will be a suitable solution until you again start receiving SPAM to this new alias.
  • Try to keep your alias names as unexposed as possible to reduce the SPAM sent to them.
  • Create a Mailbox for your alias. The Mailbox will receive 100% of emails sent to it.
  • Do not use forwarding aliases for important or mission critical applications, use a Mailbox.
If you require any  further assistance or advice do not hesitate to contact support.
External resources:

Plesk Backup Manager Not Working – Missing Tables BackupsSettings, BackupsScheduled, BackupsRunning

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!

Parked Domain Services – Infrastructure Upgrades (18th/19th August 2012)

We are shortly commencing the upgrades of all hardware and infrastructure related to the parked domain name services. This will improve security, performance and reliability of all related domain services including:

  • DNS Management
  • Email forwarding
  • Web Forwarding
  • Parked Mailboxes
  • Domain Homepages

These upgrades only concern parked domain name customers and not any hosting accounts will be affected. If your domain name is using name servers other than ns.microlite1.com then this upgrade will not  concern any of your services.

The hardware will be installed and tested by 1st August and migration testing will begin 7th August. We anticipate final completion of the migration to commence weekend 18th/19th August. The entire process will be complete by midnight on Sunday 19th August.

We will disable the Domain Control Panel at 0300 Saturday 18th and it will be re-enabled 0300 Monday 20th. During this period there may be intermittent outages or propagation issues which we endeavour to keep to a minimum. Our priority will be to have the services 100% active by 0300 Monday 20th August.

For information purposes (you do not need to do anything) the parked domain name servers host names will remain the same however the IP addresses will change as follows:

  • ns.microlite1.com -> currently 66.98.136.44 -> changes to 109.75.164.106
  • ns2.microlite1.com -> currently 66.98.137.170 -> changes to 109.75.164.107

This will mean that there will be a propagation delay between changes however this should cause minimal disruption as both sets of IP addresses will remain active during this period.

Thank you for your patience and support during this time. If you have any questions do not hesitate to contact us.