I'm wondering why opening the port via security group is not sufficient? For me running a service on a different port than the one open by defaut with default role was just a matter of opening additionnal ports, isn't it?
On Tue, Jul 28, 2009 at 6:02 PM, Nickolas Toursky <[email protected]> wrote: > > Hi Martin, > > You have numerous options here, depending on what do you wish exactly. > > 1. Make port 8080 of application servers accessible by > http://mydomain.com/: > Create a file /etc/nginx/app.conf, with a line APP_PORT="8080". > > 2. Make it accessible via http://jetty.mydomain.com/: > Assign this application to www instance, then edit > /etc/nginx/nginx.conf to forward this particular hostname to app > server's port 8080. > > 3. Make it accessible via http://jetty.mydomain.com:8080/: > Assign an application to app role. > > Nick > > > 2009/7/28 Martin Sweeney <[email protected]>: > > > > I have Jetty (http://jetty.mortbay.org/) running on port 8080 on my > > app server (no load balancer) on farm #2127. > > > > If I browse internally http://localhost:8080 I see the correct page, > > but any attempt to view the port externally (http://mydomain.com:8080) > > just times out. > > > > nmap tells me the port is open > > > > Any pointers on how to expose this port to the outside world, or...if > > I'm completely off track with this? > > > > Martin. > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" 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/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
