PHP Fatal Error whe...
 
Notifications
Clear all

PHP Fatal Error when Cronjob Runs

4 Posts
2 Users
0 Reactions
996 Views
Posts: 2
Topic starter
(@affituk)
New Member
Joined: 7 years ago

Morning All!

We have been having an issue with our WHMCS to SolidCP connection recently and can't seem to get to the bottom of it. When the cron runs we get the following error message:

*Note that * is an actual domain name which I have edited out for the purposes of this post.

PHP Fatal error:  SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://*:9002/esUsers.asmx?WSDL' : failed to load external entity " http://* :9002/esUsers.asmx?WSDL"

in /home/*/domains/*/public_html/hosting/modules/addons/solidcp_module/lib/enterpriseserver.php on line 519 PHP Fatal error:  SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://*:9002/esUsers.asmx?WSDL' : failed to load external entity " http://* :9002/esUsers.asmx?WSDL"

We have tried opening up the firewall completely between the two servers but this still doesn't appear to help matters. When we navigate to http://*:9002/esUsers.asmx?WSDL in a web browser it loads the XML file without any issues.

SolidCP Is running in a Windows Server 2016 Environment and WHMCS is running in a DirectAdmin environment on a Centos 6 linux box. Environment is build within Amazon Web Services.

Any advice or pointers in the right direction would be greatly appreciated!

Thanks,

George

3 Replies
Posts: 1967
Admin
(@m-tiggelaar)
Noble Member
Joined: 9 years ago

Hello,

From the error it appears it's having issues contacting SolidCP Enterprise.

can you verify the bindings in IIS Management are correct? (by default it's 127.0.0.1:9002 which means it only works on the server it self not an external server).

Regards,

Marco

Reply
Posts: 2
Topic starter
(@affituk)
New Member
Joined: 7 years ago

Hi Marco,

Thanks for the reply - the bindings for the Enterprise Server are:

127.0.0.1:9002

*:9002

 

I believe that the * binding was added in as we were not able to access  http://****:9002/esUsers.asmx?WSDL without it in there.

Reply
Posts: 1967
Admin
(@m-tiggelaar)
Noble Member
Joined: 9 years ago

Yes, the * 9002 would be custom (but required if you want to connect from an external whmcs server).

In that case the only other aspect i can imagine is the url's not exactly matching or not resolveable for the whmcs server (what you can do is see if you can ping it for example from the linux server to the address listed in the error, etc).

Reply
Share: