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
So far there are a lot of places to make mistakes. But I do not know what I have done wrong that when I try to call this function from inside a backend api using curl:
searchai | qdrant_client.http.exceptions.ResponseHandlingException: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)
I also checked the qdrant connection both from my host machine and from inside the searchai container:
When I ran this curl command from my host machine, I got:
curl -X GET https://localhost:6333
{"title":"qdrant - vector search engine","version":"1.7.4"}
But the I went into the searchai container:
docker exec -it searchai sh
curl -X GET https://qdrant:6333
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
I did check that the .pem files exactly exist in the specified dir /qdrant_data/tls. Other than this, I have no clue on how to solve this problem.
The text was updated successfully, but these errors were encountered:
vhdmoradi
changed the title
ERTIFICATE_VERIFY_FAILED when trying to use qdrant with docker-compose and https
CERTIFICATE_VERIFY_FAILED when trying to use qdrant with docker-compose and https
Mar 7, 2024
I have two containers, qdrant and searchai. qdrant is my qdrant container with this docker-compose setup:
And this is my qdrant_custom_config.yaml:
I generated the .pem files using
mkcert
and I gave the qdrant container name (qdrant) alongside with localhost to mkcert for .pem generation:Then I have a function inside my django backend which is in the searchai container to connect to qdrant using:
So far there are a lot of places to make mistakes. But I do not know what I have done wrong that when I try to call this function from inside a backend api using curl:
I get this error:
I also checked the qdrant connection both from my host machine and from inside the searchai container:
When I ran this curl command from my host machine, I got:
But the I went into the searchai container:
I did check that the .pem files exactly exist in the specified dir /qdrant_data/tls. Other than this, I have no clue on how to solve this problem.
The text was updated successfully, but these errors were encountered: