Modify the elasticsearch.yml configuration file to allow extranet access.

vim config/elasticsearch.yml
# Add

network.host: 0.0.0.0

Failed to start, check did not pass, error reported

[2018-05-18T17:44:59,658][INFO ][o.e.b.BootstrapChecks    ] [gFOuNlS] bound or publishing to a non-loopback address, enforcing bootstrap checks
ERROR: [2] bootstrap checks failed
[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]

[2]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

[1]: max file descriptors [65535] for elasticsearch process is too low, increase to at least [65536]

Edit /etc/security/limits.conf and append the following.
* soft nofile 65536
* hard nofile 65536
You need to re-login to the user after modifying this file for it to take effect

[2]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

Edit /etc/sysctl.conf and append the following.
vm.max_map_count=655360
After saving, execute.

sysctl -p

Restart and done!

bin/elasticsearch

Similar Posts:

• Elasticsearch startup error, bootstrap checks failed
• [Solved] Elasticsearch Startup Error: node validation exception
• max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
• [Solved] ERROR: bootstrap checks failed memory locking requested for elasticsearch process but memory is not locked
• Nginx report 500 internal server error
• [Solved] MYSQL Error: [Warning] Changed limits: max_open_files: 1024
• [Solved] Linux Start solr Error: Your Max Processes Limit is currently 31202. It should be set to 65000 to avoid operational disruption.
• Nginx Error: too many open files [How to Solve]
• Error: too many open files [How to Solve]
• [Solved] Elasticsearch Error: maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?