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

Could not connect to Weaviate #20285

New Issue
Closed
opened 2026-02-21 20:06:40 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 20:06:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @dyuehang on GitHub (Nov 12, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

latest

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Could not connect to Weaviate:Connection to Weaviate failed.

✔️ Expected Behavior

successfully upload and analyze the my files

❌ Actual Behavior

Could not connect to Weaviate:Connection to Weaviate failed.

Originally created by @dyuehang on GitHub (Nov 12, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version latest ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Could not connect to Weaviate:Connection to Weaviate failed. ### ✔️ Expected Behavior successfully upload and analyze the my files ### ❌ Actual Behavior Could not connect to Weaviate:Connection to Weaviate failed.
yindo added the 🌚 invalid label 2026-02-21 20:06:40 -05:00
yindo closed this issue 2026-02-21 20:06:40 -05:00
yindo commented 2026-02-21 20:06:41 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 12, 2025):

Hi @dyuehang! I'm Dosu and I’m helping the dify team.

Recent updates to Dify's Weaviate integration require both the HTTP (8080) and gRPC (50051) ports to be exposed and accessible in your Docker setup. The Weaviate Docker image and Python client were upgraded, and the new client expects the gRPC port to be available for health checks and operations. If either port is missing or misconfigured, Dify will fail to connect to Weaviate, resulting in the error you're seeing.

Here’s a troubleshooting checklist based on the latest migration guides and PRs:

  1. Make sure your docker-compose file exposes both ports for Weaviate:

    ports:
  - "8080:8080"
  - "50051:50051"

  2. Confirm your Weaviate container is running and both ports are mapped:

    docker ps | grep weaviate

    You should see both 8080 and 50051 listed.

  3. If you’re using custom endpoints (for example, with Helm or a remote Weaviate), set the WEAVIATE_GRPC_ENDPOINT environment variable, e.g.:

    WEAVIATE_GRPC_ENDPOINT=grpc://weaviate:50051

    This is especially important if your HTTP and gRPC endpoints differ or are on different hosts/ports details.

  4. Ensure you are running Weaviate server version 1.27.0 and Python client version 4.17.0 as required by recent Dify releases details.

  5. After updating your configuration, restart your Docker services and check the logs for any errors:

    docker compose up -d
docker compose logs weaviate

  6. You can verify Weaviate is accessible with:

    curl http://localhost:8080/v1/meta
netstat -tulpn | grep 50051

If you see errors about missing modules or failed health checks, reinstall the Python client in the API container:

cd api
uv sync --reinstall-package weaviate-client
uv run python -c "import weaviate; print(weaviate.__version__)"

You should see version 4.17.0.

These steps reflect the latest requirements and fixes for Weaviate integration in Dify’s Docker deployment details details. If you still have issues, check your environment variables and Docker network settings for typos or conflicts.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 12, 2025): <!-- Greeting --> Hi @dyuehang! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> Recent updates to Dify's Weaviate integration require both the HTTP (8080) and gRPC (50051) ports to be exposed and accessible in your Docker setup. The Weaviate Docker image and Python client were upgraded, and the new client expects the gRPC port to be available for health checks and operations. If either port is missing or misconfigured, Dify will fail to connect to Weaviate, resulting in the error you're seeing. Here’s a troubleshooting checklist based on the latest migration guides and PRs: 1. Make sure your docker-compose file exposes both ports for Weaviate: ``` ports: - "8080:8080" - "50051:50051" ``` 2. Confirm your Weaviate container is running and both ports are mapped: ``` docker ps | grep weaviate ``` You should see both 8080 and 50051 listed. 3. If you’re using custom endpoints (for example, with Helm or a remote Weaviate), set the `WEAVIATE_GRPC_ENDPOINT` environment variable, e.g.: ``` WEAVIATE_GRPC_ENDPOINT=grpc://weaviate:50051 ``` This is especially important if your HTTP and gRPC endpoints differ or are on different hosts/ports [details](https://github.com/langgenius/dify/pull/27861). 4. Ensure you are running Weaviate server version 1.27.0 and Python client version 4.17.0 as required by recent Dify releases [details](https://github.com/langgenius/dify/pull/26964). 5. After updating your configuration, restart your Docker services and check the logs for any errors: ``` docker compose up -d docker compose logs weaviate ``` 6. You can verify Weaviate is accessible with: ``` curl http://localhost:8080/v1/meta netstat -tulpn | grep 50051 ``` If you see errors about missing modules or failed health checks, reinstall the Python client in the API container: ``` cd api uv sync --reinstall-package weaviate-client uv run python -c "import weaviate; print(weaviate.__version__)" ``` You should see version 4.17.0. These steps reflect the latest requirements and fixes for Weaviate integration in Dify’s Docker deployment [details](https://github.com/langgenius/dify/pull/26964) [details](https://github.com/langgenius/dify/pull/25447). If you still have issues, check your environment variables and Docker network settings for typos or conflicts. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/bffc96cc-ea61-45a3-ba31-f1251f20bb25?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/bffc96cc-ea61-45a3-ba31-f1251f20bb25?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/bffc96cc-ea61-45a3-ba31-f1251f20bb25?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/bffc96cc-ea61-45a3-ba31-f1251f20bb25?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/bffc96cc-ea61-45a3-ba31-f1251f20bb25?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/bffc96cc-ea61-45a3-ba31-f1251f20bb25?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/bffc96cc-ea61-45a3-ba31-f1251f20bb25?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28133)
yindo commented 2026-02-21 20:06:41 -05:00
Author
Owner
Copy Link
Copy Source

@dyuehang commented on GitHub (Nov 12, 2025):

@dosu i just wanna Qdrant,not weaviate

@dyuehang commented on GitHub (Nov 12, 2025): @dosu i just wanna Qdrant,not weaviate
yindo commented 2026-02-21 20:06:41 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 12, 2025):

