pfinucan

Hi, As a test I install whm on a ec2 small instance. The install seemed to go fine, but the web interface is extremely slow, to the point of being unusable. Is it unreasonable to run whm on a ec2 small instance, even as a test without any sites? iostat Linux 4.9.20-10.30.amzn1.x86_64 (xxxx) 04/11/2017 _x86_64_ (1 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 3.53 0.08 0.33 0.46 0.07 95.54 Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn xvda 8.83 248.90 477.88 8082449 15518032 loop0 0.00 0.04 0.00 1312 4

While doing what seems like a straightforward client update external API call, the response is returned as successful but nothing is changed in the system. The response also returned the client id as null. Example Request Query: (I'm using guzzle to post) array (size=1) 'query' => array (size= 'username' => string 'xxx' (length= 'password' => string 'xxx' (length=32) 'responsetype' => string 'json' (length=4) 'action' => string 'updateclient' (length=12) 'clientid' => int 1266 'firstname' => string 'Test' (length=7) object(stdClass)[113] public 'result' => string 'success' (length=7) public 'clientid' => null Just as a test I removed the clientid from the post fields and I get the expected error: object(stdClass)[113] public 'result' => string 'error' (length=5) public 'message' => string 'Client ID Not Found' (length=19) So is there any undocumented restricts to updating client details or is this a bug?

I understand that part of the problem we were having was that the last invoice requirement is not documented. But I believe there still is a bug. The bug comes from the fact that if you add payment information before you add an order you can NEVER save client payment information to the gateway. Even after adding a order with the payment gateway specified.

... anyone?

Context: WHMCS API with Authorize.net CIM payment Gateway How to test bug. Use API to create a new client with optional fields for credit card filled out. API reports success. Review gateway transaction log to and confirm no gateway transaction was created. Confirm payment gateway does work: Use the API Update Client function to update credit card details of client that wasn't created through the API. API reports success. Review the gateway transaction log and see the "UpdateCustomer" action reported. Test with API Created Client Use the API Update Client function to update credit card details of client that was created through the API. API reports success Review the gateway transaction log and see no transaction were created. Trying to capture payment on a client created with the API always throw a "No Client Profile ID Found" in the gateway transaction log.

Hi, Our authorize cim works fine when using the admin section but doesn't seem to work using the whmcs api. The API "create client function" seems to work, including adding CC information. But no client created through the API can successfully submit a payment. The error in the gateway is "No Client Profile ID Found". Which makes it seem like the client isn't being created in the CIM. How do you create a billable client with the API? After creating a client with the api I can manually add a the same CC through the admin section and then capture a payment. This creates a "Action => CreateCustomer" in the gateway log. This doesn't happen when updating the client through the API. What is the right way to use the API to create new users?