Yes, the transport uri should be the external address of the interface. A bug fix changed the autodetection a little, which we will improve in 0.20.3 soon.
You can also force java to use ipv4 instead of ipv6: http://support.torch.sh/help/kb/graylog2-server/installing-graylog2-server-v020x-on-nix-systems#problems-with-ipv6-vs-ipv4- Best, Kay On Jun 4, 2014 12:20 PM, "Giles Coochey" <[email protected]> wrote: > On 04/06/2014 10:53, [email protected] wrote: > >> Hi Giles, >> >> Thanks 4 your replay,, :-) >> >> I thought of disabling IPV6, having the experience this get me some more >> trouble in the past. >> So I disabled IPV6 and did the trick for enabling the graylog-web >> service. It works. >> >> But I have to put this up in te server.conf file: >> rest_transport_uri =http://127.0.0.1:12900/ >> >> > I think that what you have in server.conf rest_transport_uri line should > match what you have in web.conf graylog2-server.uris > > If you use localhost (127.0.0.1) or an actual IP would depend on whether > you have multiple servers in a cluster? > > -- > Regards, > > Giles Coochey, CCNP, CCNA, CCNAS > NetSecSpec Ltd > +44 (0) 8444 780677 > +44 (0) 7983 877438 > http://www.coochey.net > http://www.netsecspec.co.uk > [email protected] > > > -- You received this message because you are subscribed to the Google Groups "graylog2" 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/d/optout.
