# Unable to connect to self-hosted weaviate clusters through verba 2.0 version

**URL:** <https://forum.weaviate.io/t/unable-to-connect-to-self-hosted-weaviate-clusters-through-verba-2-0-version/4050>\
**Category:** Support\
**Created:** [September 10, 2024, 2:48am UTC](https://forum.weaviate.io/t/unable-to-connect-to-self-hosted-weaviate-clusters-through-verba-2-0-version/4050 "2024-09-10T02:48:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![adithya.ch](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/adithya.ch/32/615_2.png) [@adithya.ch](https://forum.weaviate.io/u/adithya.ch)\
**Post date:** [September 10, 2024, 2:48am UTC](https://forum.weaviate.io/t/unable-to-connect-to-self-hosted-weaviate-clusters-through-verba-2-0-version/4050/1 "2024-09-10T02:48:58Z")

</div>

I am trying to access verba 2.0 version with weaviate cluster 1.26.3 version.

export WEAVIATE\_API\_KEY\_VERBA=“pwd”  
export OLLAMA\_EMBED\_MODEL=llama3.1  
export OLLAMA\_MODEL=llama3.1  
export WEAVIATE\_URL\_VERBA=https://:6383  
export OLLAMA\_URL=[http://ollama-url:2300](http://ollama-url:2300)

Error :  
https://::6383 with Auth  
✘ Couldn’t connect to Weaviate, check your URL/API KEY: Invalid port:  
‘6383:443’  
✘ Failed to connect to Weaviate Couldn’t connect to Weaviate, check  
your URL/API KEY: Invalid port: ‘6383:443’  
INFO: 10.82.204.17:65400 - “POST /api/connect HTTP/1.1” 400 Bad Request

 ![image](https://canada1.discourse-cdn.com/flex027/uploads/weaviate/original/2X/6/679d273c772d83cc490378fc686209d236c3eeb1.jpeg)

note : It was working fine with verba 1.0 version !!

Please let me know how to fix this issue ?

---

<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:** [September 10, 2024, 2:29pm UTC](https://forum.weaviate.io/t/unable-to-connect-to-self-hosted-weaviate-clusters-through-verba-2-0-version/4050/2 "2024-09-10T14:29:16Z")

</div>

Hi @adithya.ch !

If you are using it locally, hosting using the embeddedm you need to choose local.

This option will work for Weaviate hosted in our cloud.

---

<div class="post-metadata">

**Author:** ![adithya.ch](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/adithya.ch/32/615_2.png) [@adithya.ch](https://forum.weaviate.io/u/adithya.ch)\
**Post date:** [September 10, 2024, 2:47pm UTC](https://forum.weaviate.io/t/unable-to-connect-to-self-hosted-weaviate-clusters-through-verba-2-0-version/4050/3 "2024-09-10T14:47:04Z")

</div>

Hi @DudaNogueira ,

We hosted weaviate cluster locally on our kubernetes cluster.

It was working fine with v1.0 ? Was there any process/breaking changes with V2.0 disabling access to self hosted weaviate cluster ?

Regards,  
Adithya

---

<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:** [September 10, 2024, 6:16pm UTC](https://forum.weaviate.io/t/unable-to-connect-to-self-hosted-weaviate-clusters-through-verba-2-0-version/4050/4 "2024-09-10T18:16:42Z")

</div>

Right now the new Verba 2.0 will give you three options to connect:

- Local (Embedded, will spin a Weaviate instance)
- Weaviate (will allow you to provide URL and API KEY to connect to our cloud)
- Docker. will use connect\_to\_local. It expects a host named `weaviate` at http port 8080 and grpc port 50051.

As you are using K8s, you will need provide Verba pod a way to connect to your K8s Weaviate instance having those exact informations.