Elastic Search CORS Error [SOLVED]

[Saha]

Failed to load http://localhost:9200/thirtybees11/_search: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://thirtybee.local' is therefore not allowed access.

[lesley]

Are you using the domain thirtybees.local? Or is that something we left in the module?

[Saha]

@lesley thirtybee.local is my local virtual host.

[lesley]

It sounds like then you need to set the cors policy of your local instance to be able to connect to your elastic instance. https://enable-cors.org/server_apache.html

[Saha]

@lesley I did try this . Put the code in apache conf,virtual host as well as .htaccess still no luck .

[lesley]

I am not positive, but it might require a domain name being attached and then adding a content policy for the domain.

[Saha]

@lesley I didn't get you. If you don't mind . Can you elaborate.

[lesley]

It looks like you are using localhost for your elastic instance, it might require you to use a domain name instead of a local host. @mdekker might be best suited to answer this one.

[Saha]

@lesley You mean it will work fine on domain and not on local host. Thankyou.

[lesley]

Possibly, you would need to test it though.

[bzndk]

I think lesley is right.

The issue here is you need to run it thrue Apache or Nginx in proxy, and make sure the config for that proxy has the right headers set for Access-Control-Allow-Origin.

Apache Header set Access-Control-Allow-Origin "*"

Nginx add_header 'Access-Control-Allow-Origin' '*';

[bzndk]

Actually found some more info, it looks like in the configuration of Elasticsearch you can setup CORS to there is some more info about it on https://github.com/elastic/elasticsearch/issues/9031

[Saha]

Setting http.cors.enabled : true http.cors.allow-origin : "*" In Elastic config located at config/elasticsearch.yml Fixed the Issue. But Now i am getting { "error":{ "root_cause":[ { "type":"illegal_argument_exception", "reason":"query malformed, empty clause found at [1:533]" } ], "type":"illegal_argument_exception", "reason":"query malformed, empty clause found at [1:533]" }, "status":400 }

[bzndk]

Hmm revert back to the settings before you change, i think it's better to proxy it via nginx since Elastic Search can be a bit of a PITA.

[Saha]

{ “error”:{ “rootcause”:[ { “type”:“illegalargumentexception”, “reason”:“query malformed, empty clause found at [1:533]” } ], “type”:“illegalargument_exception”, “reason”:“query malformed, empty clause found at [1:533]” }, “status”:400 } @lesley @mdekker Anyone

[bzndk]

hmm in the elastic search module is the query missing there something sounds like it in my mind.