Hmm, this does not work properly in the end. On Monday, August 15, 2016 at 6:24:19 PM UTC+2, Fred Blaise wrote: > > As a workaround, in a screen session, I am redirecting with netcat, such > as: > > while true; do nc -l 192.168.x.y 12900 | nc 213.244.x.y 12900; done > > Does the job, but well. > > Thanks, > fred > > On Monday, August 15, 2016 at 6:09:43 PM UTC+2, Fred Blaise wrote: >> >> Hello, >> >> I am using the openstack 2.0.3 qcow2 image on a single instance. I am >> having issues when specifying the rest_listen_uri to http://0.0.0.0:12900 >> . >> I need to have the API port available for both the web UI and >> graylog-sidecar clients, which are on 2 different networks. >> >> The graylog server instance has 2 interfaces system bound: the public >> one, and a private one (192.168.x.y). >> >> The other instances of that tenant have an interface for the private >> network (and possibly a floating IP, thus not bound at system level). >> That's the interface they use when they send logs to graylog, especially >> with graylog-sidecar which requires port 12900. >> >> The Web UI is accessed via the public IP. So I need to have port 12900 >> available there as well. >> >> Despite the network socket well listening on 0.0.0.0:12900, the Web UI >> is no longer loading, because it tries to reach port 12900 on the internal >> interface at http://192.168.x.y:12900. >> >> Is this a bug? If not, what do you advise? >> >> Thank you. >> Best, >> fred >> >> >> >> >>
-- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/63b9d622-42fb-4ace-b5b1-0d1f621c0d5f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
