I copied the new module into WHMCS, then try to create an account on whmcs get:

Socket error accessing http://centova.mysite.com.br:2199/api.php

Any information about it is welcome.

That means that the server hosting WHMCS cannot open a connection to centova.mysite.com.br on port 2199.  Most commonly this happens if you've mistyped the hostname "centova.mysite.com.br" in WHMCS, or if there's an outbound firewall on your WHMCS machine preventing outbound connections to port 2199 on centova.mysite.com.br.  Or Centova Cast is not in fact running, but I assume you've checked that already.

Thanks Steve, I will check with my host for my main site if 2199 is any blockage. If it was a firewall output, this should not also occur using a module for v2?

That should happen if using the module V2? For with V2 module can perform any operation MAINTENANCE. Except create.

No, if the v2 module is able to connect then it's not a firewall issue... and given that the v3 module works for other folks, it's very unlikely to be a module bug... so I can't see any realistic reason for this issue other than having a typo in your URL in your v3 module configuration.

If a typo it should also affect the module v2 I presume. Since the address registered with WHMCS is the same.

URL:

http://centova10.namedomain.com.br:2199

Something wrong?

If a typo it should also affect the module v2 I presume. Since the address registered with WHMCS is the same.

Right, what I was meant was simply to make sure you've not mistyped it when re-entering it for the v3 module.

You PMed me your CCv3 URL and I'm able to connect to it with no problems with the v3 module from here:

Code: [Select]

<?xml version="1.0" encoding="UTF-8"?><centovacast version="3.0.0b2" host="centova10.xxx.com.br:2199"><response type="error"><message>Invalid username or password</message></response></centovacast>

Obviously it's returning a password error since I don't know your password, but the error you quoted previously indicates that your WHMCS module can't even *connect* to the Centova Cast web server, which I was able to do with no problems.  So I've confirmed that the issue is neither with the module nor with your Centova Cast v3 installation.

Sending restart a server running V3 and V3 module:

WHMCS COMAND RESTART:  Module Command Error
Socket error accessing http://centova10.xxxxxx.com.br/api.php

Sending restart a server running V2.6 and V3 module:

WHMCS COMAND RESTART:  Module Command Error
Socket error accessing http://centova8.xxxxxx.com.br/api.php

Any command with the V3 module, NOT it executes. If the module v2.6 performs basic commands in V3.

I just transfer the extra billing for whmcs modules folder> servers, centovacast.

Sorry Steve, but how could I have written to the error password and get WHMCS restarting the account with the V2 module? So here I should also have a password error.

From already thank you very much for your help. I believe it is the only thing left for me to do the work Centova module in whmcs with V3.

The strange thing is that with the v2.6 module centovacast I can do any operation except create and remove.

Already with the module centovacast v3, do not perform any operation in WHMCS. Any help is welcome.

Only Socket error accessing in module V3.

Just for the record. The problem was the output connection. Turning off the firewall functioned normally.

What are the ports used to connect to WHMCS Centova 3, only 2199 ?