langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 04:25:29 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Error with host weaviate #5256

New Issue
Closed
opened 2026-02-21 18:10:06 -05:00 by yindo · 12 comments
yindo commented 2026-02-21 18:10:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @tienldbnk on GitHub (Aug 27, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.7.1

Cloud or Self Hosted

Cloud, Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

✔️ Expected Behavior

It working 0.7.0 but when update 0.7.2 it bug

❌ Actual Behavior

image

I'm not update file

image
Originally created by @tienldbnk on GitHub (Aug 27, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.7.1 ### Cloud or Self Hosted Cloud, Self Hosted (Docker), Self Hosted (Source) ### Steps to reproduce ### ✔️ Expected Behavior It working 0.7.0 but when update 0.7.2 it bug ### ❌ Actual Behavior <img width="1788" alt="image" src="https://github.com/user-attachments/assets/931503ce-e8dc-4109-97f1-535ea6908972"> I'm not update file <img width="1771" alt="image" src="https://github.com/user-attachments/assets/68e97e71-ab92-45b5-a0ef-d270aa9f4ee3">
yindo added the 🌚 invalid🤔 cant-reproduce👻 feat:rag labels 2026-02-21 18:10:06 -05:00
yindo closed this issue 2026-02-21 18:10:06 -05:00
yindo commented 2026-02-21 18:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 27, 2024):

Hello, @tienldbnk! 👋 I'm here to help you with bugs, questions, and becoming a contributor. I'm Dosu, a bot designed to assist you while waiting for a human maintainer.

I found a similar issue related to the Weaviate vector database connection error after updating to Dify version 0.7.2. The problem is caused by the weaviate.connect.connection.has_grpc attribute being set to False in the _init_client method, which does not exist in the Weaviate client library. Removing or correcting this line should resolve the connection issue [1].

Additionally, ensure that your environment variables for Weaviate are correctly set. The default configuration includes:

  • VECTOR_STORE: Should be set to weaviate.
  • WEAVIATE_ENDPOINT: The Weaviate endpoint address (e.g., http://weaviate:8080).
  • WEAVIATE_API_KEY: The API key for connecting to Weaviate.
  • WEAVIATE_BATCH_SIZE: The batch size for creating objects in Weaviate, with a default value of 100.
  • WEAVIATE_GRPC_ENABLED: Whether to use gRPC for communication with Weaviate, with a default value of true [1][2].

If you have any custom configurations, double-check them to ensure they are compatible with the new version.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 27, 2024): <!-- Greeting --> Hello, @tienldbnk! 👋 I'm here to help you with bugs, questions, and becoming a contributor. I'm Dosu, a bot designed to assist you while waiting for a human maintainer. <!-- Answer --> I found a similar issue related to the Weaviate vector database connection error after updating to Dify version 0.7.2. The problem is caused by the `weaviate.connect.connection.has_grpc` attribute being set to `False` in the `_init_client` method, which does not exist in the Weaviate client library. Removing or correcting this line should resolve the connection issue <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/rag/datasource/vdb/weaviate/weaviate_vector.py)</sup>. Additionally, ensure that your environment variables for Weaviate are correctly set. The default configuration includes: - `VECTOR_STORE`: Should be set to `weaviate`. - `WEAVIATE_ENDPOINT`: The Weaviate endpoint address (e.g., `http://weaviate:8080`). - `WEAVIATE_API_KEY`: The API key for connecting to Weaviate. - `WEAVIATE_BATCH_SIZE`: The batch size for creating objects in Weaviate, with a default value of 100. - `WEAVIATE_GRPC_ENABLED`: Whether to use gRPC for communication with Weaviate, with a default value of true <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/rag/datasource/vdb/weaviate/weaviate_vector.py)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md)</sup>. If you have any custom configurations, double-check them to ensure they are compatible with the new version. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@tienldbnk commented on GitHub (Aug 28, 2024):

Hello, @tienldbnk! 👋 I'm here to help you with bugs, questions, and becoming a contributor. I'm Dosu, a bot designed to assist you while waiting for a human maintainer.

I found a similar issue related to the Weaviate vector database connection error after updating to Dify version 0.7.2. The problem is caused by the weaviate.connect.connection.has_grpc attribute being set to False in the _init_client method, which does not exist in the Weaviate client library. Removing or correcting this line should resolve the connection issue [1].

