Glad to see this has been reported already. I ran into the exact same problem and figured out the same fix too. It would be great if Marvel (and Kibana actually does the same thing I believe) could modify the supplied config.js to use window.location.protocol instead of assuming "http://"; all the time.
Great product though :) Cheers, Will. On Tuesday, January 28, 2014 3:45:04 PM UTC, J. Schulz wrote: > > Hi, > > I have Nginx configured as reverse proxy to access elasticsearch over > https + auth basic. As example > > Unfortunately Marvel tries to connect to http://hostname/. > > The affected code line is in > /usr/share/elasticsearch/plugins/marvel/_site/kibana/config.js > > elasticsearch: "http://"+window.location.hostname+(window.location.port > !== '' ? ':'+window.location.port : ''), > > should be > > elasticsearch: > window.location.protocol+"//"+window.location.hostname+(window.location.port > !== '' ? ':'+window.location.port : '') > > Cheers, > Jonny > -- You received this message because you are subscribed to the Google Groups "elasticsearch" 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/elasticsearch/f9b3cdb7-db59-468e-9c75-a0b95a52c130%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
