plesk / whmcs-plugin

Other
16 stars 33 forks source link

Plesk v17.8 Compatibility #43

Closed ghost closed 6 years ago

ghost commented 6 years ago

Hi, I have recently setup WHMCS and have hit some issues with the API not working with Plesk Onyx 17.8. WHMCS have advised me that due to changes to the API in this version it is not backwards compatible and that I should install v17.5. I am on a managed VPS with my hosting company and they say they are unable to change the version of Plesk that my server is running. I wondered when WHMCS will be compatible with Plesk 17.8? Or if there is a workaround?

ghost commented 6 years ago

The issue occurs when I run a test order. The automation seems to fail in setting up an account and subscription on the server.

I get an email that reads:

An order has received its first payment but the automatic provisioning has failed and requires you to manually check & resolve.

Client ID: 2 Service ID: 3 Product/Service: Essential Domain: thecustomersdomain.com Error: Error code: 1014. Error message: Server response could not be processed.

And then when I click the "Test Connection" button on the server setup page I see this error:

FAILED: Error code: 1014. Error message: Server response could not be processed.

And then on the Product/Services > Edit Product > Module Settings tab there is a warning triangle with an "!" inside which when I hover over it reads:

Server response could not be processed.

Now after reading WHMCS Plesk documentation and seeing that Plesk Onyx 17.8 is not fully compatible I assumed that this was the reason I am seeing these errors. Any help at all would be greatly appreciated, I don't seem to be getting anywhere with my hosting company or WHMCS support!

ghost commented 6 years ago

Sorry for the spam of comments but I also have a request and response from the module log for this issue that may be helpful:

Request:
<?xml version="1.0" encoding="UTF-8"?><packet version="1.0.0.0"><!-- Copyright 1999-2016. Parallels IP Holdings GmbH. -->
<server>
<get_protos/>
</server>
</packet>

Response:
File not found.

Again thank you for any help,

Hayden