Additionally, ensure that your environment variables for Weaviate are correctly set. The default configuration includes:

  • VECTOR_STORE: Should be set to weaviate.
  • WEAVIATE_ENDPOINT: The Weaviate endpoint address (e.g., http://weaviate:8080).
  • WEAVIATE_API_KEY: The API key for connecting to Weaviate.
  • WEAVIATE_BATCH_SIZE: The batch size for creating objects in Weaviate, with a default value of 100.
  • WEAVIATE_GRPC_ENABLED: Whether to use gRPC for communication with Weaviate, with a default value of true [1][2].

If you have any custom configurations, double-check them to ensure they are compatible with the new version.

To continue talking to Dosu, mention @dosu.

@tienldbnk commented on GitHub (Aug 28, 2024): > Hello, @tienldbnk! 👋 I'm here to help you with bugs, questions, and becoming a contributor. I'm Dosu, a bot designed to assist you while waiting for a human maintainer. > > I found a similar issue related to the Weaviate vector database connection error after updating to Dify version 0.7.2. The problem is caused by the `weaviate.connect.connection.has_grpc` attribute being set to `False` in the `_init_client` method, which does not exist in the Weaviate client library. Removing or correcting this line should resolve the connection issue [[1]](https://github.com/langgenius/dify/blob/main/api/core/rag/datasource/vdb/weaviate/weaviate_vector.py). > > Additionally, ensure that your environment variables for Weaviate are correctly set. The default configuration includes: > > * `VECTOR_STORE`: Should be set to `weaviate`. > * `WEAVIATE_ENDPOINT`: The Weaviate endpoint address (e.g., `http://weaviate:8080`). > * `WEAVIATE_API_KEY`: The API key for connecting to Weaviate. > * `WEAVIATE_BATCH_SIZE`: The batch size for creating objects in Weaviate, with a default value of 100. > * `WEAVIATE_GRPC_ENABLED`: Whether to use gRPC for communication with Weaviate, with a default value of true [[1]](https://github.com/langgenius/dify/blob/main/api/core/rag/datasource/vdb/weaviate/weaviate_vector.py)[[2]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md). > > If you have any custom configurations, double-check them to ensure they are compatible with the new version. > > _To continue talking to [Dosu](https://dosu.dev), mention @dosu._
yindo commented 2026-02-21 18:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@tienldbnk commented on GitHub (Aug 28, 2024):

Hello, @tienldbnk! 👋 I'm here to help you with bugs, questions, and becoming a contributor. I'm Dosu, a bot designed to assist you while waiting for a human maintainer.
I found a similar issue related to the Weaviate vector database connection error after updating to Dify version 0.7.2. The problem is caused by the weaviate.connect.connection.has_grpc attribute being set to False in the _init_client method, which does not exist in the Weaviate client library. Removing or correcting this line should resolve the connection issue [1].
Additionally, ensure that your environment variables for Weaviate are correctly set. The default configuration includes:

  • VECTOR_STORE: Should be set to weaviate.
  • WEAVIATE_ENDPOINT: The Weaviate endpoint address (e.g., http://weaviate:8080).
  • WEAVIATE_API_KEY: The API key for connecting to Weaviate.
  • WEAVIATE_BATCH_SIZE: The batch size for creating objects in Weaviate, with a default value of 100.
  • WEAVIATE_GRPC_ENABLED: Whether to use gRPC for communication with Weaviate, with a default value of true [1][2].

If you have any custom configurations, double-check them to ensure they are compatible with the new version.
To continue talking to Dosu, mention @dosu.

Screenshot 2024-08-28 at 12 04 50 Screenshot 2024-08-28 at 12 04 58 Screenshot 2024-08-28 at 12 05 08
@tienldbnk commented on GitHub (Aug 28, 2024): > > Hello, @tienldbnk! 👋 I'm here to help you with bugs, questions, and becoming a contributor. I'm Dosu, a bot designed to assist you while waiting for a human maintainer. > > I found a similar issue related to the Weaviate vector database connection error after updating to Dify version 0.7.2. The problem is caused by the `weaviate.connect.connection.has_grpc` attribute being set to `False` in the `_init_client` method, which does not exist in the Weaviate client library. Removing or correcting this line should resolve the connection issue [[1]](https://github.com/langgenius/dify/blob/main/api/core/rag/datasource/vdb/weaviate/weaviate_vector.py). > > Additionally, ensure that your environment variables for Weaviate are correctly set. The default configuration includes: > > > > * `VECTOR_STORE`: Should be set to `weaviate`. > > * `WEAVIATE_ENDPOINT`: The Weaviate endpoint address (e.g., `http://weaviate:8080`). > > * `WEAVIATE_API_KEY`: The API key for connecting to Weaviate. > > * `WEAVIATE_BATCH_SIZE`: The batch size for creating objects in Weaviate, with a default value of 100. > > * `WEAVIATE_GRPC_ENABLED`: Whether to use gRPC for communication with Weaviate, with a default value of true [[1]](https://github.com/langgenius/dify/blob/main/api/core/rag/datasource/vdb/weaviate/weaviate_vector.py)[[2]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md). > > > > If you have any custom configurations, double-check them to ensure they are compatible with the new version. > > _To continue talking to [Dosu](https://dosu.dev), mention @dosu._ <img width="745" alt="Screenshot 2024-08-28 at 12 04 50" src="https://github.com/user-attachments/assets/e44c5f31-5932-44c4-b0d3-013f87a96779"> <img width="872" alt="Screenshot 2024-08-28 at 12 04 58" src="https://github.com/user-attachments/assets/d209bbe3-47f1-4706-956b-7cd4d252651e"> <img width="699" alt="Screenshot 2024-08-28 at 12 05 08" src="https://github.com/user-attachments/assets/03501715-7cb4-47a7-9e6a-a7b07b3621af">
yindo commented 2026-02-21 18:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 28, 2024):

Please check the weaviate container status. Thus, the version you provided is not correct. We do not use this vector db in our Cloud version.

@crazywoola commented on GitHub (Aug 28, 2024): Please check the weaviate container status. Thus, the version you provided is not correct. We do not use this vector db in our Cloud version.
yindo commented 2026-02-21 18:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@tienldbnk commented on GitHub (Aug 28, 2024):

Please check the weaviate container status. Thus, the version you provided is not correct. We do not use this vector db in our Cloud version.

inside docker-compose file still exists this service

@tienldbnk commented on GitHub (Aug 28, 2024): > Please check the weaviate container status. Thus, the version you provided is not correct. We do not use this vector db in our Cloud version. inside docker-compose file still exists this service
yindo commented 2026-02-21 18:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@akramer-zibra commented on GitHub (Aug 29, 2024):

@tienldbnk if you want to use weaviate in the latest docker-compose setup, try to use the --profile argument: docker-compose --profile weaviate up

This should start the dify stack WITH weaviate as vector database service. The errors above say "Connection error ...". which could be the case, when weaviate container is not running.

@akramer-zibra commented on GitHub (Aug 29, 2024): @tienldbnk if you want to use weaviate in the latest docker-compose setup, try to use the `--profile` argument: `docker-compose --profile weaviate up` This should start the dify stack WITH weaviate as vector database service. The errors above say "Connection error ...". which could be the case, when weaviate container is not running.
yindo commented 2026-02-21 18:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@tienldbnk commented on GitHub (Aug 30, 2024):

@tienldbnk if you want to use weaviate in the latest docker-compose setup, try to use the --profile argument: docker-compose --profile weaviate up

This should start the dify stack WITH weaviate as vector database service. The errors above say "Connection error ...". which could be the case, when weaviate container is not running.

may error from services here :

image
@tienldbnk commented on GitHub (Aug 30, 2024): > @tienldbnk if you want to use weaviate in the latest docker-compose setup, try to use the `--profile` argument: `docker-compose --profile weaviate up` > > This should start the dify stack WITH weaviate as vector database service. The errors above say "Connection error ...". which could be the case, when weaviate container is not running. may error from services here : <img width="822" alt="image" src="https://github.com/user-attachments/assets/d5276c03-688b-4606-814c-2a3539809911">
yindo commented 2026-02-21 18:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@akramer-zibra commented on GitHub (Aug 30, 2024):

The error messages in the log are still the same? And docker ps shows weaviate service is running?

You have configured the services directly in the docker-compose.yml file. This may lead to errors, because some variables are used in several services. It is better practise to configure the setup within a .env file. The docker-compose file within the docker folder injects the variables where necessary.

@akramer-zibra commented on GitHub (Aug 30, 2024): The error messages in the log are still the same? And `docker ps` shows weaviate service is running? You have configured the services directly in the docker-compose.yml file. This may lead to errors, because some variables are used in several services. It is better practise to configure the setup within a `.env` file. The docker-compose file within the `docker` folder injects the variables where necessary.
yindo commented 2026-02-21 18:10:08 -05:00
Author
Owner
Copy Link
Copy Source

@tienldbnk commented on GitHub (Aug 31, 2024):

@akramer-zibra I think I only use the service from dify, and 100% use the default from dify, I do not have any edits or replacements of the default configurations of dify, so the problem that happened above I feel is unreasonable, must be dify has these hidden errors that the developers have not encountered yet

@tienldbnk commented on GitHub (Aug 31, 2024): @akramer-zibra I think I only use the service from dify, and 100% use the default from dify, I do not have any edits or replacements of the default configurations of dify, so the problem that happened above I feel is unreasonable, must be dify has these hidden errors that the developers have not encountered yet
yindo commented 2026-02-21 18:10:08 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 4, 2024):

I think this maybe a network issue, try to turn off the VPN?

@crazywoola commented on GitHub (Sep 4, 2024): I think this maybe a network issue, try to turn off the VPN?
yindo commented 2026-02-21 18:10:08 -05:00
Author
Owner
Copy Link
Copy Source

@tienldbnk commented on GitHub (Sep 5, 2024):

try to turn off the VPN

I'm not turn on vpn , I'm use my wifi

@tienldbnk commented on GitHub (Sep 5, 2024): > try to turn off the VPN I'm not turn on vpn , I'm use my wifi
yindo commented 2026-02-21 18:10:08 -05:00
Author
Owner
Copy Link
Copy Source

@ironboxer commented on GitHub (Mar 17, 2025):

WHY CLOSE THIS ISSUE?

I ALSO MEET THE SAME QUESTION!!!

DOES ANBODY HAS ANY SOLUTION?

PLEASE SOLVE IT INSTEAD CLOSE IT.

@ironboxer commented on GitHub (Mar 17, 2025): WHY CLOSE THIS ISSUE? I ALSO MEET THE SAME QUESTION!!! DOES ANBODY HAS ANY SOLUTION? PLEASE SOLVE IT INSTEAD CLOSE IT.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🌚 invalid 👻 feat:rag 🤔 cant-reproduce
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#5256
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?