Difference between network.host, transport.host and http.host settings

Why http.host: and #transport.host: are still 0.0.0.0 after changing network.host: to a static @ i know that i have been configured my network.host before "0.0.0.0" but it still 0.0.0.0 in this two settings { http.host: and #transport.host:}

network.host: 192.168.1.10
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
#http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.seed_hosts: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# --------------------------------- Readiness ----------------------------------
#
# Enable an unauthenticated TCP readiness endpoint on localhost
#
#readiness.port: 9399
#
# ---------------------------------- Various -----------------------------------
#
# Allow wildcard deletion of indices:
#
#action.destructive_requires_name: false

#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically
# generated to configure Elasticsearch security features on 11-06-2022 21:39:47

# Enable security features
xpack.security.enabled: true

xpack.security.enrollment.enabled: true

# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12

# Enable encryption and mutual authentication between cluster nodes
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12
# Create a new cluster with the current node only
# Additional nodes can still join the cluster later
cluster.initial_master_nodes: ["elastic"]

# Allow HTTP API connections from anywhere
# Connections are encrypted and require user authentication
http.host: 0.0.0.0

# Allow other nodes to join the cluster from anywhere
# Connections are encrypted and mutually authenticated
#transport.host: 0.0.0.0

#----------------------- END SECURITY AUTO CONFIGURATION -----------------------

--

I have edited your post to make it easier to read. Again, please use the topic title as a summary of your question :slight_smile:

If you set network.host, it will automatically apply to both http.host and transport.host.

thanks @warkolm for your response ,
i edited my network.host to static ip but http.host and transport.host still 0.0.0.0 what the solution ?? remove the elastic and install it again ?,

It's not clear what you are asking there sorry.

how to configuring kibana and elasticsearsh in HTTPS and how to access to the interface of kibana with https ??

Take a look at Secure the Elastic Stack | Elasticsearch Guide [8.3] | Elastic

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.