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

The original 1.6.0 version reported an error when upgrading to the dify-1.10.1-fix.1 knowledge base to upload files #20915

New Issue
Closed
opened 2026-02-21 20:09:46 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:09:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @XiaoYueTan on GitHub (Dec 9, 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

dify-1.10.1-fix.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Based on the original knowledge base, when uploading documents, the contents of the files in the knowledge base Could not be parsed and an error Could not connect to Weaviate:Connection to Weaviate failed. Details:.

Image

✔️ Expected Behavior

Can files be uploaded to the knowledge base normally and the contents inside be parsed

❌ Actual Behavior

No response

Originally created by @XiaoYueTan on GitHub (Dec 9, 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 dify-1.10.1-fix.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Based on the original knowledge base, when uploading documents, the contents of the files in the knowledge base Could not be parsed and an error Could not connect to Weaviate:Connection to Weaviate failed. Details:. <img width="1139" height="742" alt="Image" src="https://github.com/user-attachments/assets/38a81ba2-3faf-4e21-a4fc-614b555c4182" /> ### ✔️ Expected Behavior Can files be uploaded to the knowledge base normally and the contents inside be parsed ### ❌ Actual Behavior _No response_
yindo added the 👻 feat:rag label 2026-02-21 20:09:46 -05:00
yindo closed this issue 2026-02-21 20:09:46 -05:00
yindo commented 2026-02-21 20:09:47 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 9, 2025):

The upgrade to Dify 1.10.1-fix.1 introduced breaking changes in Weaviate integration: you now need both HTTP (8080) and gRPC (50051) ports exposed for Weaviate, and the Docker image must be updated to semitechnologies/weaviate:1.27.0. If you see "Could not connect to Weaviate," it's usually because the gRPC port isn't exposed, the image is outdated, or the environment variables are misconfigured.

Here's a quick checklist to resolve this:

  1. In your docker-compose.yaml, make sure the Weaviate service uses image: semitechnologies/weaviate:1.27.0 and exposes both ports:

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

  2. In your .env file, set:

    VECTOR_STORE=weaviate
WEAVIATE_ENDPOINT=http://weaviate:8080
WEAVIATE_GRPC_ENDPOINT=grpc://weaviate:50051
WEAVIATE_API_KEY=<your_api_key>

    (API key must match what's allowed in Weaviate config.)

  3. Restart your containers:

    docker compose down
docker compose up -d

  4. Test connectivity:

    • From your host: curl http://localhost:8080/v1/meta
    • Check gRPC: netstat -tulpn | grep 50051 (should show Weaviate listening)

  5. Try uploading a document in the Dify UI. If it still fails, check the logs for more details.

Migration and troubleshooting steps are documented in the Weaviate migration guide.

If you have custom Docker configs or use self-signed certs, double-check your network and authentication settings. For plugin-related credential errors, see this workaround.

Let me know if you need help with specific error logs or configuration details!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 9, 2025): <!-- Answer --> The upgrade to Dify 1.10.1-fix.1 introduced breaking changes in Weaviate integration: you now need both HTTP (8080) and gRPC (50051) ports exposed for Weaviate, and the Docker image must be updated to semitechnologies/weaviate:1.27.0. If you see "Could not connect to Weaviate," it's usually because the gRPC port isn't exposed, the image is outdated, or the environment variables are misconfigured. Here's a quick checklist to resolve this: 1. In your `docker-compose.yaml`, make sure the Weaviate service uses `image: semitechnologies/weaviate:1.27.0` and exposes both ports: ``` ports: - "8080:8080" - "50051:50051" ``` 2. In your `.env` file, set: ``` VECTOR_STORE=weaviate WEAVIATE_ENDPOINT=http://weaviate:8080 WEAVIATE_GRPC_ENDPOINT=grpc://weaviate:50051 WEAVIATE_API_KEY=<your_api_key> ``` (API key must match what's allowed in Weaviate config.) 3. Restart your containers: ``` docker compose down docker compose up -d ``` 4. Test connectivity: - From your host: `curl http://localhost:8080/v1/meta` - Check gRPC: `netstat -tulpn | grep 50051` (should show Weaviate listening) 5. Try uploading a document in the Dify UI. If it still fails, check the logs for more details. Migration and troubleshooting steps are documented in the [Weaviate migration guide](https://github.com/langgenius/dify/blob/51330c0ee631de49f6cc5f7b7436c00cab62d38f/docs/weaviate/WEAVIATE_MIGRATION_GUIDE/README.md#L5-L120). If you have custom Docker configs or use self-signed certs, double-check your network and authentication settings. For plugin-related credential errors, see [this workaround](https://github.com/langgenius/dify-official-plugins/issues/2203). Let me know if you need help with specific error logs or configuration details! <!-- 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/8a9ab64c-b944-40ec-9bb2-de098d95e32b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8a9ab64c-b944-40ec-9bb2-de098d95e32b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8a9ab64c-b944-40ec-9bb2-de098d95e32b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8a9ab64c-b944-40ec-9bb2-de098d95e32b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8a9ab64c-b944-40ec-9bb2-de098d95e32b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8a9ab64c-b944-40ec-9bb2-de098d95e32b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8a9ab64c-b944-40ec-9bb2-de098d95e32b?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20upgrade%20to%20Dify%201.10.1-fix.1%20introduced%20breaking%20changes%20in%20Weaviate%20integration%3A%20you%20now%20need%20both%20HTTP%20%288080%29%20and%20gRPC%20%2850051%29%20ports%20exposed%20for%20Weaviate%2C%20and%20the%20Docker%20image%20must%20be%20updated%20to%20semitechnologies/weaviate%3A1.27.0.%20If%20you%20see%20%22Could%20not%20connect%20to%20Weaviate%2C%22%20it%27s%20usually%20because%20the%20gRPC%20port%20isn%27t%20exposed%2C%20the%20image%20is%20outdated%2C%20or%20the%20environment%20variables%20are%20misconfigured.%0A%0AHere%27s%20a%20quick%20checklist%20to%20resolve%20this%3A%0A%0A1.%20In%20your%20%60docker-compose.yaml%60%2C%20make%20sure%20the%20Weaviate%20service%20uses%20%60image%3A%20semitechnologies/weaviate%3A1.27.0%60%20and%20exposes%20both%20ports%3A%0A%20%20%20%60%60%60%0A%20%20%20ports%3A%0A%20%20%20%20%20-%20%228080%3A8080%22%0A%20%20%20%20%20-%20%2250051%3A50051%22%0A%20%20%20%60%60%60%0A2.%20In%20your%20%60.env%60%20file%2C%20set%3A%0A%20%20%20%60%60%60%0A%20%20%20VECTOR_STORE%3Dweaviate%0A%20%20%20WEAVIATE_ENDPOINT%3Dhttp%3A//weaviate%3A8080%0A%20%20%20WEAVIATE_GRPC_ENDPOINT%3Dgrpc%3A//weaviate%3A50051%0A%20%20%20WEAVIATE_API_KEY%3D%3Cyour_api_key%3E%0A%20%20%20%60%60%60%0A%20%20%20%28API%20key%20must%20match%20what%27s%20allowed%20in%20Weaviate%20config.%29%0A%0A3.%20Restart%20your%20containers%3A%0A%20%20%20%60%60%60%0A%20%20%20docker%20compose%20down%0A%20%20%20docker%20compose%20up%20-d%0A%20%20%20%60%60%60%0A%0A4.%20Test%20connectivity%3A%0A%20%20%20-%20From%20your%20host%3A%20%60curl%20http%3A//localhost%3A8080/v1/meta%60%0A%20%20%20-%20Check%20gRPC%3A%20%60netstat%20-tulpn%20%7C%20grep%2050051%60%20%28should%20show%20Weaviate%20listening%29%0A%0A5.%20Try%20uploading%20a%20document%20in%20the%20Dify%20UI.%20If%20it%20still%20fails%2C%20check%20the%20logs%20for%20more%20details.%0A%0AMigration%20and%20troubleshooting%20steps%20are%20documented%20in%20the%20%5BWeaviate%20migration%20guide%5D%28https%3A//github.com/langgenius/dify/blob/51330c0ee631de49f6cc5f7b7436c00cab62d38f/docs/weaviate/WEAVIATE_MIGRATION_GUIDE/README.md%23L5-L120%29.%0A%0AIf%20you%20have%20custom%20Docker%20configs%20or%20use%20self-signed%20certs%2C%20double-check%20your%20network%20and%20authentication%20settings.%20For%20plugin-related%20credential%20errors%2C%20see%20%5Bthis%20workaround%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/2203%29.%0A%0ALet%20me%20know%20if%20you%20need%20help%20with%20specific%20error%20logs%20or%20configuration%20details%21)&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/29386)
yindo commented 2026-02-21 20:09:47 -05:00
Author
Owner
Copy Link
Copy Source

@XiaoYueTan commented on GitHub (Dec 10, 2025):

Useful. It has been solved

@XiaoYueTan commented on GitHub (Dec 10, 2025): Useful. It has been solved
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 👻 feat:rag
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#20915
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?