The error received in plesk is:

HTTP Error 404.13 – Not Found

The request filtering module is configured to deny a request that exceeds the request content length.

All you have to do to solve this :

%windir%\system32\inetsrv\appcmd set config “PleskControlPanel/” -section:requestFiltering -requestLimits.maxAllowedContentLength:104857600

which will set a 100MB limit for file uploads in plesk file manager.

Server -> Certificates -> Add New Certificate

For Parallels Plesk Panel version 9.x:

Settings -> SSL Certificates -> Add SSL Certificate

Fill in required preferences and click button {Self-Signed}

New self-signed SSL certificate will be created in server certificate repository.

To assign this SSL certificate for securing your Parallels Plesk Panel mark enabled new SSL certificate in the list and push Secure control panel if you have Plesk 8.2 or later, or Install if you have older Plesk version.
Also, see Plesk documentation how to setup self-signed certificates.

After you created or uploaded new certificate into Plesk and wish to use it for domains you should set it for every IP you need, so domains use it when you access them via HTTPS.
It can be done on page Server -> IP Addresses -> “choose IP” by selecting needed Certificate in “SSL Certificate” drop down menu.

or

I use 1 SSL cert for plesk control-panel, pop3s, imaps and smtps.

After generating the new certificate in the administrator repository. make it your default certificate and mark it again and press setup to install it on your plesk admin server on port 8443. then put the certificate at your main ip-adresse in your ip-pool(maybee this step is not necessary).

copy /usr/local/psa/admin/conf/httpsd.pem
to
/usr/share/courier-imap/pop3d.pem, /usr/share/courier-imap/imapd.pem and /var/qmail/control/servercert.pem

please have a look that the owner(very important) and the chmod rights are the same of pop3d.pem, imapd.pem and servercert.pem. like before otherwhise qmail will for example not work/start, because it can’t read the file.

restart courier(imap,pop3) and qmail(smtp) in the plesk server service control panel.

after this plesk control-panel 8443, pop3s, imaps and smtps should work without warning messages and with only 1 ssl cert, if you use for all services the same main hostname.domain.com address like me.

(maybee you should also have a look, that the same hostname is configured in the qmail config file)

finally to test certificates :

openssl s_client -connect [host]:993

openssl s_client -connect [host]:995

openssl s_client -connect [host]:465

openssl s_client -connect [host]:8443

where for e.g. host=localhost

