Connection failed "possibility #1 / #2" page when setting up on a machine that has a "dash" in the hostname

[Stijnlb]

Connection failed "possibility #1 / #2" page when setting up on a machine that has a "dash" in the hostname.

Renaming the machine and changing the configuration accordingly solves the problem. re-applying a machine-name with dash and reconfiguring breaks it again.

elasticsearch 1.4.2
kibana 3.1.2

config.js:
elasticsearch: "http://belka-srv:9200",

elasticsearch.yml:
http.cors.enabled: true
http.cors.allow-origin: "/.*/"

[rashidkpc]

This sounds like a DNS issue, I have no issue accessing hosts with a dash:

Please check your browser console for any errors.

[Stijnlb]

Hi Rashid,

hm ... Indeed ... From looking at the console, it seems that it is sending
GET requests to the ES nodes index using the hostname of my dev-machine ?!
(I file- copied the entire ElasticSearch + Kibana instance from one machine
to the other and changed the config, assuming that would work ...)

GET http://gnela164.agfahealthcare.com:9200/_nodes
net::ERR_NAME_NOT_RESOLVEDapp.js:9 $get.idapp.js:9 qapp.js:9 $get.japp.js:9
g.promise.then.iapp.js:9 g.promise.then.iapp.js:9 (anonymous function)

Is this expected behavior?
or is it expected that I set up a fresh instance from scratch and re-import
all the documents after exporting them from my dev cluster ?

best regards,
Stijn Lambert, Belgium

On Fri, Jan 30, 2015 at 11:00 PM, Rashid Khan notifications@github.com
wrote:

This sounds like a DNS issue, I have no issue accessing hosts with a dash:

[image: screen shot 2015-01-30 at 2 59 03 pm]
https://cloud.githubusercontent.com/assets/1250387/5984148/9c0bcf28-a890-11e4-8812-ebb3b0bac1c8.png

Please check your browser console for any errors.

—
Reply to this email directly or view it on GitHub
#2821 (comment)
.

[rashidkpc]

Try clearing your browser cache, closing this as it appears to be a DNS issue not a bug.