i'm seeing the same problem. On Thursday, November 3, 2016 at 12:58:27 PM UTC-5, Andrew Morgan wrote: > > I had set it because I am behind a http proxy, is it used for the proxy to > communicate with graylog box? I set it to the internal ip address which the > proxy will use to get to it > > > rest_listen_uri = http://10.1.80.18:9000/api/ > > rest_transport_uri = http://10.1.80.18:12900/ > web_listen_uri = http://10.1.80.18:9000/ > > > there is nothing in the logs that says error: > 2016-11-03T17:54:56.860Z INFO [discovery] [graylog-30cfccc1-68ac-44b4- > a064-64b0f0851faf] graylog2/FimGuUaNSuixYjIxtE4heg > 2016-11-03T17:54:57.055Z INFO [JerseyService] Enabling CORS for HTTP > endpoint > 2016-11-03T17:54:59.863Z WARN [discovery] [graylog-30cfccc1-68ac-44b4- > a064-64b0f0851faf] waited for 3s and no initial state was set by the > discovery > 2016-11-03T17:54:59.864Z INFO [node] [graylog-30cfccc1-68ac-44b4-a064- > 64b0f0851faf] started > 2016-11-03T17:54:59.933Z INFO [service] [graylog-30cfccc1-68ac-44b4-a064- > 64b0f0851faf] detected_master {X-Cutioner}{hzQkdEGvQV2ktep8euZnAQ}{127.0. > 0.1}{127.0.0.1:9300}, added {{X-Cutioner}{hzQkdEGvQV2ktep8euZnAQ}{127.0. > 0.1}{127.0.0.1:9300},}, reason: zen-disco-receive(from master [{X-Cutioner > }{hzQkdEGvQV2ktep8euZnAQ}{127.0.0.1}{127.0.0.1:9300}]) > 2016-11-03T17:55:05.869Z INFO [NetworkListener] Started listener bound > to [10.1.80.18:9000] > 2016-11-03T17:55:05.871Z INFO [HttpServer] [HttpServer] Started. > 2016-11-03T17:55:05.871Z INFO [JerseyService] Started REST API at <http: > //10.1.80.18:9000/api/> > 2016-11-03T17:55:05.871Z INFO [JerseyService] Started Web Interface at < > http://10.1.80.18:9000/> > 2016-11-03T17:55:05.872Z INFO [ServiceManagerListener] Services are > healthy > 2016-11-03T17:55:05.873Z INFO [ServerBootstrap] Services started, > startup times in ms: {KafkaJournal [RUNNING]=13, OutputSetupService [ > RUNNING]=16, BufferSynchronizerService [RUNNING]=29, JournalReader [ > RUNNING]=63, InputSetupService [RUNNING]=105, PeriodicalsService [RUNNING > ]=147, IndexerSetupService [RUNNING]=3301, JerseyService [RUNNING]=9227} > 2016-11-03T17:55:05.873Z INFO [InputSetupService] Triggering launching > persisted inputs, node transitioned from Uninitialized [LB:DEAD] to > Running [LB:ALIVE] > 2016-11-03T17:55:05.877Z INFO [ServerBootstrap] Graylog server up and > running. > > > > but still cant log in > > > > > We are experiencing problems connecting to the Graylog server running on > http://10.1.80.18:12900/. Please verify that the server is healthy and > working correctly. > > You will be automatically redirected to the previous page once we can > connect to the server. > > > On Thursday, November 3, 2016 at 12:40:43 PM UTC-4, Jochen Schalanda wrote: >> >> Hi Andrew, >> >> On Thursday, 3 November 2016 15:24:11 UTC+1, Andrew Morgan wrote: >>> >>> Thank you for your response, honestly I tried a many different ways >>> based on research and I read that it should be the public ip of your >>> instance, so I set it to that. >>> >> >> Okay, but what do you think the setting is for? In your own words. >> >> >> >>> Can you please tell me what it should be . >>> >> >> It should be the URI of the Graylog REST API which can be reached by the >> Graylog web interface (i. e. your web browser) and the Graylog node itself. >> >> Cheers, >> Jochen >> >
-- 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/2a06c0fe-1845-4819-82e1-8a01724bd915%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
