Archive for the ‘Plesk for Windows’ Category

Admin Login fails.

Wednesday, September 20th, 2006

Problem,
Fatal error: Unable to logon user (EV1SERVE-01UIT2\Plesk Administrator): (1327) Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced. in C:\Program Files\SWsoft\Plesk\admin\htdocs\login_up.php3 on line 3

Solution,

In the C:\Program Files\SWsoft\Plesk\admin\bin\ folder run the papswd.exe file with the following values,
papswd –set –password=’NewPassword’

File Manager cant access httpdocs

Wednesday, August 17th, 2005

You receive the following error when accesing httpdocs through the control panel,

Unable to change directory to /httpdocs/: Invalid file name.

The problem is caused by invalid charachters in the files names uploaded, so fat it seems that the following could
cause the problem,

“&”, “`”, “‘ “, ” [ and ]”

The solution is to change the filenames.

Unable to remove sub domains from Plesk for windows

Monday, August 15th, 2005

The normal cause of this is that IIS lost the sub domain entry.

Without this entry you won’t be able to manage the sub domain in your Plesk Control Panel.

The entry must be re-created in IIS.

When creating the sub domain in IIS, the default path for the sub domain to use,
C:\Inetpub\vhosts\domain.co.za\subdomains\test\httpdocs

Once added log into the control panel and remove or edit the sub domain.

Running Plesk on Port 443

Saturday, March 5th, 2005

By default Plesk is installed to run on port 8443. Some companies have very restrictive firewalls, which might lead to clients not being able to access the Plesk control panel. I have found that most companies will happily allow a connection on port 443, the standard port for SSL connection. Luckily you can configure Plesk to listen on a second IP address for connections to port 443.

This method describled below has been tested on Plesk for Linux version 6.0.x, 7.1.x and Plesk for Windows version 7.5.x.

Step 1: Add a secondary IP address to your server. The way to do this depends on the OS and is left as an excercise to the reader. We assume that our secondary IP address is: 10.0.0.1
Step 2: Edit the httpsd.conf file. In this file add the following entry: Listen 10.0.0.1:443.
Step 3: If on Linux, edit the ssl.conf file, to only Listen on the the main IP address’s SSL port.
Step 4: Restart the Plesk control panel
Step 5: Test the setup, by connecting to: https://10.0.0.1/

If everything was done properly the Plesk control panel will now be running on port 443.

Plesk for Windows 7.5.0 & MySQL

Sunday, February 27th, 2005

There are two instances of MySQL running, one on port 3306 (default) and one on port 8306. The instance running on port 8306 is the intstance that is used by the Plesk contol panel.

Use the -P option of the mysql.exe client tool to specify the port:

mysql -u admin -p -P 8306

Mail Enable 1.8 on Plesk 7.0.3 & the default email message

Saturday, February 5th, 2005

When creating a new email address (mailbox) on Plesk 7.0.3 for Windows, you will recieve a default email in the mailbox. This default email is stored in the following locations:

Filename: DEFAULT.MAI
System default: C:\Program Files\SWsoft\Plesk\Mail Enable\Config\Postoffices
Domain default: C:\Program Files\SWsoft\Plesk\Mail Enable\Config\Postoffices\<domainname>

To alter the email is very easy. All you need to do is to create the email message as you would like it to appear to your clients and then send it to one of the defined email addresses on the system. You will be able to retrieve the email from the location below.

Email file locaton: C:\Program Files\SWsoft\Plesk\Mail Enable\Postoffices\<domainname>\MAILROOT\<mailbox>\Inbox\*.MAI

Plesk 7.0.3 for Windows & PASV FTP

Tuesday, February 1st, 2005

After playing with the defautl install of Plesk 7.0.3 for Windows we reliased that it does not support PASV FTP if you enable the Firewall. After a few minutes of searching, the solution was found.

You need to tell IIS to only use a certain range of ports for PASV FTP connections. Microsof provides the following knowledge base article on how to achive this: How To Configure PassivePortRange In IIS

After you have limited IIS to only use a certain port range, you have to configure the default firewall management file Plesk\admin\bin\pfwmng.js to listen on the TCP ports for incomming connections. Yes, this does mean adding each port seperated by a comma in this file. For more information please visit the followin link: Plesk Firewall question