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/5b787b07-bd45-472e-9ba7-8ac0470b9347%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to