Top Nav

Archive | Plesk

WordPress URL Rewrites On Plesk 10 Windows

We needed to get URL rewrites working on a Plesk 10 Windows server for a client wanting friendly URLs in WordPress. Turned out to be pretty easy ….

1. Make sure the Microsoft IIS URL Rewrite 2 extension is installed. You can find it here:

2. Create a web.config file in the folder where you have WordPress installed with the following:


Howto: Change Default Index On Plesk 10 for Windows

When you request a URL with no file name at the end like:

the web server consults a list of predefined “index” or “default” file names and returns the first matching file.

On Plesk 10 for Windows follow these steps to change the default index page list:

  1. Login to Plesk
  2. Drill-down to the control panel for the domain that you wish to change.
  3. Click on “Websites & Domains >> more” link.
  4. Click on “Show Advanced Operations” link.
  5. Click on “Virtual Directories” icon.
  6. Click “Directory Properties” icon.
  7. In the “Documents” section, find the “Default documents search order field”. From here you can add new default file names and change the order of precedence for the file names.
  8. When you’re finished making changes click the “OK” button at the bottom of the page.

Plesk 10 Greylist Problems

Recently on several Plesk 10 servers we’ve had users complain that they could not receive email from various domains. Upon investigation we found that the domains were all hosted on Microsoft’s Exchange email service. The bounce messages received by the sender were from and the source address in the server mail logs was a host in

We found log entries like this:

So the greylist filter in Plesk 10 is blocking server that are on “dsl|pool|broadband|hsd” address ranges. In this case it would be Microsofts cloud anti-spam service that is on “pool” addresses.

From the Plesk control panel there are very few settings for the greylist filter – you can turn the filter on/off and manage white/black list entries. But there are no options to configure the filtering rules. After some digging at the command line I found this:

This plesk utility give a listing of the configuration for the greylist filter and provides options for configuring the greylist:

Here’s a sample of the info output:

Notice that the server admin tried to whitelist the “” but it did not work because the “black domain patterns list takes precedent.

Now to solve the problem of mail from * we can just add another “white domains pattern list” like this:

And now the email from Microsoft hosted domains should be delivered without error.

Here’s a Parallels Knowledgebase Article on this subject:

How to configure Greylisting

And here’s a thread on Serverfault that got me on the right track:

e-mail gets rejected – error


Non-chrooted Cronjobs In Plesk 10

Plesk 10 has a bug (feature?) where it inserts this line into the crontab file for each user (including non-chrooted users):

This effectively breaks the jobs, because it makes them try to run in a chroot jail, which won’t work. You can manually remove the lines but Plesk will restore them when the job is edited. A workaround, is to run this command on the server:

That changes the SHELL setting to a normal default value, which should run the jobs correctly. This is not a great fix, because it probably messes up cronjobs for users who really are chrooted but it may be useful to some.



Plesk Admin Password

On versions prior to Plesk 10, you can find the Plesk admin password in:

For Plesk 10 and beyond, use this command instead:

Even more interesting is the MySQL admin password. For all versions of Plesk, the MySQL admin password is the string contained in /etc/psa/.psa.shadow. In Plesk 10, the password is the hashed value stored in this file.