websavers Posted December 2, 2011 Share Posted December 2, 2011 This is not a 5.0 bug. By coincidence after updating to 5.0 we lost the old school 'plesk' module and wound up with the individual version modules - plesk8, plesk9, plesk10. Since our servers are all Plesk 9 boxes anyway, I figured I would just switch all products over to using the plesk9 module. Except it doesn't work. I had to switch it to the plesk8 module in order to make auto provisioning work at all, otherwise I would get an Error 1014 (even though the client details are all accurate and have no special characters). Using the Plesk8 module on a Plesk 9.5.4 server works perfectly. See here for others describing the same problem: http://forum.whmcs.com/showthread.php?t=42079 This is not likely to be a problem for others upgrading, but it will be a problem for new users and should be fixed. Why is there even a Plesk9 module if it doesn't function? 0 Quote Link to comment Share on other sites More sharing options...
CavalloComm Posted December 3, 2011 Share Posted December 3, 2011 NO! Don't do that! I learned from Matt that you should add THIS to your config.php: $pleskpacketversion = "1.6.0.0"; before the end. It's an issue with their API and not all people experience this. Trust me, do NOT use the Plesk8 with a Plesk9 system, it will cause you to do surgery on your database!!! And their Plesk9 version is actually OK - it's when Plesk puts updates out they change bits without telling anyone - which they are famous for... I can't wait to have the time to migrate off Plesk..... 0 Quote Link to comment Share on other sites More sharing options...
websavers Posted December 5, 2011 Author Share Posted December 5, 2011 Thanks CavalloComm, I've applied that to my configuration.php file and put the servers back to the Plesk9 module - hopefully that will do the trick. Parallels regularly changes / increases the packet versioning system, but the API has a simple connection call that returns the current packet version number. I wrote a WHMCS plugin that connects to all your Plesk servers and gets status information and came upon different issues with the API version differences at that time. I used the initial connection request to get the current version and adapt to different bugs in older packet versions accordingly. I don't see why the plesk9 module can't do this for us. Regarding database issues - how would that be the case? All calls are done through the Plesk API, which means WHMCS doesn't have any access to do direct DB transactions. I used the Plesk8 module for a few provisions and ran a DB check on the psa database; everything reports fine. 0 Quote Link to comment Share on other sites More sharing options...
CavalloComm Posted December 5, 2011 Share Posted December 5, 2011 Maybe it was a fluke on my end. I am usinig SimpleDNS Plus and for whatever reason, when I added the domain using Plesk8 as you suggested before I opened a support ticket, I could not no matter what I did add that domain to DNS. No matter what I did. Then I had to go into the PSA Database and I noticed it added the domain several times in the DNS table. I cleared all of that out, and ran with plesk9 using the above and all worked. I would be interested in your Plugin?? 0 Quote Link to comment Share on other sites More sharing options...
websavers Posted December 5, 2011 Author Share Posted December 5, 2011 I would be interested in your Plugin?? It's a bit rough around the edges, but I'll try and fix it up and let you know how it goes 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.