cityindex-attic / logsearch

[unmaintained] A development environment for ELK
Apache License 2.0
24 stars 8 forks source link

Unable to Connect to Server! Received Status Code: 0. A status code of 0, could mean the host is unreacheable or nothing is listening on the given port. #372

Closed waterweasel4 closed 4 years ago

waterweasel4 commented 9 years ago

I am getting the following error when trying to connect:

Unable to Connect to Server! Received Status Code: 0. A status code of 0, could mean the host is unreacheable or nothing is listening on the given port.

When I go to http://192.168.3.50:9200/, I get a result: `{ "status" : 200,

}` iptables is allowing access to port 9200 as well. Yet when I go to http://192.168.3.50/elastic and enter in the aforementioned address and port, I get the error. Firefox console says the following but I am allowing CORS in .htaccess on the site following the documentation here: http://enable-cors.org/server_apache.html Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://192.168.3.50:9200//_cluster/health. (Reason: CORS header 'Access-Control-Allow-Origin' missing). "http://192.168.3.50:9200" all.min.js:12:13425 Inside ClusterHealth all.min.js:12:13056 Inside ClusterState all.min.js:12:15361 Inside IndexStatsModel all.min.js:12:16349 Inside NodeList all.min.js:12:26957 Failed to Connect on Ping! all.min.js:12:13783 Error! Unable to Connect to Server! Received Status Code: 0. A status code of 0, could mean the host is unreacheable or nothing is listening on the given port. all.min.js:12:14151 Inside ErrorMessage all.min.js:12:27956 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://192.168.3.50:9200/. (Reason: CORS header 'Access-Control-Allow-Origin' missing).