Connect weaviate instance installed on EKS


We deployed weavaite instance through helm chart weaviate-helm/weaviate/values.yaml at 853a9c212679931fc750e2550e570fe4ce0e92f9 · weaviate/weaviate-helm · GitHub. We make sure grpc is enabled in the yaml file. While we could connect client , ingest data, and search data through python v3 sdk, we could not connect the client with python v4 sdk. It keeps giving us ConnectTimeout: timed out error.

The host ( is from kubernetes ingress, which is redirecting it to the apps in kubernetes.

Python v3:
from weaviate import Client
client = Client(“https://host”)
I could check the schema, add data, and use hybrid search.

Python v4:
client = weaviate.connect_to_custom(
additional_config=weaviate.config.AdditionalConfig(timeout=(5, 15))

ConnectTimeout: timed out

I also tried to use connect_to_local, but got the same connect timeout error.

client = weaviate.connect_to_local(
additional_config=weaviate.config.AdditionalConfig(timeout=(5, 15))
Same error: ConnectTimeout: timed out
Did we miss sth here?

Hi @zmliu213 !

Can you try adding, to connect_to_custom:


If this works, there is probably a high latency between client and the server.

Another way to troubleshoot it this:

# lets test our grpc connection
❯ wget
❯ grpcurl -d '{"service": "Weaviate"}' -proto health.proto
  "status": "SERVING"

Note: This command considers that there is not APIKEY required. If you require a Bearer token, you need to adjust this grpcurl call accordingly

Let me know if this helps

Thank you for the response. (1) After adding skip_init_checks=True, I still get connection timeout error. (2) Failed to dial target host “”: dial tcp: lookup no such host. So the grpc connection is not successful?

Not really. This message will usually surface if the client couldn’t connect at that host at all.

Can you make sure that url is publicly reachable?