And, to come at it from the other direction, you can remove Turbogears from the equation and test your ability to connect to that port from the outside world. Simply run:
netcat -l -p 8080 on the server machine, and then: telnet <server machine> 8080 from your client test machine. And type to yourself. If it works, then the problem is with Turbogears (or some configuration surrounding its execution). If not, the problem lies with your network configuration (firewalling, most likely). Stuart On Tue, 2006-10-17 at 18:38 -0700, venkatbo wrote: > Chris, > > To rule out issues with your app itself, as a test, > you may want to try accessing the tgadmin app. > > This assumes tg-admin was deployed to the system > running your app. If not, temporarily, for this test, > you can add it to say ..../python/bin on that system. > And remove it after the test (for security reasons). > > . ssh to the system that's running your app. > . cd to the TG dir of your app (that with .cfg's and > start-<app>.py) > . ensure the approp .cfg says: > [global] > server.log_to_screen = True > . start tg-admin: > $ tg-admin toolbox -c <ip-addr-of-the-browser-box> > (assumes it is reachable) > . Should see some logging directed to the term > . launch a browser from the box that was granted > access (above) and go to: > http://<ip-addr-of-TGapp-box>:7654 > . Should see the toolbox start page. Access some > of the links and see if it works. The term will show > some logs. > > hth, > /venkat > > > > > -- Stuart Clarke <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
