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
Our weaviate db exposed with nginx ingress, site https://myweb.com is a company self-signed URL.
To access it, it use following piece of code and was working fine till 4.6.7.
Hi @Alansyf, it would seem that there is a subtle change in how the underlying grpc C implementation handles SSL certificates between the sync (grpc) and async (grpc.aio) modules
Now that the connection used by the client is fully async, this issue is raising its head!
I think the general solution here, from researching others' issues, is to allow users to specify the SSL certs in their client configuration. The client will then handle piping these to the respective httpx and grpc.aio connections. I will look into this in the coming days and release a patch fix once complete! Thanks for the report 😁
Our weaviate db exposed with nginx ingress, site https://myweb.com is a company self-signed URL.
To access it, it use following piece of code and was working fine till 4.6.7.
os.environ["GRPC_DEFAULT_SSL_ROOTS_FILE_PATH"] = "/home/jovyan/cert.crt"
os.environ["SSL_CERT_FILE"] = "/home/jovyan/cert.crt"
client = weaviate.connect_to_custom(
http_host="myweb.com",
http_port=443,
http_secure=True,
grpc_host="myweb.com",
grpc_port=443,
grpc_secure=True,
auth_credentials=weaviate.auth.AuthApiKey(id_token),
additional_config=weaviate.config.AdditionalConfig(
startup_period=10,
timeout=(5, 15)
),
)
client.connect()
When we use 4.7.0, it breaks, it always saying:
We have to use fixed version 4.6.7, can you help check here?
The text was updated successfully, but these errors were encountered: