-
Notifications
You must be signed in to change notification settings - Fork 288
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
CherryPy: simple example of an echo server #140
Comments
Hi @JacquesBopp, do you an error in the server's logs when you start up the server? Would you mind showing me your config? By the way, I would rather you use the ws4py mailing-list for questions like that. I prefer keeping issues on github for bugs :) Thanks! |
Hi, Thank’s for your reply. I’ve managed to run the example. Instead of using the address “services.newsdetector.net” I use the IP-Adress. Et voilà: it worked. I’ve joined the ws4py mailing-list and will post my next questions there. Kind regards, Jacques Bopp From: Sylvain Hellegouarch [mailto:notifications@github.com] Hi @JacquesBopp https://github.com/JacquesBopp , do you an error in the server's logs when you start up the server? Would you mind showing me your config? By the way, I would rather you use the ws4py mailing-list for questions like that. I prefer keeping issues on github for bugs :) Thanks! — |
The demo bind the socket on 127.0.0.1. You can either try localhost or 127.0.0.1, but any others address that don't resolve to 127.0.0.1 wont work for the example. |
Hi, I tried your "simple example of an echo server" for CherryPy but I always get Errno 10060. I used exactly the same code as in the example. My CherryPy (version 3.5.0) server runs on a Webfaction server. Url and port used on the client side are 'ws://services.newsdetector.net:10510/ws'. If I run the client locally in a Putty session using 'localhost' and port 10510 everything works fine. I opened the port in the server firewall, so the firewall should not be the problem. Do you have any ideas what's going wrong?
Thank's for your response,
Jacques Bopp
The text was updated successfully, but these errors were encountered: