[sean89]

Hey, I am trying to use the integration API with my Kayako Support Suite. When I execute the example script I get the following:

SOAP Error

wsdl error: HTTP ERROR: Couldn't open socket connection to server *domain and path to my file*, Error (110): Connection timed out

I have ensured that the url to the index.php file is correct and it is correct in config.php as well as on the $url in the example script.

Please help as I am completely stumped on how to fix this.

Thanks a lot!

[Andrew Gillard]

Are you using your SOAP client and the SOAP server (i.e. Kayako) on the same server? Some networks aren't set up properly for loopback (ones which use NAT, I think, which is pretty rare in commercial servers, but would be an issue if you're using a server behind a home Internet connection), which prevents servers connecting to themselves using their public IP address. If that is the case, you should probably be using the native PHP class, unless your client isn't written in PHP. Alternatively you could try using "localhost" instead of the URL in the client.

If the above doesn't apply, I would start troubleshooting this by ensuring that the client gets the correct IP address for the server from DNS. Checking that will be easier if you have SSH/RDC access to the client machine rather than just FTP and some Web control panel. If the DNS lookup works fine, try pinging the server or accessing some other page on the server from the client. There could theoretically be some kind of firewall or routing issue going on. It's also possible that your client machine isn't allowed to initiate HTTP connections for whatever reason (an attempt at security, perhaps?).

[sean89]

The client and the SOAP server are indeed on the same server. Kayako is coded in PHP and my application is coded in Python. Do you know how I can set it up properly to do the loopback or even something I can type into Google to find out more?

[Andrew Gillard]

I would suggest trying the URL as "localhost" instead of your server's hostname. Whether that works or not would depend upon your webserver configuration, though.

Alternatively you could modify your server's hosts file (C:\Windows\System32\drivers\etc\hosts on Windows, /etc/hosts on Unix/Linux [and possibly Mac] systems) to have your server's hostname point at 127.0.0.1:

CODE

127.0.0.1     www.my-hostname.com

[sean89]

Will try, thanks!