Elasticsearch does not work with network.host 0.0.0.0

Elastic Stack Elasticsearch
1

I have been trying to set up a test version of a website on a different server.
The website uses React, Strapi, Postgres, Nginx and Elasticsearch.
All of them are working, but the website is stuck on a loader.

I do not whether it is something with Elasticsearch or something else. However, I had a problem with network.host in yml file. When it was network.host 127.0.0.1 I could curl only for 127.0.0.1:9200 and it did not work with server-ip:9200. When I had changed it into 0.0.0.0, I could not restart elastic. So I have changed it into html.host 0.0.0.0. and it works for both 127.0.0.1:9200 and server-ip:9200.
Can I leave it like that? I mean with html.host. Or it shouldn't be like that?

Thank you for your help in advance!

2

Covered in this post

3

I had read it before, but I still was not sure.
Maybe I can use both html.host and network.host in the same time. What do you think?

4

It has started to work with only network.host after I add a domain instead IP.

5

From what I remember, I think network.host signals more startup checks to be enforced.

6

It was a communication problem. I have added CORS settings and it works now.

7

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