Top Nav

Archive | Plesk

Howto: Change Default Index On Plesk 10 for Windows

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

http://www.acme.com/

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.
2

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 bigfish.com and the source address in the server mail logs was a host in messaging.microsoft.com.

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 “@bigfish.com” but it did not work because the “black domain patterns list takes precedent.

Now to solve the problem of mail from *.messaging.microsoft.com 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 – bigfish.com error

4

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.

–ben

0

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.

1

Easy Plesk Access Tricks

Plesk is a popular web hosting control panel used by many of our clients. On servers with Plesk, the control panel is located at:

https://yourdomain.com:8443

There are several problems with this URL:

1. It’s hard for users to remember the 8443 on the end and the https on the beginning of the URL.

2. Plesk by default uses a self signed SSL certificate that causes warning to be displayed in the user’s web browser.

Wouldn’t it be nice if you could put Plesk on a friendly URL like https://plesk.yourdomain.com?

Also lets have:

http://plesk.yourdomain.com

automatically redirect to:

https://plesk.yourdomain.com.

Now the your users don’t have to remember the https part either.

Now lets get really fancy. Suppose your customer has a domain named acme.com hosted on your server. It would be nice to have the URL:

http://acme.com/plesk

redirect to:

http://plesk.yourdomain.com.

Guess what – it can all be done! Here’s how:

1. Get an SSL certificate for plesk.yourdomain.com. A $29 cert from GoDaddy will work just fine. Place the SSL key in:

/etc/pki/tls/private/plesk.yourdomain.com.key

and the SSL certificate in:

/etc/pki/tls/certs/plesk.yourdomain.com.crt

2. Next, create /etc/httpd/conf.d/plesk_proxy.conf with the following contents:

Now just restart Apache and you’re ready to go.

Couple of issues to note:

  1. You’ll need to add the hostname plesk.yourdomain.com to DNS.
  2. Depending on your server config, you may need to place plesk.yourdomain.com on a dedicated IP address since each IP address can host only a single SSL site.
2