Tbh, this is actually running on an undisclosed public IP address. The server is only being used for small tests, so I do consider it somewhat disposable. Even then, I should look into isolating it's exposure with some stricter iptables rules. On Apr 18, 2014 3:28 PM, <m.roth at 5-cent.us> wrote: > Hal Wigoda wrote: > > > > Your network config > > needs attention > > > >> On Apr 18, 2014, at 10:13 AM, Evan Rowley <rowley.evan at gmail.com> > wrote: > <snip> > >> Here is some of the output: > >> > >> [appengine at centos6-paas-dev gotour]$ gotour > >> 2014/04/17 22:04:33 Serving content from > >> /home/appengine/goprojects/firstproj/go/src/code.google.com/p/go-tour > >> 2014/04/17 22:04:33 > >> WARNING! WARNING! WARNING! > >> I appear to be listening on an address that is not localhost. > >> Anyone with access to this address and port will have access > >> to this machine as the user running gotour. > >> If you don't understand this message, hit Control-C to terminate this > >> process. > >> WARNING! WARNING! WARNING! > >> 2014/04/17 22:04:34 Please open your web browser and visit > >> http://10.10.10.205:12049 > <snip> > Is that 10.10.10.205 on your internal network, or is it the host's visible > to the guest network? Have you gone there? > > mark > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >