jessasaurus Posted September 28 Share Posted September 28 Im having some issues with the server sync with plesk under the module/server "No match found on server" the domains, ips and usernames been redataed for privicy Server Sync Step 2 of 4: Analyse Module/Server WHMCS Import /Sync Domain Primary IP Username Product Status Created ID Domain Primary IP Username Product Status Created No match found on server 1 domain.co.uk 127.0.0.1 a username Advanced Hosting Active 2021-03-07 No match found on server 2 domain.co.uk 127.0.0.1 a username Advanced Hosting Active 2019-06-02 No match found on server 5 domain.co.uk 127.0.0.1 a username Premium Hosting Active 2022-02-14 No match found on server 14 domain.co.uk 127.0.0.1 a username Platinum Hosting Active 2019-04-21 No match found on server 15 domain.co.uk 127.0.0.1 a username Platinum Hosting Active 2019-04-21 No match found on server 16 domain.co.uk 127.0.0.1 a username Platinum Hosting Active 2019-04-21 No match found on server 17 domain.co.uk 127.0.0.1 a username Platinum Hosting Active 2023-10-31 No match found on server 19 domain.co.uk 127.0.0.1 a username Platinum Hosting Active 2019-04-23 No match found on server 113 domain.co.uk 127.0.0.1 a username Platinum Hosting Active 2024-02-13 No match found on server 114 domain.co.uk 127.0.0.1 a username Platinum Hosting Active 2026-09-28 No Records Found 0 Quote Link to comment Share on other sites More sharing options...
carlpeeter32 Posted October 5 Share Posted October 5 I ran into the same "No match found on server" result with Plesk a while back and in my case it turned out the API login WHMCS was using could not actually see the subscriptions. Worth logging into Plesk with those exact API credentials and checking that the subscriptions are listed there — if they are not, the credentials are probably tied to the wrong reseller or owner. Also double check that the usernames in WHMCS match the Plesk usernames exactly, as even a small mismatch stops the match. 0 Quote Link to comment Share on other sites More sharing options...
jessasaurus Posted October 6 Author Share Posted October 6 Iv already check the credentials, im the only admin account on the plesk server, it can't be that 0 Quote Link to comment Share on other sites More sharing options...
jessasaurus Posted October 8 Author Share Posted October 8 Iv already checked all that, when i click the test connection button it comes back successfully 0 Quote Link to comment Share on other sites More sharing options...
jessasaurus Posted October 8 Author Share Posted October 8 Screen shots added 0 Quote Link to comment Share on other sites More sharing options...
jessasaurus Posted November 3 Author Share Posted November 3 Quote Anyone have any ideas ?? 0 Quote Link to comment Share on other sites More sharing options...
jessasaurus Posted November 3 Author Share Posted November 3 from the list accounts response i see the following Array ( [@attributes] => Array ( [version] => 1.6.9.1 ) [webspace] => SimpleXMLElement Object ( [get] => SimpleXMLElement Object ( [result] => Array ( [0] => SimpleXMLElement Object ( [status] => ok [filter-id] => 1 [id] => 1 [data] => SimpleXMLElement Object ( [hosting] => SimpleXMLElement Object ( [vrt_hst] => SimpleXMLElement Object ( [property] => Array ( [0] => SimpleXMLElement Object ( [name] => seo-redirect [value] => none ) [1] => SimpleXMLElement Object ( [name] => ftp_login and more like that in it wont send all of it as it has usernames and password in it as shown in the images i posted plesk is fully up to date!!! (Plesk Obsidian 18.0.81 Update #6) and running WHMCS version 9.0.9 this is the requests WHMCS is sending for list accounts <?xml version="1.0" encoding="UTF-8"?><packet version="1.6.9.1"><!-- Copyright 1999-2016. Parallels IP Holdings GmbH. --> <server> <get_protos/> </server> </packet> <?xml version="1.0" encoding="UTF-8"?><packet version="1.6.9.1"><webspace> <get> <filter/> <dataset> <hosting/> <subscriptions/> </dataset> </get> </webspace> </packet> 0 Quote Link to comment Share on other sites More sharing options...
azzepis Posted November 3 Share Posted November 3 It's because WHMCS developers do not wnat to do nothing after plesk changed it's API. Add this in Plesk in the Panel.ini editor as workaround: [api] oldVersionsSupported = true 0 Quote Link to comment Share on other sites More sharing options...
azzepis Posted November 4 Share Posted November 4 50 minutes ago, Waqas Ahmed Waseer said: On the panel.ini idea: I couldn't find oldVersionsSupported anywhere in Plesk's documentation. The [api] options Plesk documents are things like enabled, allowedIPs and deprecationWarning. And since your requests already go out as 1.6.9.1, a setting for older protocol versions shouldn't change anything here. If you want to try it anyway, back up panel.ini first and take the line out again if the sync still comes back empty. It’s mentioned in the last changelog https://docs.plesk.com/release-notes/obsidian/change-log/ 0 Quote Link to comment Share on other sites More sharing options...
Solution jessasaurus Posted November 4 Author Solution Share Posted November 4 this issues already been sorted by updating WHMCS to verions 9.1.0 and with plesk updated to version 18.0.82 Update #2 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.