Zugriff auf Port 9200 remote nicht möglich

Question

Habe gerade mit elastic search 5.4.0 begonnen, zuerst habe ich es auf Mac (lokal) und dann auf dem Server installiert. In Mac, wenn ich in Browser leite als 'http://localhost:9200' es mir Ausgabe zeigt:

{ 
 
    "name" : "Node_1", 
 
    "cluster_name" : "bhujang_bipl", 
 
    "cluster_uuid" : "N75mGOiSQCufpBl_2B7jSg", 
 
    "version" : { 
 
    "number" : "5.4.0", 
 
    "build_hash" : "780f8c4", 
 
    "build_date" : "2017-04-28T17:43:27.229Z", 
 
    "build_snapshot" : false, 
 
    "lucene_version" : "6.5.0" 
 
    }, 
 
    "tagline" : "You Know, for Search" 
 
}

was bedeutet, i bis 9200 bin verbunden, die elasticsaerch ist.

Aber wenn ich es auf dem Server von http://192.168.1.126:9200 läuft, dann wird es nicht verbunden und zeigt mir eine Ausgabe als: Seite nicht gefunden !!

Ich habe die Firewall sowohl auf dem Server als auch auf dem Client als Lösungen deaktiviert, die ich aus dem Internet bekommen habe, aber es konnte nicht funktionieren.

Meine elasticsaerch.yml Datei ist

 
# ======================== Elasticsearch Configuration ========================= 
 
# 
 
# NOTE: Elasticsearch comes with reasonable defaults for most settings. 
 
#  Before you set out to tweak and tune the configuration, make sure you 
 
#  understand what are you trying to accomplish and the consequences. 
 
# 
 
# The primary way of configuring a node is via this file. This template lists 
 
# the most important settings you may want to configure for a production cluster. 
 
# 
 
# Please consult the documentation for further information on configuration options: 
 
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html 
 
# 
 
# ---------------------------------- Cluster ----------------------------------- 
 
# 
 
# Use a descriptive name for your cluster: 
 
# 
 
#cluster.name: my-application 
 
# 
 
# ------------------------------------ Node ------------------------------------ 
 
# 
 
# Use a descriptive name for the node: 
 
# 
 
#node.name: node-1 
 
# 
 
# Add custom attributes to the node: 
 
# 
 
#node.attr.rack: r1 
 
# 
 
# ----------------------------------- Paths ------------------------------------ 
 
# 
 
# Path to directory where to store the data (separate multiple locations by comma): 
 
# 
 
#path.data: /path/to/data 
 
# 
 
# Path to log files: 
 
# 
 
#path.logs: /path/to/logs 
 
# 
 
# ----------------------------------- Memory ----------------------------------- 
 
# 
 
# Lock the memory on startup: 
 
# 
 
#bootstrap.memory_lock: true 
 
# 
 
# Make sure that the heap size is set to about half the memory available 
 
# on the system and that the owner of the process is allowed to use this 
 
# limit. 
 
# 
 
# Elasticsearch performs poorly when the system is swapping the memory. 
 
# 
 
# ---------------------------------- Network ----------------------------------- 
 
# 
 
# Set the bind address to a specific IP (IPv4 or IPv6): 
 
#network.host:192.168.1.126 
 
# 
 
# Set a custom port for HTTP: 
 
#http.port: 9200 
 
# 
 
# For more information, consult the network module documentation. 
 
# 
 
# --------------------------------- Discovery ---------------------------------- 
 
# 
 
# Pass an initial list of hosts to perform discovery when new node is started: 
 
#The default list of hosts is ["127.0.0.1", "[::1]","103.240.195.45","103.240.195.45"] 
 
# 
 
#discovery.zen.ping.unicast.hosts: ["host1", "host2"] 
 
# 
 
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes/2 + 1): 
 
# 
 
#discovery.zen.minimum_master_nodes: 3 
 
# 
 
# For more information, consult the zen discovery module documentation. 
 
# 
 
# ---------------------------------- Gateway ----------------------------------- 
 
# 
 
# Block initial recovery after a full cluster restart until N nodes are started: 
 
# 
 
#gateway.recover_after_nodes: 3 
 
# 
 
# For more information, consult the gateway module documentation. 
 
# 
 
# ---------------------------------- Various ----------------------------------- 
 
# 
 
# Require explicit names when deleting indices: 
 
# 
 
#action.destructive_requires_name: true

jemand mit mir helfen kann, was die bestmögliche Fehler von meiner Seite sein kann?

Answer 1

Von Link https://github.com/elastic/elasticsearch/issues/19987

diese zwei Zeilen in der Datei yml transport.host hinzufügen: localhost network.host:192.168.1.126