After some digging, many Azure deployments and generally a lot of time spent it turns out that the internet provider blocked websocket connections on port 80 and 8080 (secured websockets worked though). I have just tested my app through my own network setup and provider and it appears to work fine from there. For me the takeout is that a solution like socket.io that can fallback to more conventional HTTP based connections is very valuable in that it helps to circumvent these sorts of issues.
Thanks to Glenn who helped me along the way by suggesting solutions, testing and eliminating other possible issues! -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" 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/nodejs?hl=en?hl=en