[emerg] (28)No space left on device: Couldn’t create accept lock
or
[crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock Configuration Failed
Checking your disk shows that you have plenty of space. The problem is that apache didn’t shut down properly, and it’s left myriads of semaphore-arrays left, owned by my apache-user. Run:-

For CPanel :

ipcs -s | grep nobody
Removing these semaphores immediately should solve the problem and allow apache to start.
ipcs -s | grep nobody | perl -e ‘while (<STDIN>) { @a=split(/\s+/); print `ipcrm sem $a[1]`}’

For Plesk :

ipcs -s | grep apache
Removing these semaphores immediately should solve the problem and allow apache to start.
ipcs -s | grep apache | perl -e ‘while (<STDIN>) { @a=split(/\s+/); print `ipcrm sem $a[1]`}’

/usr/local/psa/bin/pre9-backup-convert -v convert -d /var/lib/psa/dumps/  /root/plesk8-backup-file

then go to plesk 9 panel and restore the backup from the client and/or precreated domain.

for example you can modify local delivery in .qmail to replace  “/usr/bin/deliverquota ./Maildir” with something like “/var/qmail/bin/preline -f /opt/libexec/dovecot/deliver -d user@domain”.

basically there are two ways to do that from plesk:

one is using event handlers: http://download1.swsoft.com/Plesk/Plesk8.6/Doc/en-US/plesk-8.6-unix-administrators-guide/22819.htm

second is using mail handlers: http://download1.parallels.com/Plesk/Plesk8.6/Doc/en-US/plesk-8.6-unix-mod-api/38611.htm

Part of what makes the PHP mail() function is so simple is its lack of flexibility. Most importantly and frustratingly, the stock mail() does not usually allow you to use the SMTP server of your choice, and it does not support SMTP authentication, required by many a mail server today, at all.

Fortunately, overcoming PHP’s built-in shortcomings need not be difficult, complicated or painful either. For most email uses, the free PEAR Mail package offers all the power and flexibility needed, and it authenticates with your desired outgoing mail server, too. For enhanced security, secure SSL connections are supported.

Send Email from a PHP Script Using SMTP Authentication

To connect to an outgoing SMTP server from a PHP script using SMTP authentication and send an email:

• Make sure the PEAR Mail package is installed.
  • Typically, in particular with PHP 4 or later, this will have already been done for you. Just give it a try.
• Adapt the example below for your needs. Make sure you change the following variables at least:
  • from: the email address from which you want the message to be sent.
  • to: the recipient’s email address and name.
  • host: your outgoing SMTP server name.
  • username: the SMTP user name (typically the same as the user name used to retrieve mail).
  • password: the password for SMTP authentication.

Sending Mail from PHP Using SMTP Authentication – Example

<?php
require_once “Mail.php”;

$from = “Sandra Sender <sender@example.com>”;
$to = “Ramona Recipient <recipient@example.com>”;
$subject = “Hi!”;
$body = “Hi,\n\nHow are you?”;

$host = “mail.example.com”;
$username = “smtp_username”;
$password = “smtp_password”;

$headers = array (‘From’ => $from,
‘To’ => $to,
‘Subject’ => $subject);
$smtp = Mail::factory(’smtp’,
array (‘host’ => $host,
‘auth’ => true,
‘username’ => $username,
‘password’ => $password));

$mail = $smtp->send($to, $headers, $body);

if (PEAR::isError($mail)) {
echo(“<p>” . $mail->getMessage() . “</p>”);
} else {
echo(“<p>Message successfully sent!</p>”);
}
?>

Sending Mail from PHP Using SMTP Authentication and SSL Encryption – Example

<?php
require_once “Mail.php”;

$from = “Sandra Sender <sender@example.com>”;
$to = “Ramona Recipient <recipient@example.com>”;
$subject = “Hi!”;
$body = “Hi,\n\nHow are you?”;

$host = “ssl://mail.example.com”;
$port = “465″;
$username = “smtp_username”;
$password = “smtp_password”;

$headers = array (‘From’ => $from,
‘To’ => $to,
‘Subject’ => $subject);
$smtp = Mail::factory(’smtp’,
array (‘host’ => $host,
‘port’ => $port,
‘auth’ => true,
‘username’ => $username,
‘password’ => $password));

$mail = $smtp->send($to, $headers, $body);

if (PEAR::isError($mail)) {
echo(“<p>” . $mail->getMessage() . “</p>”);
} else {
echo(“<p>Message successfully sent!</p>”);
}
?>

Unfortunately I did not find too many docs related to it so find out from Parallels that webmail is not running from “webmail” application pool but on plesk default application pool that can be found in plesk -> server-> IIS Application Pool . If this is not running so webmail will not work and you have to restart this application pool to start webmail.

<IfModule mod_tls.c>
TLSEngine on
TLSLog /var/log/tls.log
TLSProtocol SSLv23

# Are clients required to use FTP over TLS?
TLSRequired off

# Server’s certificate
TLSRSACertificateFile /usr/local/psa/admin/conf/httpsd.pem
TLSRSACertificateKeyFile /usr/local/psa/admin/conf/httpsd.pem

# Authenticate clients that want to use FTP over TLS?
TLSVerifyClient off

# Allow SSL/TLS renegotiations when the client requests them, but
# do not force the renegotations.  Some clients do not support
# SSL/TLS renegotiations; when mod_tls forces a renegotiation, these
# clients will close the data connection, or there will be a timeout
# on an idle data connection.
TLSRenegotiate required off
</IfModule>

As values in TLSRSACertificateFile and TLSRSACertificateKeyFile otion you can use as Plesk certificate, for example /usr/local/psa/admin/conf/httpsd.pem as your own one.

After that restart proftpd from xinetd : /etc/init.d/xinetd restart

1. Launch command prompt.

2. CD “%plesk_dir%Additional\Php\”.

Note: The folder can be different – e.g. in case of using PHP5.

3. Execute go-pear.bat and follow the on-screen instructions.

4. Add the path to the newly created pear.bat file into the PATH system variable after installation and reboot the machine for changes to take effect.

These actions will install the ‘pear’ command on your server including basic pear packages. You can use ‘pear’ command from the Windows command prompt to manage PEAR packages.