Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Could not reach http://192.168.0.110:888888880/_nodes. If you are using a proxy, ensure it is configured correctly #2452

Closed
samarthsikotara opened this issue Dec 23, 2014 · 1 comment

Comments

@samarthsikotara
Copy link

When I started kibana using http://192.168.0.110:80, Kibana shows me blank dashboard with red alert.
and my config.js file is below. let me know what i am doing things wrong.

/** @scratch /configuration/config.js/1
*

  • == Configuration

  • config.js is where you will find the core Kibana configuration. This file contains parameter that

  • must be set before kibana is run for the first time.
    */
    define(['settings'],
    function (Settings) {

    /** @scratch /configuration/config.js/2
    *

    • === Parameters
      */
      return new Settings({

      /** @scratch /configuration/config.js/5
      *

      • ==== elasticsearch
        *
      • The URL to your elasticsearch server. You almost certainly don't
      • want +http://localhost:9200+ here. Even if Kibana and Elasticsearch are on
      • the same host. By default this will attempt to reach ES at the same host you have
      • kibana installed on. You probably want to set it to the FQDN of your
      • elasticsearch host
        *
      • Note: this can also be an object if you want to pass options to the http client. For example:
        *
      • +elasticsearch: {server: "http://localhost:9200", withCredentials: true}+

      */
      elasticsearch: "http://"+window.location.hostname+":80",

      /** @scratch /configuration/config.js/5
      *

      • ==== default_route
        *
      • This is the default landing page when you don't specify a dashboard to load. You can specify
      • files, scripts or saved dashboards here. For example, if you had saved a dashboard called
      • `WebLogs' to elasticsearch you might use:
        *
      • default_route: '/dashboard/elasticsearch/WebLogs',
        */
        default_route : '/dashboard/file/default.json',

      /** @scratch /configuration/config.js/5
      *

      • ==== kibana-int
        *
      • The default ES index to use for storing Kibana specific object
      • such as stored dashboards
        */
        kibana_index: "kibana-int",

      /** @scratch /configuration/config.js/5
      *

      • ==== panel_name
        *
      • An array of panel modules available. Panels will only be loaded when they are defined in the
      • dashboard, but this list is used in the "add panel" interface.
        */
        panel_names: [
        'histogram',
        'map',
        'goal',
        'table',
        'filtering',
        'timepicker',
        'text',
        'hits',
        'column',
        'trends',
        'bettermap',
        'query',
        'terms',
        'stats',
        'sparklines'
        ]
        });
        });
@rashidkpc
Copy link
Contributor

Given that error message I'd wager something is wrong with your configuration, or perhaps you have a proxy performing some sort of strange redirect? Feel free to drop by #kibana on Freenode for interactive troubleshooting, Github issues are for bug reports and feature requests only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants