I got some issue with my whmcs module and Solidcp.
I am using Solidcp purely for only hyper-v services. Now the problem I got on my few nodes are that though whmcs terminates accounts on solidcp but VMs remain in host node. Is there any fix for this ? If I delete VMs manually from solidcp it works but whmcs is not terminating VMS it just terminates solidcp accounts.
Any help would be appreciated.
Currently this is a known bug for the WHMCS module. I am not aware of a workaround at this time.
The issue is not with the WHMCS module, but with the termination of the service in SolidCP. The WHMCS module is using the standard API calls for termination of a service in SolidCP, doesn’t matter which services are provisioned. It’s the same behavior, like you would terminate/cancel the service via SolidCP. While for example exchange mailboxes will be deleted successfully, there is a lack of implementation, what should happen with VMs in the VPS service while termination.
I wanted to create a workaround in the WHMCS module for it, but to be honest, you will need to create a workaround for every provider, which hasn’t implemented termination/cancel tasks for the existing resources.
Not to add any more confusion to this post but: I did think the Hyper-v termination was fixed with version 1.4.3 inside SolidCP it self.
Can you verify you run the latest version of SolidCP : 1.4.3 ?
Yes, I am using SolidCP 1.4.3.
Actually I have master panel and added all other nodes as a slave on the panel.
We are in the same boat, except that it occurs the day (today) we upgraded WHMCS from 7.5.1 to 7.8.3.
@Sam you posted in July so it is safe to assume you were on current stable version WHMCS 7.7.1 or so?
Did you happen to fix the issue ?
I just wanted to provide you with an update.
@HostStage has been busy looking at this with WHMCS and they sound there was a issue in another hook unrelated to SolidCP. WHMCS are now reporting that this has been fixed in newer versions.
Actually, I was running Solidcp v 1.4.2 and after updating to solidcp 1.4.3 it was fixed so I guess it is not working with 1.4.2 but module works flawlessly on 1.4.3
- Views1123 times
- Answers7 answers