# gRPC unable to connect

**URL:** <https://forum.weaviate.io/t/grpc-unable-to-connect/20290>\
**Category:** Support\
**Tags:** python, technical\
**Created:** [March 24, 2025, 3:04pm UTC](https://forum.weaviate.io/t/grpc-unable-to-connect/20290 "2025-03-24T15:04:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tejas\_Sharma](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/tejas_sharma/32/2086_2.png) [@Tejas\_Sharma](https://forum.weaviate.io/u/Tejas_Sharma)\
**Post date:** [March 24, 2025, 3:04pm UTC](https://forum.weaviate.io/t/grpc-unable-to-connect/20290/1 "2025-03-24T15:04:04Z")

</div>

### Description

We’ve been using HTTP just find but when trying to use the gRPC URL on Weaviate client 4.11.1, we get this error:

```Error
Unable to get client collection: 'NoneType' object has no attribute 'collections'

```

However, I saw in the documentation this:

 ![image](https://canada1.discourse-cdn.com/flex027/uploads/weaviate/original/2X/3/39162ace52f00fef63c2ed1acd05eda28516546f.png)

I’m a bit confused if it uses gRPC underneath the hood or whether we need to pass in the GRPC variable in the code:

```auto
client = weaviate.connect_to_weaviate_cloud(
		cluster_url=wcd_url, # Replace with your Weaviate Cloud URL
		auth_credentials=wvc.init.Auth.api_key(wcd_api_key), # Replace with your Weaviate Cloud key
	)

```

### Server Setup Information

- Weaviate Server Version:
- Deployment Method: 
- Multi Node? Number of Running Nodes:
- Client Language and Version:
- Multitenancy?:

### Any additional Information

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [March 25, 2025, 5:49pm UTC](https://forum.weaviate.io/t/grpc-unable-to-connect/20290/2 "2025-03-25T17:49:39Z")

</div>

hi @Tejas_Sharma !!

Were you able to fix this? I was out today, but now I got info about an outage in `europe-west3` regarding GRPC.

So they are probably related.

Let me know if this is fixed now.

Thanks!

---

<div class="post-metadata">

**Author:** ![Tejas\_Sharma](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/tejas_sharma/32/2086_2.png) [@Tejas\_Sharma](https://forum.weaviate.io/u/Tejas_Sharma)\
**Post date:** [March 31, 2025, 7:05am UTC](https://forum.weaviate.io/t/grpc-unable-to-connect/20290/3 "2025-03-31T07:05:37Z")

</div>

Hi @DudaNogueira I’m still getting this and it was before this europe outage happened (we are us-west).

I’m also confused regarding the documentation above because it says it automatically uses GRPC underneath the hood anyways without me specifying anything on Python v4?

(Oh and for some reason, I had posted this but when I came back to check it was still in my drafts, so sorry for late response)

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [March 31, 2025, 2:27pm UTC](https://forum.weaviate.io/t/grpc-unable-to-connect/20290/4 "2025-03-31T14:27:26Z")

</div>

hi @Tejas_Sharma !!

That’s right.

Some method of the client are still using the REST endpoints, but we are moving towards only using GRPC, so we are slowly migrating those methods from REST to GRPC.

But note that this is “under the hood”, so it shouldn’t affect the client syntax.

So now, in python v4, when you instantiate the python client, it will first check both REST and GRPC endpoints, and use it accordingly.

Let me know if that helps.

---

<div class="post-metadata">

**Author:** ![Tejas\_Sharma](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/tejas_sharma/32/2086_2.png) [@Tejas\_Sharma](https://forum.weaviate.io/u/Tejas_Sharma)\
**Post date:** [April 3, 2025, 8:26pm UTC](https://forum.weaviate.io/t/grpc-unable-to-connect/20290/5 "2025-04-03T20:26:02Z")

</div>

Thanks @DudaNogueira ! Good to know