Hi Ovidiu, please post the contents of your Graylog configuration file. Also make sure that your browser cache isn't using a stale version of the web interface assets (specifically the configuration provided by /config.js).
Cheers, Jochen On Tuesday, 29 March 2016 10:16:22 UTC+2, Ovidiu Pacuraru wrote: > > I fiddled some more and set this to my public domain instead of localhost > or 127.0.0.1 > rest_listen_uri = http://mdomain.tld:12900/ > > And I now briefly see the login form when hitting mydomain.tld:9000 > immediately followed by this but no clue why it is still looking at > 127.0.0.1:12900 when I have already changed that to my domain > It seems to work but cannot log in via web, getting: > *Server currently unavailable. We are experiencing problems connecting to > the Graylog server running on http://127.0.0.1:12900// > <http://127.0.0.1:12900//>. Please verify that the server is healthy and > working correctly.* > Which doesn't make sense to me as I cannot find any errors in the logs. > > Clicking on more details, I see: > > Error messageBad requestOriginal RequestGET > http://127.0.0.1:12900/system/cluster/nodeStatus codeundefinedFull error > messageError: Request has been terminated Possible causes: the network is > offline, Origin is not allowed by Access-Control-Allow-Origin, the page is > being unloaded, etc. > -- 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/3f2f5b85-38a2-477d-8eeb-19a1abcb0799%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
