-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Soap service connection is refused when I call it from a remote machine #18
Comments
Hello maccaron.... I am checking in a remote machine (in a cloud)...and I have some problems with the use of ip address, is not a serious problem...I solve coding and modifying the API code...I am making tests now....If all is OK, tomorrow I upload a new release of the API. I am testing with the Helloworld services.... class HelloWorldService(soaphandler.SoapHandler): I use the targetns_address to especify the address of the service. http://helloword-midom.rhcloud.com/HelloWorldService?wsdl Question, You are using the port 80?.... ThX. Rodrigo. |
Hi Rodrigo, Your service on http://helloword-midom.rhcloud.com/HelloWorldService?wsdl works fine. I invoked it a few times using the same suds client. I did use port 80. However it didn't work. Thanks a lot for the quick response, and I look forward to the update. |
Hello maccaron. There is a problem (a little bug) with the use of port 80 in the code of the API...I hope modify and upload the code today.... Thanks....Rodrigo. |
Hello maccaron. I made change at the code, you can test. You must download the API release 0.9.4.3, from the button "ZIP". I stay waiting yours tests....;) Thank, Rodrigo. |
Hi Rodrigo, I downloaded and installed from the Zip button. I can reach it from a browser, it shows the wsdl schema, but the connection is refused when I use a suds client. The same client worked with your http://helloword-midom.rhcloud.com/HelloWorldService?wsdl webservice. What do you think the problem is? |
Ok, maccaron. Questions: I understand that your server machine and the client are in different network segments. You has tested in two machines (client and server) in the same segment?. tornadows is installed over tornado web server....and uses his network low level functions. You can test with a simple tornado application? for dismiss the problem of tornado. I am looking in the API code some bugs :-)....Today we will testing in two different segment.... ThX. Rodrigo. |
Hi Rodrigo, The client and server were not on the same LAN. They were on separate segments. I don't have two machines on a LAN :). One thing, I'm using an IP address in the 'url' field of the client. Could that be an issue? url = http://XXX.XXX.XXX.XXX:80/HelloWorldService?wsdl Tornado server works fine. I tested with a simple server, and it works. I'm currently running a json Get, Post, Put webservice with tornado for a small application, and there is no problem. |
Hello maccaron. Question: You are using the tagerns_address in the class? In your case: targetns_address = "XXX.XXX.XXX.XXX" class EchoTargetnsService(soaphandler.SoapHandler): ThX, Rodrigo. |
Hi rancavil,
I'm trying to run your example services. They work fine on the same machine, but don't work when the client is on a remote machine. I get error 61 connection refused every time.
I did open the port on the firewall, and it still doesn't work.
The text was updated successfully, but these errors were encountered: