plesk

If you have a Plesk server where short mail names are enabled, upgrading to Plesk 8.

Some of you may have already noticed from my Twitter feed, but I’ve started a complete re-write of pleskhacker.

I found a Plesk 8.

If you have Plesk 8.

If you recently upgraded to Plesk 8.

There was a bug in versions of Plesk prior to 8.

It seems like I have a conversation like this one at least once a week:

I’m really enjoying the Parallels Summit in Washington D.

Normally, qmail will be able to process the mail queue without any interaction from the system administrator, however, if you want to force it to process everything that is in the queue right now, you can do so:

Upgrading Plesk from 7.

UPDATE: The TRACE/TRACK methods are disabled in Plesk 8.

If you’re working in Plesk and you receive this error:

On a Plesk server, the maximum size for an individual e-mail sent through qmail is unlimited.

I really dislike qmail.

One of my biggest Plesk gripes is dealing with the Plesk Professional Website Editor.

I saw a ticket the other day where a customer received this error from Horde when trying to expand items on the left pane of the interface:

One of my biggest complaints on RHEL 4 is the large resource usage by the version of SpamAssassin that is installed.

One of the questions I receive the most is: “What version of Plesk works with MySQL 5?

If you have a new Plesk installation and the following option is greyed out in Server -> Mail:

I stumbled upon this peculiar bounce message recently while working on a server:

If you’ve used newer versions of Horde with Plesk, you have probably noticed the news feed that runs down the left side of the screen.

I stumbled upon a server running Plesk 8.

There’s a few issues with PHP 5.

One of my biggest beefs with Plesk’s e-mail handling is the lack of server-side filtering.

I found myself wrestling with a server where the Plesk interface suddenly became unavailable without any user intervention.

If you’re using Plesk 8.

On brand new Plesk 8.

I’ve seen quite a few situations where the Horde login process can take upwards of 45 minutes to log a user into the webmail interface.

One of the most annoying (and explosive) changes in Plesk 8.

Yet another weird Plesk error with terrible grammar popped up on a server that I worked with this week:

Normally, this error will pop up when you attempt to restart a Plesk-related service, like httpsd, psa-spamassassin or qmail:

Some users will want to parse HTML through the PHP parser because one of their applications requires it, or because they think it’s a good idea.

Since AOL sends their users’ traffic through proxy servers, this can cause problems with Horde’s session handling in Plesk.

I hear a lot of complaints about Plesk’s backup routines and how they can bring a server to its knees.

It’s not abnormal for qmail act oddly at times with Plesk, and sometimes it can use 100% of the CPU.

By default, views in MySQL 5.

In some situations, you may want to have domain.

With Plesk 7.

Plesk has a (somewhat annoying) default firewall configuration that you can adjust from within the Plesk interface.

This error means that Plesk attempted to make a DNS change and reload named, but it failed.

If you’ve used Plesk with a large amount of domains, you know what a pain running out of file descriptors can be.

These two commands will enable SpamAssassin for all users on a Plesk 8 server:

If you want to make a quick bookmark that will automatically log yourself into Plesk, make this bookmark:

If this situation pops up in Plesk, it means that a user has changed their MySQL password outside of Plesk.

If you want to remove all of the open_basedir restrictions for all sites in Plesk, simply create a file called /etc/httpd/conf.

Should you find yourself needing to send e-mail destined for a certain account to a blackhole or to /dev/null, you’ll find very little information from Google.

If you have an open_basedir restriction that is causing issues with a domain, you can remove the restriction easily.

When Plesk is installed, the default certificate for the Plesk interface itself is a self-signed certificate that is generated during the installation.

Thanks to a highly awesome technician on my team, we’ve discovered the perfect permissions setup for Joomla and Plesk:

If you can’t send mail via port 25 due to blocks imposed by your ISP, you can enable the submission port within Plesk pretty easily.

If you find that Horde (with Plesk) keeps refreshing when you attempt to log in, and there are no errors logged on the screen or in Apache’s logs, check the session.

When you need to find information about anything in Plesk, here’s some SQL statements that you can use:

To add a chrooted FTP user outside of Plesk properly, you need to:

If you find yourself in the situation where you need to bulk add SPF records to every domain in Plesk, you can use this huge one-liner:

If you get this error, you’ve most likely done a file-based MySQL backup restore, and the InnoDB files are hosed.

If Plesk throws an error that it can’t upgrade your license key because of languages, you need to remove the extra locales:

Before you upgrade Plesk, it’s always a good idea to make a backup and also make your ip and shell maps:

I’ve heard a lot of people are interested in something like this, so I decided to create it.

To disable reverse lookups in qmail with Plesk, simply add -Rt0 to the server_args line in /etc/xinetd.

Often times, the wonderful webmail application known as Horde will spin out of control and cause unnecessary resource usage and often cause defunct Apache processes to appear.

The AWStats package in RHEL4/Centos4 and Plesk 8.

If your server is sending out spam because of some bad scripts, hunt that stuff down:

To stop those evil double bounce e-mails in Plesk, just do:

If you need to change to a different primary IP in Plesk, here’s the easiest way:

To disable SSLv2 server-wide on a Plesk server, add this in your /etc/httpd/conf.

You can edit /etc/drweb/drweb_qmail.

A really really strange issue randomly appears with ProFTPD and Plesk occasionally.

There’s lots of situations where you’d want to use a bulk IP change in Plesk:

Moving domains from client to client in Plesk is pretty quick from the command line.

If odd bounced e-mails are coming back to the server or the server is listed in a blacklist, some accounts may be compromised on the server.

If you need to enable SSL in ProFTPD, try this out:

Need to redirect all users except for yourself to another site until yours is live?

If you think an e-mail account has been hacked in Plesk, use this to hunt down which one it could be:

Need a handy way to list all the email accounts and their passwords?

If Plesk ever appears to be out of sync with the configuration files, or if there’s a Plesk issue that’s occurring that makes no sense at all, just stand back and wave the Plesk magic wand:

If you’re migrating a domain, sometimes their mail will go to the old server for a while after you’ve changed the DNS.

Need a username and password from the Plesk DB?