# Elasticsearch startup error with 0.0.0.0
**URL:** https://discuss.elastic.co/t/elasticsearch-startup-error-with-0-0-0-0/185635
**Category:** Elasticsearch
**Created:** [June 13, 2019, 12:11pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-with-0-0-0-0/185635 "2019-06-13T12:11:24Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Imrankhan\_Patan](https://discuss.elastic.co/u/Imrankhan_Patan)
#### Post date: [June 13, 2019, 12:11pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-with-0-0-0-0/185635/1 "2019-06-13T12:11:24Z")
I am trying to set up single node elasticsearch on RHEL virtual machine. It is running fine with default configuration of 127.0.0.1, but its not available outside the VM. when I changed the network.host "0.0.0.0" its not starting up.Initially it gave error getting error while creating max file descriptors [65000] for elasticsearch process is too low, increase to at least [65536]. I have changed the `/etc/security/limits.conf` file increase the file descriptors. But now its failing in another boot strap check which is system call filters failed to install; check the logs and fix your configuration or disable system call. I am confused, why this happens only with different bind address than 127.0.0.1
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [June 13, 2019, 12:19pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-with-0-0-0-0/185635/2 "2019-06-13T12:19:23Z")
> [@Imrankhan\_Patan](#):
>
> why this happens only with different bind address than 127.0.0.1
Because [bootstrap checks are enforced when nodes are remotely accessible](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html#dev-vs-prod-mode) unless you set `discovery.type: single-node`. Here's a [blog post](https://www.elastic.co/blog/bootstrap_checks_annoying_instead_of_devastating) with more details too.
---
### Author:  [@Imrankhan\_Patan](https://discuss.elastic.co/u/Imrankhan_Patan)
#### Post date: [June 13, 2019, 12:23pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-with-0-0-0-0/185635/4 "2019-06-13T12:23:17Z")
Thanks David for that clarification, so how can I resolve this system call filter check failure ? Also please note that I am not trying to setup cluster, I just need to set up on single machine but as this is VM in a cloud, I need to access it via external IP address, so I had to change network.host to other than loop back address
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [June 13, 2019, 1:27pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-with-0-0-0-0/185635/5 "2019-06-13T13:27:18Z")
You can bypass the bootstrap checks and form a single-node cluster by setting `discovery.type: single-node`.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 11, 2019, 1:27pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-with-0-0-0-0/185635/6 "2019-07-11T13:27:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.