Hi all

I'm trialling a WHMCS install on a Plesk server.

I'm sure I've got everything set up right, client & domain templates are in place, & I believe the server is set up right in WHMCS but on my 1st test purchase the user account was set up ok, money taken ok, but the hosting account could not be created on the Plesk server, the error being '1001 - Login is incorrect.'

I've verified that the username / password I've set up in the Server config is correct (Plesk button there takes me to the admin CP)

What am I doing wrong?

Make sure the packages that you have added on server should be same in packages in whmcs.

Also in Products >> Module Type you need to select Plesk.

When you say packages do you mean the Client / Domain templates? If so, both your suggestions are already set up correctly.

I'm also making the assumption that the username / password set up in the server config in WHMCS should be that of the admin user on the Plesk server?

Not sure if plesk has Hash Key / Access key :(

In WHMCS Server section you may want to add Hash Key to access server
along with login details.

Atleast in cPanel I am sure it needs hask key.

Just had another read of the WHMCS instructions & it doesn't mention hash keys, I think the key is the '1001 - Login is incorrect' error. I'm 110% certain it is correct (the Plesk button in the WHMCS server list takes me to the admin CP)

The best thing to do is e-mail Matt and the guys over at WHMCS and they can look into it for you. Their support address is support@whmcs.com

A Google search revealed a post from 2007 with that error regarding MB. Here was the solution then:
"Anyone having problems with Plesk/Modernbill integration be advised that at the present time Plesk 8.2 will only accept a password with no more than 14 characters! The password supplied to Modernbill's API was 19 characters."

If your password is quite long, that might still be an issue with Plesk?

A Google search revealed a post from 2007 with that error regarding MB. Here was the solution then:
"Anyone having problems with Plesk/Modernbill integration be advised that at the present time Plesk 8.2 will only accept a password with no more than 14 characters! The password supplied to Modernbill's API was 19 characters."

If your password is quite long, that might still be an issue with Plesk?

Given how buggy most Parallels products are, I would not be surprised if this was still an issue. There are a few bugs lingering from Plesk 7.6 (released in July 2006), such as the following mentioned on this very site

http://www.webhostingtalk.com/showthread.php?p=6513366

OP, try setting a shorter password (say 12 characters), and set it in the Server info in WHMCS. Does it work then? Different error?

Bear, looks like you might have found it, my original password was 14 characters long, I've changed it to a shorter one & things are starting to happen.

Still more problems to deal with but it looks like WHMCS is talking to Plesk now.

Thanks to everybody for your help

Bear, looks like you might have found it, my original password was 14 characters long, I've changed it to a shorter one & things are starting to happen.

Still more problems to deal with but it looks like WHMCS is talking to Plesk now.

Thanks to everybody for your help

Glad to hear it is working out for you, and shame on Parallels for letting such a stupid bug to last for as long as it has. I don't know how they stay in business sometimes.

Excellent, glad that worked.

Also make sure none of your package names have 2 underscores this often cause's problems.

Thanks for the tip

This thread came up in a Google search as I have been fighting the same problem all day (WHMCS support wasn't able to help).

My problem was that the password was too short rather than too long - it was only 7 characters. I changed to 10 and the module works perfectly now!

Thank you!

still not working.. :( not getting the required help from whmcs support team too.

still not working.. :( not getting the required help from whmcs support team too.
What isn't working about yours? Explain the issue, and maybe someone can offer a suggestion.