Hi Josep, if you're using HTTPS for the web interface, the Graylog REST API must also be accessed via HTTPS to prevent mixed content warnings of your web browser.
See https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content for details about mixed content. Cheers, Jochen On Thursday, 21 April 2016 10:53:36 UTC+2, Josep Maria Comas Serrano wrote: > > We've configured nginx to reverse proxy port 80 to port 9000, and port > 12900 to 12900 > > > To make it work, we've configured > > > rest_transport_uri = http://public_ip:12900/ > > > on graylog's server.conf > > It works fine, > > Now we're trying to reverse proxy port 443 to port 9000, in order to have > ssl enabled on the nginx front-end > > After we enter user & password, nothing happens. It stays forever on the > login dialog page. > > It seems that it's not able to connect to port 12900, but we don't know > why, any ideas about this behaviour? Anything missing on the configuration? > > Best > > JM > > > -- 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/d20c7404-c7d6-4d35-8779-c9912650faa6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
