WHMCS > WebSitePanel integration

[Pensive]

Hi All

 

Getting a blank screen when I try and create a WebsitePanel account from WHMCS. I have sent all my settings through to my host who has checked them over and said they are correct.

 

When I add the error message display to configuration.php I get

 

 

Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://XX.XX.XX:9002/espackages.asmx?WSDL' : Start tag expected, '<' not found in /home/thiswebh/public_html/modules/servers/websitepanel/websitepanel.php:0 Stack trace: #0 /home/thiswebh/public_html/modules/servers/websitepanel/websitepanel.php(0): SoapClient->SoapClient() #1 /home/thiswebh/public_html/includes/modulefunctions.php(0) : eval()'d code(1): websitepanel_CreateAccount('http://XX.XX.XX...', Array) #2 /home/thiswebh/public_html/includes/modulefunctions.php(0): unknown() #3 /home/thiswebh/public_html/admin/clientshosting.php(0): ServerCreateAccount() #4 {main} thrown in /home/thiswebh/public_html/modules/servers/websitepanel/websitepanel.php on line 0

 

Any ideas people?

[Pensive]

Turned out to be a firewall issue between WHMCS linux box and websitepanel server.

[vitofun]

Hi pensive, I'm having the same problem right now. Any ideas about how to solve it?

[eseixas]

Hi, I have the same problem. The file the module is trying to access is espackages.asmx, but the correct file should be esPackages.asmx.

I opened a support ticket to correct the module information.

[twdserv]

I am having the following issue, has anyone been able to get a resolution to this. Support is still trying to figure it out as well. They have opened the firewall, so thats not it.

 

Caught exception: SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://:9002/espackages.asmx?WSDL' : failed to load external entity "http://:9002/espackages.asmx?WSDL"

 

- - - Updated - - -

 

I am having the following issue, has anyone been able to get a resolution to this. Support is still trying to figure it out as well. They have opened the firewall, so thats not it.

 

Caught exception: SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://:9002/espackages.asmx?WSDL' : failed to load external entity "http://:9002/espackages.asmx?WSDL"