Warning: the CA certificate does not sign the certificate.

When installing an SSL certificate in Parallels Panel (Plesk) along with an intermediate certificate you receive the error message

Warning: the CA certificate does not sign the certificate.

Generally it is safe to ignore this error. It is just Parallels Panel not being able to follow the complete CA root path. However, I have found that if you append the intermediate certificate to the CA certificate (instead of putting it in the intermediate certificate box), you do not get the error.

Here is the intermediate and root DomainSSL cert for globalsign:

—–BEGIN CERTIFICATE—–
MIIFQjCCBCqgAwIBAgISESFxABpzduLKxXYRi0KcPsx3MA0GCSqGSIb3DQEBCwUA
MGAxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTYwNAYD
VQQDEy1HbG9iYWxTaWduIERvbWFpbiBWYWxpZGF0aW9uIENBIC0gU0hBMjU2IC0g
RzIwHhcNMTQwOTI5MTU1OTQxWhcNMTUwOTMwMTU1OTQxWjBKMQswCQYDVQQGEwJV
UzEhMB8GA1UECxMYRG9tYWluIENvbnRyb2wgVmFsaWRhdGVkMRgwFgYDVQQDEw9p
bnRvdGhld2luZC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCZ
4nwCxV+6qWgZONNxGyMNjdIbEzO+EaGG4TlhYBzsn6h3yDCtat18tWXIQ25J+l03
zSJS2CbfMR7yFr1iKlrNHtdkmvHSOi3fC/FlIjmsJYbP5IQTSF7UoLLt21Vs6T8x
ix/sH6u2rs8aGyfPBbduY607v0r8yqcIJ4j1WczNcsvpixXG9mPKSCEmOQB4QppO
mc7OaIR6UUXunzQFrccZYUP978hzGzgZHXQNSELgkHELNJwYJi7+CJ1KJSqNeOw/
j8B5h+GbhhPrdvOr8NPwjQ3k+3YxevpVBSOFIPrYC8Wz0SLqHcuiI41I7t2lIU8o
bKQfhHvSpF521KQH79BVAgMBAAGjggIKMIICBjAOBgNVHQ8BAf8EBAMCBaAwSQYD
VR0gBEIwQDA+BgZngQwBAgEwNDAyBggrBgEFBQcCARYmaHR0cHM6Ly93d3cuZ2xv
YmFsc2lnbi5jb20vcmVwb3NpdG9yeS8wYwYDVR0RBFwwWoIPaW50b3RoZXdpbmQu
Y29tghNvd2EuaW50b3RoZXdpbmQuY29tghRtYWlsLmludG90aGV3aW5kLmNvbYIc
YXV0b2Rpc2NvdmVyLmludG90aGV3aW5kLmNvbTAJBgNVHRMEAjAAMB0GA1UdJQQW
MBQGCCsGAQUFBwMBBggrBgEFBQcDAjBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8v
Y3JsLmdsb2JhbHNpZ24uY29tL2dzL2dzZG9tYWludmFsc2hhMmcyLmNybDCBlAYI
KwYBBQUHAQEEgYcwgYQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9zZWN1cmUuZ2xvYmFs
c2lnbi5jb20vY2FjZXJ0L2dzZG9tYWludmFsc2hhMmcycjEuY3J0MDkGCCsGAQUF
BzABhi1odHRwOi8vb2NzcDIuZ2xvYmFsc2lnbi5jb20vZ3Nkb21haW52YWxzaGEy
ZzIwHQYDVR0OBBYEFPfk8s6E7BRobX+cTK8Ao/9z86IHMB8GA1UdIwQYMBaAFOpO
fNSALeUVgYYmjIJtwJikz5cPMA0GCSqGSIb3DQEBCwUAA4IBAQB9Fyabi4Ju+RU4
sWKcfZ6TnSj4dS/nZbKJtD9m2vSt55MVb/gpJMiz1Ytoi1ftj6jUvWiciIMcKNTT
OnpopipBgqvi5QbtcsPvT4cWw0xjxCqqZNPYvduKcHcZm2wFy7xargrn0keNP30+
gTMWBRVUVNECkqExv8tMG27MeVXPNzgz8pGk+qibR0Ysv/IBiqvdA3DGrPxTmuYS
b/lw6n4Ya/BwHcXhzOh63/d+CD+6cg/HWYt88gyycWfzOjtF65lRL1BUCYgsQLRP
ieHEnyzicLW+sWJhtvMgAkxwKpCOswb1puVxuD5QPUedIjVG+u1HtjrK+uQ1MclL
heUZjPom
—–END CERTIFICATE—–
—–BEGIN CERTIFICATE—–
MIIEXDCCA0SgAwIBAgILBAAAAAABMYnGQlgwDQYJKoZIhvcNAQELBQAwTDEgMB4G
A1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNp
Z24xEzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMTEwODAyMTAwMDAwWhcNMjIwODAy
MTAwMDAwWjBgMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1z
YTE2MDQGA1UEAxMtR2xvYmFsU2lnbiBEb21haW4gVmFsaWRhdGlvbiBDQSAtIFNI
QTI1NiAtIEcyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqd3MDrPi
MjndSSKoE2mTh4jhDO5xfb2Qh5ZdWfLMs9JYV1f5Ru9sJtg2Qo5+MLMvmj5Tex9u
tqJMRR880xWTHIntPPRX3sq97AaaaiqgGVJ/UdF0OQifq+vXhhMVl642w1RmDlry
oHOFMeOyZBRq/6WijiS7vYVSFaJ57vC17j249H2AvNmQNWW4F6mts5ifoH59bvs/
rXzCG1k2lto3MktLXTUCY47bp89i7swu1I3JvTxqkXKiIqdyLSDR+so32hiY5hYk
cSVLxOV7iVIJAv1ZKwRuygeB1LPa2tvjzICoVgcGfJYIN53bOLZiNJFiB3QBONhy
MOLrkHEmYsBX8wIDAQABo4IBKTCCASUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB
/wQIMAYBAf8CAQAwHQYDVR0OBBYEFOpOfNSALeUVgYYmjIJtwJikz5cPMEcGA1Ud
IARAMD4wPAYEVR0gADA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxz
aWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8ELzAtMCugKaAnhiVodHRwOi8vY3Js
Lmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMD4GCCsGAQUFBwEBBDIwMDAuBggr
BgEFBQcwAYYiaHR0cDovL29jc3AyLmdsb2JhbHNpZ24uY29tL3Jvb3RyMzAfBgNV
HSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0bvDANBgkqhkiG9w0BAQsFAAOCAQEA
asQTEbudYOYIgMIwjjpyB5oIB0XIrKrD85MGzbyWwKt7IzfBYFPvJPpKhbGSET9Y
Z3RAFBWwLNQme7DAeGM3MedBUDL/h2VtRi9mFsJ3cjffjB2ynXz79WmNDEGDBeXD
CDhdCaUwUQzemQAYJFATZ9U956HDXbA92Ho3wqPeCzxXJmuY/hfAUdEL8BdEK71i
gPIuTWgRjCLvlHt4p7WbguowPW2xYzOsZvok9lOdICfAXHRETYzo2yBAhQDmbSaf
dzhT8XdnuiJ3yEW84eLFJqSi6NDOgmdMyXg/4ntqs5XUwfpSfUQaAuXxScCedcp3
IAITFUgbBl1wm7duUhuklQ==
—–END CERTIFICATE—–

