Posts tagged Plesk

Table ‘mysql.servers’ doesn’t exist

Sep 28th

Posted by PB in Plesk

No comments

If you have ever had the error message “Table ‘mysql.servers’ doesn’t exist” when you have tried to delete a database or a domain with a database attacked within plesk, error below (DB names masked out for security) then luckily there is an easy fix which does require you being able to SSH onto your server:

More >

, , , ,

Upgrading PHP on a windows plesk server

Jul 27th

Posted by PB in Plesk

No comments

PHP comes pre-installed along with Plesk on a windows server, and by default, PHP only gets upgraded as new versions of Plesk are released. Unfortunately the release cycle of the Plesk Control Panel does not keep pace with that of PHP, so the result is that VPS / VDS Containers are often running versions of PHP that are several versions older than the current release. This can be an issue when you are trying to get PCI compliant

Follow the sets below to upgrade PHP

In order to upgrade PHP 5.x to the needed version (beyond that which is current bundled with the Plesk Control Panel), please perform the following steps…

More >

, , ,

Upgrading BIND on a plesk windows server

Jul 26th

Posted by PB in Plesk

1 comment

If you want to manually upgrade the version of BIND running on your plesk windows server then follow the following steps:

  1. Check what version of bind you are currently running by going to the Components Management in plesk, you should see something like the following:

  2. Go to LINK and download desirable version of BIND for Windows.

    3. More >

, , ,

PCI Scan – Plesk PHP easter egg issue

Jun 25th

Posted by PB in PCI

1 comment

PCI Scan – Plesk PHP easter egg issue

If your PCI scan reports the following:

Port: 8443

Synops is: The configuration of PHP on the remote host allows disclosure of sensitive
information.

More >

, , ,

Increase maximum number of addesses that can be added to the Spamassassin White or Black list

Mar 23rd

Posted by PB in Plesk

No comments

You may get the following error message

Warning: Only 100 first unique e-mail addresses will be added.


Since Plesk Control Panel version 8.4.0 you may configure maximum number of addresses that can be added to the Spamassassin While or Black lists through the control panel.

It is variable psa.misc.spamfilter_max_addr_list_length in Plesk database, 100 addresses are used by default.

To set the new figure do the following:

  1. Connect to mysql and the plesk DB, you can use
    mysql -uadmin -p$ (cat /etc/psa/.psa.shadow) -Dpsa
  2. Then use the following SQL query to set maximum number of addresses to 150
    replace into misc values(‘spamfilter_max_addr_list_length’,150);
Note

Big number of addresses in Spamassassin White/Black may strongly reduce server performance.

, , , ,

Running a .vbs file as a Schedule task in plesk

Mar 17th

Posted by PB in Plesk

No comments

This took me a bit of time to work out but if you are trying to run a scheduled task in Plesk (Windows) that launches a .vbs file then you need to do the following:

In Path to executable file you need to enter the path to csripts.exe, for example:

c:\windows\system32\cscript.exe

Then in Arguments you need to enter the full path to the .vbs file

c:\interpub\vhost\…\…\myscript.vbs

And that is all you need to do to launch a .vbs file in Plesk task scheduler

, , ,

PCI Compliance Expect Header Cross-Site Scripting Vulnerability (8443, plesk)

Feb 22nd

Posted by PB in PCI

3 comments


PCI compliance Expect Header Cross-Site Scripting Vulnerability

If you get the following warning in a PCI scan:

Security warning found on port/service "pcsync-https (8443/tcp)"
 Plugin "Expect Header Cross-Site Scripting Vulnerability"
 Category "CGI abuses : XSS "

Priority "Medium Priority "Synopsis : The remote web server is vulnerable to a cross-site scripting
attack. Description : The remote web server fails to sanitize the contents of an 'Expect'
request header before using it to generate dynamic web content. An unauthenticated
remote attacker may be able to leverage this issue to launch cross-site scripting attacks
against the affected service, perhaps through specially-crafted ShockWave (SWF) files
  More >
, ,
12»