On Wednesday 1. June 2016 11.05.59 Renato Pontefice wrote: > Hi Paul, > yes, your idea seem to be correct. > I've just ask to google cloud help, how can I add a firewall rule to route > (but is not a routing) the call fot the external addr (104.155.16.89) to > 127.0.0.1, so the server can answer.
I can't help you there because I don't use the Google cloud. But 104.155.16.89 and 127.0.0.1 are likely to be addresses exposed by different interfaces. You really need to serve Moin on 104.155.16.89 because it is accessible by the external interface. Maybe you could route traffic between the interfaces, but that isn't how most people would solve this. Indeed, it's possible that the internal loopback interface (responsible for 127.0.0.1) isn't even participating in the general routing rules. (At least that's what I see when I run "/sbin/route -n".) > The answer was on my attempt to connect from inside the VM (by lynx) to > addr 127.0.0.1. This already said that the server work and answer... > > Remains the fact that I've not understand how to change the port where the > server werkzung listen Didn't the --host option work? Paul P.S. I don't even use Moin 2, so I just have the documentation to work with, and I honestly can't really justify the time to dig into that documentation or the code any deeper. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Moin-user mailing list Moin-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/moin-user