To use Qdrant instead of Weaviate in your self-hosted Dify Docker setup, set VECTOR_STORE=qdrant in your .env file or docker-compose.yaml. Make sure the Qdrant service is enabled and configured, and you can ignore or remove any Weaviate-specific environment variables. Qdrant-specific variables you may want to set include QDRANT_URL (default is http://qdrant:6333), QDRANT_API_KEY, and others as needed. No code changes are required—just update your environment variables and Docker Compose profiles as needed. Only the selected backend needs to be running at startup.
You can find the relevant configuration options and examples in the docker/.env.example and docker-compose.yaml files in the repo (reference).

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 12, 2025): <!-- Answer --> To use Qdrant instead of Weaviate in your self-hosted Dify Docker setup, set VECTOR_STORE=qdrant in your .env file or docker-compose.yaml. Make sure the Qdrant service is enabled and configured, and you can ignore or remove any Weaviate-specific environment variables. Qdrant-specific variables you may want to set include QDRANT_URL (default is http://qdrant:6333), QDRANT_API_KEY, and others as needed. No code changes are required—just update your environment variables and Docker Compose profiles as needed. Only the selected backend needs to be running at startup. You can find the relevant configuration options and examples in the docker/.env.example and docker-compose.yaml files in the repo ([reference](https://github.com/langgenius/dify/blob/b76e17b25d51fa98cf9108a3d0a65a2d8b44ae68/docker/.env.example#L491-L509)). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/bfea6dec-4203-4177-9631-9dd552e862e7?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/bfea6dec-4203-4177-9631-9dd552e862e7?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/bfea6dec-4203-4177-9631-9dd552e862e7?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/bfea6dec-4203-4177-9631-9dd552e862e7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/bfea6dec-4203-4177-9631-9dd552e862e7?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/bfea6dec-4203-4177-9631-9dd552e862e7?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/bfea6dec-4203-4177-9631-9dd552e862e7?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28133)
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
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#20285
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?