yeah ; I figured out ; actually somehow I deleted TCP:80 from my security group (I guess lack of sleep made me a zombie )
On Mon, May 5, 2014 at 9:36 PM, Mark Walkom <[email protected]>wrote: > You can find an example reverse proxy config for nginx here - > https://github.com/elasticsearch/kibana/blob/master/sample/nginx.conf > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [email protected] > web: www.campaignmonitor.com > > > On 6 May 2014 11:34, Nish <[email protected]> wrote: > >> Have you figured out a solution ? >> I am getting this all of a sudden ! >> I can access it ok via ip address but not via kibana via nginx rev proxy >> .. >> >> On Monday, March 24, 2014 9:48:21 AM UTC-4, Dušan Đorđević wrote: >>> >>> Hi, >>> >>> I downloaded elasticsearch-1.0.1.noarch.rpm, >>> logstash-1.4.0-1_c82dc09.noarch.rpm >>> and kibana-3.0.0.tar.gz from >>> http://www.elasticsearch.org/overview/elkdownloads/ and installed them >>> on RHEL 6 with Apache and self signed http cert. >>> >>> I replaced default Kibana dashboard with logstash dashboard that comes >>> with Kibana (cp logstash.json default.json in kibana/app/dashboards) >>> >>> When I connect from another machine's browser to >>> https://10.142.4.104/kibana I get following error message: >>> >>> Could not reach http://10.142.4.104:9200/_nodes. If you are using a >>> proxy, ensure it is configured correctly >>> >>> However from that same machine curl http://10.142.4.104:9200/_nodesworks >>> without any problems, and one with pretty output also: >>> >>> curl 10.142.4.104:9200/_nodes/process?pretty >>> { >>> "cluster_name" : "aerlingus", >>> "nodes" : { >>> "avemXrb9SB6lxgxgL54ecA" : { >>> "name" : "central-log-server", >>> "transport_address" : "inet[/10.142.4.104:9300]", >>> "host" : "central-log-server", >>> "ip" : "10.142.4.104", >>> "version" : "1.0.1", >>> "build" : "5c03844", >>> "http_address" : "inet[/10.142.4.104:9200]", >>> "attributes" : { >>> "master" : "true" >>> }, >>> "process" : { >>> "refresh_interval" : 1000, >>> "id" : 28121, >>> "max_file_descriptors" : 65535, >>> "mlockall" : false >>> } >>> } >>> } >>> } >>> >>> Any idea what might be the problem ? >>> >>> Thanks, >>> Dusan >>> >> -- >> 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/78e8b516-dad7-4ede-9cb1-c2970c250d51%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/78e8b516-dad7-4ede-9cb1-c2970c250d51%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CAEM624buhQgcYJ-_wT%2B%2BVK3agQuWfrSc2AYxQ3%2B1aN9UHV%3DMWQ%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAEM624buhQgcYJ-_wT%2B%2BVK3agQuWfrSc2AYxQ3%2B1aN9UHV%3DMWQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CANma5K7O0n6vrePxvW0fOh2%2BS0Dq2oQTvobkYW6y-r4o_s26zQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