How to upgrade PHP to PHP 5.4 on CentOS 6 from a remi repository

Parallels Article ID: 115875

1. Install epel and remi repositories:
# wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
# wget http://rpms.famillecollet.com/enterprise/remi-release-6.rpm
# sudo rpm -Uvh remi-release-6*.rpm epel-release-6*.rpm

2. Enable remi repository:
# sudo vi /etc/yum.repos.d/remi.repo
In the [remi] section of the file, set the “enabled” option to 1.

3. Upgrade PHP with this command:
# yum install php

4. Set remi section back to 0.

Enable Spamassassin for all existing mailboxes

In order to enable Spamassassin for all existing mailboxes you can use the following script:
#!/bin/sh

#Get the list of mailboxes registered in PPA

mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -sNe “select mail.mail_name, domains.name from mail left join domains on mail.dom_id=domains.id” | sed -E ‘s/[[:space:]]+/@/g’ > /tmp/mailboxes_list

#Enable spamassassin for mailboxes

while read mailbox
do
/usr/local/psa/bin/spamassassin -u $mailbox -status true
done < /tmp/mailboxes_list

How to display email headers

Outlook 2013, 2010 (Windows): Double-click the message to open it in a new window. Select the File tab, and then click Properties.

Outlook 2007 (Windows): Double-click the message to open it, and then in the Options group, click the dialog box launcher (small square with an arrow).

