# ES6 Cluster , with mult-NIC(Each node has more than two ips) bindip to 0.0.0.0 successfully . But Same with ES8 does not work **URL:** \ **Category:** Elasticsearch\ **Created:** [March 27, 2025, 3:47am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447 "2025-03-27T03:47:48Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Varinder](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/varinder/32/123243_2.png) [@Varinder](https://discuss.elastic.co/u/Varinder)\ **Post date:** [March 27, 2025, 3:47am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/1 "2025-03-27T03:47:48Z")
ES6 Cluster , with mult-NIC(Each node has more than two ips) bindip to 0.0.0.0 successfully . But Same with ES8 does not work. ES 8.15.2 Cluster throws and error in installation of two or more servers with (Each server is multi-NIC have more than 1 IP ) But same installation with ES6.8.23 with multi-NIC servers is successful when binding to 0.0.0.0. Why is that ? Am I doing something wrong . ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [March 27, 2025, 3:51am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/2 "2025-03-27T03:51:45Z")
Hello, Please share all the related configurations, both for ES6 and for ES8, and share the logs you are getting as well. ---
**Author:** ![Varinder](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/varinder/32/123243_2.png) [@Varinder](https://discuss.elastic.co/u/Varinder)\ **Post date:** [March 27, 2025, 4:01am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/3 "2025-03-27T04:01:00Z")
ES6 configuration Successful vi /etc/elasticsearch/elasticsearch.yml path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch cluster.name: elasticsearch node.name: localhost.localdomain network.host: 0.0.0.0 http.port: 9200 searchguard.enterprise\_modules\_enabled: false thread\_pool.write.queue\_size: 1000 thread\_pool.index.queue\_size: 1000 http.max\_content\_length: 500mb indices.query.bool.max\_clause\_count: 200000 thread\_pool.search.size: 50 searchguard.ssl.transport.pemkey\_filepath: key.pem searchguard.ssl.transport.pemcert\_filepath: cert.pem searchguard.ssl.transport.pemtrustedcas\_filepath: cacert.pem searchguard.ssl.transport.enforce\_hostname\_verification: false searchguard.ssl.transport.enabled\_protocols: - TLSv1.2 searchguard.ssl.http.pemkey\_filepath: key.pem searchguard.ssl.http.pemcert\_filepath: cert.pem searchguard.ssl.http.pemtrustedcas\_filepath: cacert.pem searchguard.ssl.http.enabled: false s searchguard.ssl.http.enabled\_protocols: - TLSv1.2 discovery.zen.ping.unicast.hosts: - X - Y - Z discovery.zen.minimum\_master\_nodes: 2 ES8 configuration failed. below path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch xpack.security.enabled: false xpack.security.enrollment.enabled: false xpack.security.http.ssl: enabled: false keystore.path: certs/http.p12 xpack.security.transport.ssl: enabled: false verification\_mode: certificate keystore.path: certs/transport.p12 truststore.path: certs/transport.p12 cluster.initial\_master\_nodes: - X - Y - z network.host: 0.0.0.0 http.port: 9200 searchguard.enterprise\_modules\_enabled: false thread\_pool.write.queue\_size: 1000 xpack.security.http.ssl.supported\_protocols: - TLSv1.3 xpack.security.transport.ssl.supported\_protocols: - TLSv1.3 http.max\_content\_length: 500mb indices.query.bool.max\_clause\_count: 200000 thread\_pool.search.size: 50 searchguard.ssl.transport.pemkey\_filepath: key.pem searchguard.ssl.transport.pemcert\_filepath: cert.pem searchguard.ssl.transport.pemtrustedcas\_filepath: cacert.pem searchguard.ssl.transport.enforce\_hostname\_verification: false searchguard.ssl.transport.enabled\_protocols: - TLSv1.2 - TLSv1.3 searchguard.ssl.http.pemkey\_filepath: key.pem searchguard.ssl.http.pemcert\_filepath: cert.pem searchguard.ssl.http.pemtrustedcas\_filepath: cacert.pem searchguard.ssl.http.enabled: true searchguard.ssl.http.enabled\_protocols: - TLSv1.2 - TLSv1.3 searchguard.check\_snapshot\_restore\_write\_privileges: true searchguard.restapi.roles\_enabled: - SGS\_ALL\_ACCESS cluster.name: elasticsearch discovery.seed\_hosts: - X - Y - Z node.name: Centos-8 node.roles: [data, master] bootstrap.memory\_lock: true When I use bindip to Ip of server instead of 0.0.0.0 then it passes. Error I am getting on both data nodes Successfully connected to cluster elasticsearch (localhost) as user cert XXXXXXXXXXXXXXXXXXX Internal Server Error Can I get any reason for failure or success according to ES6 and ES8 documentation. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [March 27, 2025, 4:06am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/4 "2025-03-27T04:06:46Z")
You need to share the full log error you are receiving, not just the description of the error. Share the full log error. Also, you are using a third-party plugin that is not supported here, it is not possible to know if this may impact or not. ---
**Author:** ![Varinder](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/varinder/32/123243_2.png) [@Varinder](https://discuss.elastic.co/u/Varinder)\ **Post date:** [March 27, 2025, 4:09am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/5 "2025-03-27T04:09:22Z")
Same error is repeated over and over again even in logs. Changing in elasticsearch.yml, From network.host: 0.0.0.0 to network.host: localhost,IP . Makes it work. Question is multi-NIC servers as nodes work on ES6.8.23 cluster , same environment failed in installation in ES8.15.2 When binding to 0.0.0.0 ---
**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\ **Post date:** [March 27, 2025, 4:22am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/6 "2025-03-27T04:22:50Z")
> [@Varinder](#): > > Same error is repeated over and over again even in logs. That's unfortunate, but until you provide us with an exact copy of that full error message we won't be able to help you determine the fix. ---
**Author:** ![Varinder](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/varinder/32/123243_2.png) [@Varinder](https://discuss.elastic.co/u/Varinder)\ **Post date:** [March 27, 2025, 4:41am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/7 "2025-03-27T04:41:07Z")
Error I am getting on both data nodes Successfully connected to cluster elasticsearch (localhost) as user cert XXXXXXXXXXXXXXXXXXX Internal Server Error Here XXXXXXXXXXXXXX are certs details. This Errorprint onscreen on both nodes. I did not get any other ERROR. So i dont haveanything to POST. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [March 27, 2025, 4:54am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/8 "2025-03-27T04:54:18Z")
You need to get the log from the log file and share it, without it is not possible to troubleshoot. But from the short description you provide this seems to be related to certificates and authenticaton, which are not being done by Elasticsearch in your case, but by a third-party plugin. Any issue in Elastisearch to bind to ip address/port would cause the service to not start, I doubt you would get an _Internal Server Error_ in this case. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [March 27, 2025, 8:11am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/9 "2025-03-27T08:11:57Z")
> [@Varinder](#): > > ES6 Cluster , with mult-NIC(Each node has more than two ips) bindip to 0.0.0.0 successfully . But Same with ES8 does not work. I think this is expected not to work in general. See [these docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#modules-network-binding-publishing), particularly (emphasis mine): > To avoid confusion, it is simplest to use a value which resolves to a single address. **It is usually a mistake to use `0.0.0.0` as a publish address on hosts with more than one network interface.** If it worked for you in version 6 then that was not by design, but you may have been lucky and got away with it. That's in addition to what folks have said above: you're using a third-party plugin that mucks around with networking stuff in ways that we do not support or even understand here, but which definitely could explain the fragments of errors you've shared so far. If you can reproduce the problem with the built-in security functionality, after fixing the `0.0.0.0` mistake, then it's more likely we can help. ---
**Author:** ![Varinder](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/varinder/32/123243_2.png) [@Varinder](https://discuss.elastic.co/u/Varinder)\ **Post date:** [March 27, 2025, 3:16pm UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/10 "2025-03-27T15:16:55Z")
Hi @DavidTurner, Thanks for the feedback and your more clear answer. I really appreciate this, but what if customer want to provide ES service on all NICs. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [March 27, 2025, 4:03pm UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/11 "2025-03-27T16:03:44Z")
> [@Varinder](#): > > what if customer want to provide ES service on all NICs. In that case you probably only want `http.bind_host: 0.0.0.0`. ---
**Author:** ![Varinder](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/varinder/32/123243_2.png) [@Varinder](https://discuss.elastic.co/u/Varinder)\ **Post date:** [April 1, 2025, 11:50pm UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/12 "2025-04-01T23:50:10Z")
Thanks for the updated @DavidTurner , I have used below setting, set\_yaml "${elasticsearch\_conf}" "[transport.bind\_host]" "0.0.0.0" && set\_yaml "${elasticsearch\_conf}" "[transport.publish\_host]" "${resolved\_host}" && set\_yaml "${elasticsearch\_conf}" "[http.bind\_host]" "0.0.0.0" && set\_yaml "${elasticsearch\_conf}" "[http.publish\_host]" "${resolved\_host}" It worked for multi-NIC IPs, but failed for FQDNs ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 2, 2025, 9:41am UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/13 "2025-04-02T09:41:41Z")
> [@Varinder](#): > > set\_yaml "${elasticsearch\_conf}" "[transport.bind\_host]" "0.0.0.0" && Binding the transport port to multiple interfaces is probably a mistake. > [@Varinder](#): > > It worked for multi-NIC IPs, but failed for FQDNs This implies that something is wrong with name resolution. You're still making it incredibly hard to help by just not sharing any actual logs or error messages. Just saying "it failed" without any supporting evidence is frustrating for those of us trying our best to help you. ---
**Author:** ![Varinder](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/varinder/32/123243_2.png) [@Varinder](https://discuss.elastic.co/u/Varinder)\ **Post date:** [April 2, 2025, 1:12pm UTC](https://discuss.elastic.co/t/es6-cluster-with-mult-nic-each-node-has-more-than-two-ips-bindip-to-0-0-0-0-successfully-but-same-with-es8-does-not-work/376447/14 "2025-04-02T13:12:48Z")
Thanks, @DavidTurner, for your valuable feedback. You're right — it seems the name resolution wasn't properly set up. After revisiting the configuration and ensuring proper FQDN resolution for the multi-NIC environment, things are now working as expected. I agree, troubleshooting without complete logs was frustrating — apologies for that. I'll run a few more validation tests and will follow up here with final confirmation. Thanks again for your support! Have a great day!!