Hi Jochen These were the only variables that were changed from vanila graylog.conf.example file (some values removed) password_secret root_password_sha2 root_email rest_listen_uri = http://10.20.2.75:9000/api/ allow_leading_wildcard_searches = true allow_highlighting = true elasticsearch_cluster_name = graylog stream_processing_timeout = 5000 stream_processing_max_faults = 10 rules_file = /etc/graylog/server/rules.drl
transport_email_enabled = true transport_email_hostname transport_email_port transport_email_use_auth = false transport_email_use_tls = false transport_email_use_ssl = false transport_email_subject_prefix = [graylog] transport_email_from_email transport_email_web_interface_url Are there additionally any error messages in the Developer Console > <https://developers.google.com/web/tools/chrome-devtools/> of your web > browser when opening http://10.20.2.75:9000/api/ > <http://www.google.com/url?q=http%3A%2F%2F10.20.2.75%3A9000%2Fapi%2F&sa=D&sntz=1&usg=AFQjCNEIF_dkP-1zWRCJngoxV9dgST_KCQ> > ? There were none I managed to get the Web Interface showing after making the following changes to the conf file. rest_listen_uri = http://0.0.0.0:9000/api web_listen_uri = http://0.0.0.0:9000/ I think web_listen_uri was the key, haven't tried reverting rest_listen_uri. One other change I had to make was removing the AWS plugin graylog-plugin-aws-1.0.0.jar I noticed some warnings in the logs WARN : org.graylog.aws.processors.instancelookup. AWSInstanceNameLookupProcessor - AWS plugin is not fully configured. No instance lookups will happen. Not sure if it had any relevance. Thanks for the follow up. On Monday, August 29, 2016 at 10:49:17 AM UTC-4, Jochen Schalanda wrote: > > Hi, > > please post the complete Graylog configuration file and the complete > Graylog log file. > > Are there additionally any error messages in the Developer Console > <https://developers.google.com/web/tools/chrome-devtools/> of your web > browser when opening http://10.20.2.75:9000/api/? > > Cheers, > Jochen > > On Friday, 26 August 2016 23:06:48 UTC+2, 123Dev wrote: >> >> Just upgraded to graylog-2.1.0-rc.1 using graylog-2.1.0-rc.1.tgz >> >> Web Interface does not come up on http://<ip_address>:9000 >> however API endpoint http://<ip_address:9000/api responds with >> >> {"cluster_id":"e9d051a9-c3db-4102-9fa3-0856d2269cfb","node_id": >> "da80dd2b-6735-4788-bcd7-e94cdacc3bc2","version":"2.1.0-rc.1+f7cb92f", >> "tagline":"Manage your logs in the dark and have lasers going and make >> it look like you're from space!"} >> >> >> >> Looking at browser developer options, I see that config.js is not found >> (404) >> and same goes for assets\vendor.js (404) and other scripts it tries to >> load from assets >> >> The previous version ( Graylog 2.0.2) is not having any such issues, and >> is loading vendor.js and other js-es from the root and not from assets >> Not sure if this is a bug or a mis-configuration on our part, but the >> config is quite vanila with only *significant *change from the example >> is: >> rest_listen_uri = http://10.20.2.75:9000/api/ >> >> >> Graylog log doesn't show any errors >> >> Any idea what it might be. >> I'll turn off some of the plugins that were enabled in 2.0.2 and see if >> any of those makes a difference. >> Anything persistent in MongDB that could cause this? >> >> Thanks >> >> >> -- 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/939060b7-7715-45d7-a7d4-f3df52aa28e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