Outlook Web App (OWA): Double-click the message to open it, and then click the Message Details icon (an envelope with a small document over it).

Outlook Express, Windows Mail, or Windows Live Mail (Windows): In the message index, right-click the message, and then select Properties. Click the Details tab.

Outlook 2011 (Mac OS X): In your Inbox (or other folder), right-click or control-click the message, and then select View Source.

Thunderbird (Windows, Mac OS X): Click View, select Headers, and then choose All.

Mail (Mac OS X): With the message selected, from the View menu, select Message, and then select either All Headers or Long Headers.

Gmail: Open the message in your Gmail inbox, Click the down-arrow in the top-right corner of the message, Click the “Show original” link toward the bottom of the options box. The message will open in a separate window with the full message headers at the top.

Yahoo Mail: Open the email message in your Yahoo Mail inbox. Click the “Full Headers” link located in the lower-right corner of the email message.

WordPress migration with full Plesk integration

Step by step instructions for moving a WordPress site between servers using ‘duplicator’ plugin.

Source server
1. Install duplicator
Login to WP admin area. Click Plugins. Search for ‘Duplicator’ plugin and install.
2. Activate the plugin through the ‘Plugins’ menu in WordPress
3. Click on the Duplicator link from the main menu
4. Create your first package.
You will go through a verification check of the setup. Fix any issues that duplicator finds.
5. FTP installer.php and packageName_archive.zip to destination server (download to PC, upload to new server).

Destination server
1. Move installer.php and package.zip file into document root directory.
2. Install WP through Plesk. This step is only necessary if you want Plesk to recognize the WP installation.
3. Look in the wp-config.php file and make a note of mysql db, user, password and then rename file to be wp-config.php.back.
4. Run the installer.php script. Adjust domain name and mysql settings.
5. Verify successful migration.
6. Remove migration files: installer.php, installer-data.sql, installer-log.txt, packageName_archive.zip, wp-config.php.back

change maximum email size in plesk

To change this do the following,
Login to Plesk
Under Server Management, Click “Tools & Settings”
Under Mail, Click “Mail Server Settings”
Change the “Maximum Message size” to however large you would like it to be. (for example: 25600 for 25MB limit or 30720 for 30MB limit)
Click “OK”

virtuozzo backup tips

http://kb.parallels.com/en/113790

Summary
Parallels server virtualization products use Parallels Virtual Automation (PVA) for standard backup and restore operations.
Parallels Virtual Automation Agent (PVA Agent) provides backup and restore tools and an API for the particular Hardware Node it is installed on.
Parallels Virtual Automation Management Node (PVA MN) provides a centralized backup and restore API for all nodes registered in the PVA group.
This article describes the backgrounds of the backup and restore processes, the server roles in the backup and restore processes, and common terms used in PVA.
Server roles
Generally, there are three roles in a backup or restore process:
Virtualization node – The Hardware Node with the virtual environments to be backed up. It must have Parallels Virtual Automation Agent installed.
Backup storage node – The Hardware Node used for storing backup data. It must have Parallels Virtual Automation Agent installed.
Control node – The server initiating the backup process. It must have either Parallels Virtual Automation Agent or Parallels Virtual Automation Management Node installed.

A single server can handle all three roles in the case of a local backup.
Backup scenarios
Scenario Roles Example
Local backup of mypvcserver
Virtualization node: mypvcserver

