Connection Failed : Your elasticsearch server is down or unreachable


Hello there,

I am currently doing an internship in which I need to have my VM installed with specific versions of ELK products. I got Kibana 3.1.2, Nginx, Elasticsearch 1.7.3, and Logstash 2.1.0 installed by myself, and the Linux version is Redhat.

Chrome: When I try http://x.x.x.x/ on Chrome, I got an error "Connection Failed
Possibility #1: Your elasticsearch server is down or unreachable"[...], and the browser is showing "GET http://x.x.x.x/app/dashboards/default.json?1457344328763 net::ERR_CONNECTION_REFUSED" in the console
Firefox: When I try http://x.x.x.x/ on Firefox, I got the Nginx welcome page "Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required."[...]

http://x.x.x.x:9200 shows this:

"status" : 200,
"name" : "bam_guillaume",
"cluster_name" : "bam_guillaume",
"version" : {
"number" : "1.7.3",
"build_hash" : "05d4530971ef0ea46d0f4fa6ee64dbc8df659682",
"build_timestamp" : "2015-10-15T09:14:17Z",
"build_snapshot" : false,
"lucene_version" : "4.10.4"
"tagline" : "You Know, for Search"

Which means that elasticsearch is running properly.

/etc/elasticsearch/elasticsearch.yml: bam_guillaume "bam_guillaume" /tech/cloud/MONITORING/elasticsearch/data /tech/cloud/MONITORING/elasticsearch/tmp
http.cors.enabled: true
indices.fielddata.cache.size: 40%
indices.breaker.fielddata.limit: 50% 70%
network.publish_host: x.x.x.x
http.port: 9200
http.enabled: true
http.cors.allow-origin: /http://(.*)(:[0-9]+)?/ true
cluster.routing.allocation.allow_rebalance: always


 * ==== 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: [


Any idea of which could be the cause ? Any help will be appreciated.

Thanks in advance,



Resolved. httpd service was simply not started !

(system) #3