enom module connection problem

[ditto]

Is anyone else having trouble with the enom modules recently? I am running the newest version of whmcs, and I am running php 5.4.16 and apache 2.4.4

 

When I try to view a enom domain in WHMCS, the page just hangs loading forever and nothing happen. This also causes 100% cpu usage.

 

I enabled Module Debug Log and it shows under "action" getdns, and under "requests" is say (I have replaced DOMAIN): uid=*********&pw=****************&tld=com&sld=DOMAIN&command=getdns& and last under column "response" it is empty, nothning there.

 

So I am not able to open any enom domains page in whmcs any longer. I have sent whmcs a ticket on this. I have asked enom, and they say there is no known proplem with the api at the moment.

 

I even disabled enom module in whmcs, and then tried to navigate to a enom domain in whmcs, but still the same thing happen, the page just load forever and nothing happen, and 100% cpu usage again.

Edited June 25, 2013 by ditto

[ditto]

I just received a nonsense reply from whmcs support. I get so angry when they send me replies like that. No help what so ever.

 

Edit: I have asked eNom to provide a traceroute from reseller.enom.com to my server, I suspect it is my datacenter that is blocking eNom reseller ip. However, the eNom module is buggy, it should not cause 100% cpu usage only because the reply from eNom is not comming through.

Edited June 25, 2013 by ditto

[WHMCS John]

Hi,

I'm sorry to hear you were not satisfied with the response from our support team. If you would kind enough to PM the ticket ID to me along with your feedback I'd be pleased to receive it.

 

Regarding the problem at hand, the behaviour you're seeing here does suggest a connectivity issue between your server and eNom's API.

[ditto]

I am still angry at WHMCS. And WHMCS should pay me for providing the solution in this reply, and for the idiotic support I was provided. I have closed the support ticket, I will not speak to any of your support team ever again. The problem was that enom api is not compatible with newest curl 7.31, I have posted the details about it in DirectAdmin forum here http://forum.directadmin.com/showthread.php?t=46801

 

So, there you go, the solution. I will now unsubscribe from this thread. Edit: The idiotic reply to my support ticket was by "Lawrence"

Edited June 27, 2013 by ditto

[ditto]

And here is the reply:

 

Hello,

 

The performance of a PHP script is based on your server. WHMCS is a fairly lightweight PHP & MySQL software. While it has a large amount of features in it, it's only running such features when called upon by a user, thus the resources that it requires and uses are provided by the server itself. It's common that additional hooks & addons can make WHMCS slower than desired. I would recommend disabling any that are installed and see if that helps. If it does, I would recommend re-enabling them one by one until the issue returns. The last enabled one will be the likely cause and you will need to contact the author to investigate and fix it.

 

If the above does not help, you will want to have your web host or server admin review your server logs to assist with performance related issues, particular your web server (Apache, IIS, etc.) and your MySQL server.

 

If you have any other questions, please feel free to contact us again!

 

Regards,

 

Lawrence

Customer Support

[WHMCS John]

Hi,

I'm pleased to hear you were able to resolve the issue with your server/eNom's API and thanks for providing the follow-up.

 

The invitation for you to provide the Ticket ID is still open and I'd be pleased to review the ticket. It really all depends upon what information you provided in the ticket, as I'm sure Lawrence felt his response was appropriate based upon what we knew at the time.