You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm have quite a bit of difficulties trying to get started. First I tried building and running the match docker image with an Elasticsearch connectionstring in the form of https://xxx:xxx@provider:port which does not work. Then I tried to rebuild the docker container using different types of setup based on the Elasticsearch python lib documentation e.g.:
es = Elasticsearch(
['localhost', 'otherhost'],
http_auth=('user', 'secret'),
port=443,
use_ssl=True
)
this also did not work (we are connecting to the instance with node.js just fine).
Then I tried to run it locally using docker-compose but this also failed because the image match container start's before the Elasticsearch image is started and causes it to fail the connection to Elasticsearch.
The text was updated successfully, but these errors were encountered:
maybe your elasticsearch version is too new? Look here: rhsimplex/image-match#88
I succesfully updated this project to the newest elastic client and will create a pull request soon. Nevertheless it is still not working for me, as I still get {"status": "fail", "error": ["bad request"], "method": "", "result": []}for /add but I when I managed to get it running for myself, I will create the PR :D
I'm have quite a bit of difficulties trying to get started. First I tried building and running the match docker image with an Elasticsearch connectionstring in the form of
https://xxx:xxx@provider:port
which does not work. Then I tried to rebuild the docker container using different types of setup based on the Elasticsearch python lib documentation e.g.:this also did not work (we are connecting to the instance with node.js just fine).
Then I tried to run it locally using docker-compose but this also failed because the image match container start's before the Elasticsearch image is started and causes it to fail the connection to Elasticsearch.
The text was updated successfully, but these errors were encountered: