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

cannot upload files to knowledge #12268

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

Originally created by @ttname on GitHub (Mar 27, 2025).

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

1.1.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

upgrade to 1.1.1, cannot upload files to knowledge

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @ttname on GitHub (Mar 27, 2025). ### 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 1.1.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce upgrade to 1.1.1, cannot upload files to knowledge ![Image](https://github.com/user-attachments/assets/c54d8b35-aafe-4ac6-a359-07cc07ba8a5d) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:06:39 -05:00
yindo closed this issue 2026-02-21 19:06:39 -05:00
yindo commented 2026-02-21 19:06:40 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 27, 2025):

Hey @ttname! I'm here to help you with any bugs, questions, or contributions you have for Dify. I'm a bot designed to assist you while you wait for a human maintainer. Let's tackle this issue together!

I found several similar threads related to the issue you're experiencing:

  1. Open Issue: There's an open issue discussing the missing retrieval_model.weights.weight_type field, which causes verification failure when adding a new file to the knowledge base [1].

  2. Closed Issues:

    • One closed issue suggests adding the weight_type field with the value customized to the weights configuration in your retrieval_model to resolve the validation error [2].
    • Another closed issue recommends deleting the old knowledge base and re-uploading the files after updating to version 1.1.3, which has been reported to work successfully [3].
    • A third closed issue provides a similar solution for self-hosted Docker setups, advising to add the weight_type field with the value customized [4].

The problem you're facing is a known bug in Dify versions 1.1.1 through 1.1.3, related to a missing weight_type field in the KnowledgeConfig model's retrieval_model.weights. You can resolve this by adding the weight_type field with the value customized to your configuration, or by reverting to version 1.1.0 where this issue does not occur [5][6].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 27, 2025): <!-- Greeting --> Hey @ttname! I'm here to help you with any bugs, questions, or contributions you have for Dify. I'm a bot designed to assist you while you wait for a human maintainer. Let's tackle this issue together! <!-- Answer --> I found several similar threads related to the issue you're experiencing: 1. **Open Issue**: There's an open issue discussing the missing `retrieval_model.weights.weight_type` field, which causes verification failure when adding a new file to the knowledge base <sup>[[1]](https://github.com/langgenius/dify/issues/16514)</sup>. 2. **Closed Issues**: - One closed issue suggests adding the `weight_type` field with the value `customized` to the weights configuration in your retrieval_model to resolve the validation error <sup>[[2]](https://github.com/langgenius/dify/issues/16591)</sup>. - Another closed issue recommends deleting the old knowledge base and re-uploading the files after updating to version 1.1.3, which has been reported to work successfully <sup>[[3]](https://github.com/langgenius/dify/issues/16663)</sup>. - A third closed issue provides a similar solution for self-hosted Docker setups, advising to add the `weight_type` field with the value `customized` <sup>[[4]](https://github.com/langgenius/dify/issues/16674)</sup>. The problem you're facing is a known bug in Dify versions 1.1.1 through 1.1.3, related to a missing `weight_type` field in the `KnowledgeConfig` model's `retrieval_model.weights`. You can resolve this by adding the `weight_type` field with the value `customized` to your configuration, or by reverting to version 1.1.0 where this issue does not occur <sup>[[5]](https://github.com/langgenius/dify/issues/16520)</sup><sup>[[6]](https://github.com/langgenius/dify/issues/16411)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/59e93371-6c89-4a45-88f4-4f934c8e34bc?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/59e93371-6c89-4a45-88f4-4f934c8e34bc?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/59e93371-6c89-4a45-88f4-4f934c8e34bc?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/59e93371-6c89-4a45-88f4-4f934c8e34bc?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/59e93371-6c89-4a45-88f4-4f934c8e34bc?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/59e93371-6c89-4a45-88f4-4f934c8e34bc?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/59e93371-6c89-4a45-88f4-4f934c8e34bc?feedback_type=other)</sup>
yindo commented 2026-02-21 19:06:40 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 27, 2025):

This has been fixed in v1.1.3

@crazywoola commented on GitHub (Mar 27, 2025): This has been fixed in v1.1.3
yindo commented 2026-02-21 19:06:40 -05:00
Author
Owner
Copy Link
Copy Source

@ttname commented on GitHub (Mar 27, 2025):

just upgrade 1.1.3 , but no reslove

@ttname commented on GitHub (Mar 27, 2025): just upgrade 1.1.3 , but no reslove
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 🐞 bug
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#12268
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?