On Wed, Aug 7, 2013 at 2:00 AM, zka <[email protected]> wrote: > Hi, > > As describe here : > https://blog.heroku.com/archives/2013/5/2/new_dyno_networking_model > >> The new dyno networking model brings us closer to that goal: The dyno no >> longer imposes any restrictions on what ports an application can listen on. >> This improves out-of-the box compatibility with application frameworks that >> listen on multiple ports (for whatever reason). You can still only connect >> from the outside world to the port specified in the $PORT environment >> variable, but now you don't have to painfully reconfigure your web stack to >> stop it from listening on other ports. In other words, if it worked on your >> local environment, there is now one less reason it might break on Heroku. > > > > I test to deploy an app listening on port 9000, and fail to access it : > > http://pure-island-8483.herokuapp.com:9000 > > How can i make it work ?
Those ports per the blog are not open to the outside world (save $PORT, which is routed), rather, the use case that is designed for is to allow cross-process communication within exactly one dyno (read: "container") without port clashing with unrelated neighbors. It probably could have been better explained. -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
