Hi Glenn, yes, it looks indeed as if your reverse proxy is broken (or rather the whole system is kind of misconfigured).
Please refer to http://docs.graylog.org/en/2.0/pages/configuring_webif.html for working instructions for setting up the web interface in Graylog 2.x (including working configurations for nginx and Apache httpd). Cheers, Jochen On Thursday, 2 June 2016 20:28:17 UTC+2, Glenn Mate wrote: > > Having the same issue as well. Curling localhost:12900/system/sessions > shows the is_valid:false return, so I know the API is answering locally. > However, curling the example.com:12900/system/sessions leaves me with > (35) Unknown SSL protocol error in connection. I believe this may be > related to my nginx reverse proxy... > > On Wednesday, May 18, 2016 at 12:47:41 PM UTC-4, Chris Chalmers wrote: >> >> Hi All, >> >> I recently installed Graylog 2 using this guide: >> http://www.systeen.com/2016/05/12/install-graylog-2-0-centos-7-collect-windows-logs/ >> >> It was working for a couple of days I added around 10 Windows servers >> using NXLog and could see all of the events coming in. Since this morning >> when I go to the webpage I can't get passed - >> >> Error messageBad requestOriginal RequestGET >> http://10.251.0.90:12900/system/sessionsStatus 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. >> >> I have restarted the individual services (graylog-server, elasticsearch >> and mongod), restarted the server, disabled iptables and selinux is >> disabled. >> >> The logs all look clean >> - /var/log/graylog-server/server.log, /var/log/elasticsearch/graylog.log >> and /var/log/mongodb/mongod.log. >> >> Has anyone else come across the same issue? Are there any other logs I >> can look at? >> >> Thanks, >> >> Chris >> > -- 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/93626254-2168-4003-9103-5051af616631%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