vzabackup -F mypvcserver -e CTID
Locally initiated backup to the remote storage
Virtualization node: myvpcserver
Backup storage node: remotestorage
Control node: myvpcserver
vzabackup –storage root@remotestorage localhost -e CTID
Backup initiated from the storage server
Virtualization node: myvpcserver
Backup storage node: remotestorage
Control node: myvpcserver
vzabackup -F mypvcserver
Backup of the server to remote storage initiated by the third server
Virtualization node: myvpcserver
Backup storage node: remotestorage
Control node: myvpcserver
vzabackup –storage root@remotestorage -F mypvcserver -e CTID
Backup tools and interfaces
Graphical
PVA Control Center – The web interface of PVA MN, allowing you to manage backups for all Hardware Nodes in the PVA group.
Power Panel – The web interface for managing a particular container. A backup initiated from the Power Panel is performed according to the local settings of the Hardware Node the container is hosted on.
Parallels Management Console (obsolete) – A graphical tool shipped with older versions of Parallels Virtuozzo Containers. This allows you to perform backup and restore operations across registered nodes.
Command-line
vzabackup\vzarestore – CLI interface to PVA Agent Backup API methods.
vzbackup\vzrestore (obsolete) – CLI interface to TAR-based backup. This does not require PVA Agent to be running.
NOTE: On Parallels Virtuozzo Containers for Windows, this is in the form of another wrapper on the vzabackup\vzarestore tool.
API
Backup interfaces of PVA Management Node XML API.
Backup interfaces of PVA Agent via SOAP and XML API.
Backup backend
Parallels provides two backends for backup files:
One that is compatible with Acronis Backup and Restore (default)
One that is compatible with TAR.
The backup engine backend can be switched in the PVA Agent configuration file:
Edit the PVA Agent configuration file:
/vz/pva/agent/etc/vzagent.conf
or
/var/opt/pva/agent/etc/vzagent.conf
Change the backend value to 0 for Acronis-compatible, or 1 for TAR-based:
vzlin_backup_serializer (for pre-PVA 4.6.4 nodes):


1
1

0
360000



vzlin_backup_serializer11 (for PVA 4.6.4 and later versions):
`

1
1
0 0
360000



Restart PVA Agent:
~# pvaagent restart
Additional information
How to increase PVA Agent timeouts for backup operations
Acronis Error: Module=0 Code=0, Tag=0 troubleshooting
Parallels Virtual Automation builds, releases, and supported virtualization products

delete email on plesk server

One of our customers had checked the “leave message on server” box, by accident in Outlook and over 8 months accumulated over 20,000 messages (mostly spam) on the server. The mailbox was close to 1.5GB in size.

Its a Qmail mail server.

First, find out exactly how many messages are in the box and sort by the largest message

ls -Slh | – less

The | less will allow you to go page by page. To exit type :q

He requested that we delete all the emails that were over 30 days old.

Then stop the server

/etc/init.d/qmail stop

Command to remove all the old messages:

find /var/qmail/mailnames///Maildir/curr -mtime +X -print | xargs rm

replace +X with the number of days (so in our case it was +30)

the Maildir/new folder contains messages in the queue.

Depending on how many messages are in the folder the above command can take a few minutes – do not cancel until you get back to the prompt $.

/etc/init.d/qmail start

search log files for most common hits

If you are having problems with possible attack on your server, check the log files for the most common hits. Many times you will find one page being accessed beyond what would be normal.

va1-fv00150# cat /usr/local/apache/logs/*/*access_log | awk ‘{print $7}’ | sort | uniq -c | sort -rn | head
35806 /administrator/index.php
89 /
37 /robots.txt
30 /favicon.ico
20 /administrator/index.php?option=com_login
16 /imgs/flash.swf
15 /imgs/home.html
14 /wp-login.php
14 /js/AC_RunActiveContent.js
14 /imgs/styles.css

Use this information to find what log file is getting the hits:

va1-fv00150# grep -R “/administrator/index.php” /usr/local/apache/logs/*/*access_log | cut -d: -f1 | sort | uniq -c | sort -rn | head
38313 /usr/local/apache/logs/ibreporttv/ibreporttv.com-access_log
5 /usr/local/apache/logs/goinsidebusiness/goinsidebusiness.com-access_log