RE: [MODULE] WHMCS
06-09-2015, 06:00 PM
(This post was last modified: 06-09-2015, 07:07 PM by Rynoxx.)
(06-09-2015, 11:34 AM)HogensHero Wrote: Hello,
I am running Sentora on Centos 6.6 and I installed the whmcs module. Once I installed the module and edited the module edit rights in the module admin tool, I had to re-log into Sentora. Upon logging back into the panel it said module not found and the entire panel was blank. Could you test this with Centos 6.6 and patch it please.
Edit:
After I went and looked for that error in the forums I found a post to recompile the database. So I removed the module and recompiled the database. On a whim, I reinstalled the module and now it is working. Now the issue that I am having is the directions on how to configure everything. I read your read.me on the github and I am still not getting the sites set up.
The error I am getting is "Account couldn't be created, the API Request failed." I am not sure if it is because I left out the name servers. This is where I am confused, I am using cloudflare and they have weird name servers. Should I put those in?
HogensHero
When it comes to the Nameservers, put the ones you've got from Cloudflare even if the names are weird.
And the reason the request failed is because the WHMCS module isn't getting a proper response, not entirely sure why, but one reason could be that you've put the wrong API info in WHMCS, for now I'll add a simple debug that outputs the PHP error to whmcsdirectory/admin/sentora_module_error.txt
I'll test myself to see what I can do to resolve this as well. And soon I'll fix so that my module uses the WHMCS Module debug system to ease the debugging in situations like these.
Edit: Here's a link to the new version of sentora.php (put it in whmcsdirectory/admin/modules/servers/sentora/) https://raw.githubusercontent.com/Rynoxx...entora.php
Edit2: HogensHero I've added support for the WHMCS debug log, enable it in WHMCS and give me the output of the debug log, unless you're capable of fixing the error yourself (one being invalid API information)