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

Cannot create knowledge base after Dify 1.10.1 upgrade #20790

New Issue
Open
opened 2026-02-21 20:08:59 -05:00 by yindo · 13 comments
yindo commented 2026-02-21 20:08:59 -05:00
Owner
Copy Link
Copy Source

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

1.10.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Cannot create knowledge base after Dify 1.10.1 upgrade

✔️ Expected Behavior

Cannot create knowledge base after Dify 1.10.1 upgrade

❌ Actual Behavior

Image
Originally created by @zhangleijun111 on GitHub (Dec 4, 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 1.10.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Cannot create knowledge base after Dify 1.10.1 upgrade ### ✔️ Expected Behavior Cannot create knowledge base after Dify 1.10.1 upgrade ### ❌ Actual Behavior <img width="866" height="546" alt="Image" src="https://github.com/user-attachments/assets/ec768984-4c29-4f38-872b-417fb53973b2" />
yindo added the 🐞 bug🤔 cant-reproducestale labels 2026-02-21 20:08:59 -05:00
yindo commented 2026-02-21 20:08:59 -05:00
Author
Owner
Copy Link
Copy Source

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

After the 1.10.1 upgrade, knowledge base creation can fail if embedding or reranking models are missing or misconfigured, or if file uploads do not return valid file IDs. The frontend disables the "Next" button if any uploaded file lacks an ID or if your vector space quota is full and billing is enabled. Recent changes added stricter validation for model settings, so please check that you have at least one valid embedding and reranking model configured in Settings → Model Provider, and that your uploaded files are supported and properly processed by the backend (you can inspect the network response for file IDs) — see details in the frontend and backend code.

If billing or quota limits are enabled, make sure you are not exceeding your plan’s limits. Also, check backend and frontend logs for any error messages when you try to create a knowledge base, as these may indicate missing models, quota issues, or upload failures.

A recent bug fix (PR #25398) addressed an error in knowledge base creation, so if you are not on a version that includes this fix, consider updating.

If these steps don’t resolve the issue, please share any relevant error logs or screenshots for further diagnosis.

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 4, 2025): <!-- Answer --> After the 1.10.1 upgrade, knowledge base creation can fail if embedding or reranking models are missing or misconfigured, or if file uploads do not return valid file IDs. The frontend disables the "Next" button if any uploaded file lacks an ID or if your vector space quota is full and billing is enabled. Recent changes added stricter validation for model settings, so please check that you have at least one valid embedding and reranking model configured in Settings → Model Provider, and that your uploaded files are supported and properly processed by the backend (you can inspect the network response for file IDs) — see details in the [frontend](https://github.com/langgenius/dify/blob/63d8fe876e1e2cbc122dc1a028c594fc21c7abd2/web/app/components/datasets/create/step-one/index.tsx#L111-L247) and [backend](https://github.com/langgenius/dify/blob/63d8fe876e1e2cbc122dc1a028c594fc21c7abd2/api/services/dataset_service.py#L95-L2486) code. If billing or quota limits are enabled, make sure you are not exceeding your plan’s limits. Also, check backend and frontend logs for any error messages when you try to create a knowledge base, as these may indicate missing models, quota issues, or upload failures. A recent bug fix ([PR #25398](https://github.com/langgenius/dify/pull/25398)) addressed an error in knowledge base creation, so if you are not on a version that includes this fix, consider updating. If these steps don’t resolve the issue, please share any relevant error logs or screenshots for further diagnosis. <!-- 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/f296b6b8-32ca-4e6d-8ac4-bb00fba2c4a0?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f296b6b8-32ca-4e6d-8ac4-bb00fba2c4a0?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f296b6b8-32ca-4e6d-8ac4-bb00fba2c4a0?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f296b6b8-32ca-4e6d-8ac4-bb00fba2c4a0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f296b6b8-32ca-4e6d-8ac4-bb00fba2c4a0?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f296b6b8-32ca-4e6d-8ac4-bb00fba2c4a0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f296b6b8-32ca-4e6d-8ac4-bb00fba2c4a0?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=After%20the%201.10.1%20upgrade%2C%20knowledge%20base%20creation%20can%20fail%20if%20embedding%20or%20reranking%20models%20are%20missing%20or%20misconfigured%2C%20or%20if%20file%20uploads%20do%20not%20return%20valid%20file%20IDs.%20The%20frontend%20disables%20the%20%22Next%22%20button%20if%20any%20uploaded%20file%20lacks%20an%20ID%20or%20if%20your%20vector%20space%20quota%20is%20full%20and%20billing%20is%20enabled.%20Recent%20changes%20added%20stricter%20validation%20for%20model%20settings%2C%20so%20please%20check%20that%20you%20have%20at%20least%20one%20valid%20embedding%20and%20reranking%20model%20configured%20in%20Settings%20%E2%86%92%20Model%20Provider%2C%20and%20that%20your%20uploaded%20files%20are%20supported%20and%20properly%20processed%20by%20the%20backend%20%28you%20can%20inspect%20the%20network%20response%20for%20file%20IDs%29%C2%A0%E2%80%94%C2%A0see%20details%20in%20the%20%5Bfrontend%5D%28https%3A//github.com/langgenius/dify/blob/63d8fe876e1e2cbc122dc1a028c594fc21c7abd2/web/app/components/datasets/create/step-one/index.tsx%23L111-L247%29%20and%20%5Bbackend%5D%28https%3A//github.com/langgenius/dify/blob/63d8fe876e1e2cbc122dc1a028c594fc21c7abd2/api/services/dataset_service.py%23L95-L2486%29%20code.%0A%0AIf%20billing%20or%20quota%20limits%20are%20enabled%2C%20make%20sure%20you%20are%20not%20exceeding%20your%20plan%E2%80%99s%20limits.%20Also%2C%20check%20backend%20and%20frontend%20logs%20for%20any%20error%20messages%20when%20you%20try%20to%20create%20a%20knowledge%20base%2C%20as%20these%20may%20indicate%20missing%20models%2C%20quota%20issues%2C%20or%20upload%20failures.%0A%0AA%20recent%20bug%20fix%20%28%5BPR%20%2325398%5D%28https%3A//github.com/langgenius/dify/pull/25398%29%29%20addressed%20an%20error%20in%20knowledge%20base%20creation%2C%20so%20if%20you%20are%20not%20on%20a%20version%20that%20includes%20this%20fix%2C%20consider%20updating.%0A%0AIf%20these%20steps%20don%E2%80%99t%20resolve%20the%20issue%2C%20please%20share%20any%20relevant%20error%20logs%20or%20screenshots%20for%20further%20diagnosis.)&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/29135)
yindo commented 2026-02-21 20:08:59 -05:00
Author
Owner
Copy Link
Copy Source

@davidkhala commented on GitHub (Dec 4, 2025):

I cannot reproduce it on my side. Is there any specialty in your txt file?

@davidkhala commented on GitHub (Dec 4, 2025): I cannot reproduce it on my side. Is there any specialty in your txt file?
yindo commented 2026-02-21 20:08:59 -05:00
Author
Owner
Copy Link
Copy Source

@kurokobo commented on GitHub (Dec 4, 2025):

I can't try it right now, but if I remember correctly, this happened either when I attached a document using drag and drop, or when I used the "Browse" link.
I think it's a bug, but as a workaround, please try attaching the file using a different method.

@kurokobo commented on GitHub (Dec 4, 2025): I can't try it right now, but if I remember correctly, this happened either when I attached a document using drag and drop, or when I used the "Browse" link. I think it's a bug, but as a workaround, please try attaching the file using a different method.
yindo commented 2026-02-21 20:08:59 -05:00
Author
Owner
Copy Link
Copy Source

@davidkhala commented on GitHub (Dec 4, 2025):

I tried both drag and drop and browse fashions but cannot reproduce this issue. If you have time to reproduce it, please attach your container logs also.

@davidkhala commented on GitHub (Dec 4, 2025): I tried both `drag and drop` and browse fashions but cannot reproduce this issue. If you have time to reproduce it, please attach your container logs also.
yindo commented 2026-02-21 20:09:00 -05:00
Author
Owner
Copy Link
Copy Source

@zhangleijun111 commented on GitHub (Dec 4, 2025):

我试过了都不行

发自我的iPhone

------------------ Original ------------------
From: David Liu @.>
Date: Fri,Dec 5,2025 11:42 AM
To: langgenius/dify @.>
Cc: zhangleijun111 @.>, Author @.>
Subject: Re: [langgenius/dify] Cannot create knowledge base after Dify 1.10.1upgrade (Issue #29135)

davidkhala left a comment (langgenius/dify#29135)

I tried both drag and drop and browse fashions but cannot reproduce this issue. If you have time to reproduce it, please attach your container logs also.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@zhangleijun111 commented on GitHub (Dec 4, 2025): 我试过了都不行 发自我的iPhone ------------------ Original ------------------ From: David Liu ***@***.***&gt; Date: Fri,Dec 5,2025 11:42 AM To: langgenius/dify ***@***.***&gt; Cc: zhangleijun111 ***@***.***&gt;, Author ***@***.***&gt; Subject: Re: [langgenius/dify] Cannot create knowledge base after Dify 1.10.1upgrade (Issue #29135) davidkhala left a comment (langgenius/dify#29135) I tried both drag and drop and browse fashions but cannot reproduce this issue. If you have time to reproduce it, please attach your container logs also. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***&gt;
yindo commented 2026-02-21 20:09:00 -05:00
Author
Owner
Copy Link
Copy Source

@davidkhala commented on GitHub (Dec 4, 2025):

我试过了都不行

发自我的iPhone
…

我想到还有一种可能，不是没配置好vector store的缘故？

@davidkhala commented on GitHub (Dec 4, 2025): > 我试过了都不行 > > > > 发自我的iPhone > […](#) 我想到还有一种可能，不是没配置好vector store的缘故？
yindo commented 2026-02-21 20:09:00 -05:00
Author
Owner
Copy Link
Copy Source

@zhangleijun111 commented on GitHub (Dec 4, 2025):

我不用vector的，1.10.0可以，10.1就不行

发自我的iPhone

------------------ Original ------------------
From: David Liu @.>
Date: Fri,Dec 5,2025 0:13 PM
To: langgenius/dify @.>
Cc: zhangleijun111 @.>, Author @.>
Subject: Re: [langgenius/dify] Cannot create knowledge base after Dify 1.10.1upgrade (Issue #29135)

davidkhala left a comment (langgenius/dify#29135)

我试过了都不行

发自我的iPhone
…

我想到还有一种可能，不是没配置好vector store的缘故？

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@zhangleijun111 commented on GitHub (Dec 4, 2025): 我不用vector的，1.10.0可以，10.1就不行 发自我的iPhone ------------------ Original ------------------ From: David Liu ***@***.***&gt; Date: Fri,Dec 5,2025 0:13 PM To: langgenius/dify ***@***.***&gt; Cc: zhangleijun111 ***@***.***&gt;, Author ***@***.***&gt; Subject: Re: [langgenius/dify] Cannot create knowledge base after Dify 1.10.1upgrade (Issue #29135) davidkhala left a comment (langgenius/dify#29135) 我试过了都不行 发自我的iPhone … 我想到还有一种可能，不是没配置好vector store的缘故？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***&gt;
yindo commented 2026-02-21 20:09:00 -05:00
Author
Owner
Copy Link
Copy Source

@davidkhala commented on GitHub (Dec 4, 2025):

@zhangleijun111 我猜这就是原因，dify建立dataset是必须要有vector store的，但是从1.10.1的docker compose文件里
https://github.com/langgenius/dify/blob/b353a126d8fd24028c24b2e89015ee1fe9629682/docker/docker-compose.yaml#L1043
将默认的vector数据库weaviate放到profiles里变成需配置项了，这样一来如果没设profile直接就没这个容器了。所以你看看有没有weaviate容器在运行

@davidkhala commented on GitHub (Dec 4, 2025): @zhangleijun111 我猜这就是原因，dify建立dataset是必须要有vector store的，但是从1.10.1的docker compose文件里 https://github.com/langgenius/dify/blob/b353a126d8fd24028c24b2e89015ee1fe9629682/docker/docker-compose.yaml#L1043 将默认的vector数据库weaviate放到profiles里变成需配置项了，这样一来如果没设profile直接就没这个容器了。所以你看看有没有weaviate容器在运行
yindo commented 2026-02-21 20:09:00 -05:00
Author
Owner
Copy Link
Copy Source

@zhangleijun111 commented on GitHub (Dec 5, 2025):

@zhangleijun111 我猜这就是原因，dify建立dataset是必须要有vector store的，但是从1.10.1的docker compose文件里

dify/docker/docker-compose.yaml

1043号线 在B353A12

简介：

将默认的vector数据库weaviate放到profiles里变成需配置项了，这样一来如果没设profile直接就没这个容器了。所以你看看有没有weaviate容器在运行

Image

有的

@zhangleijun111 commented on GitHub (Dec 5, 2025): > [@zhangleijun111](https://github.com/zhangleijun111) 我猜这就是原因，dify建立dataset是必须要有vector store的，但是从1.10.1的docker compose文件里 > > [dify/docker/docker-compose.yaml](https://github.com/langgenius/dify/blob/b353a126d8fd24028c24b2e89015ee1fe9629682/docker/docker-compose.yaml#L1043) > > 1043号线 在[B353A12](/langgenius/dify/commit/b353a126d8fd24028c24b2e89015ee1fe9629682) > > 简介： > > 将默认的vector数据库weaviate放到profiles里变成需配置项了，这样一来如果没设profile直接就没这个容器了。所以你看看有没有weaviate容器在运行 <img width="741" height="121" alt="Image" src="https://github.com/user-attachments/assets/cdb1c927-a552-423a-a59c-a20c5a6e3fd6" /> 有的
yindo commented 2026-02-21 20:09:00 -05:00
Author
Owner
Copy Link
Copy Source

@zhangleijun111 commented on GitHub (Dec 5, 2025):

我这边无法复现。你的txt文件有专门的部分吗？

Image看看日志

@zhangleijun111 commented on GitHub (Dec 5, 2025): > 我这边无法复现。你的txt文件有专门的部分吗？ <img width="1443" height="512" alt="Image" src="https://github.com/user-attachments/assets/383c3831-ace8-4aa4-8e71-900daa52a9da" />看看日志
yindo commented 2026-02-21 20:09:00 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 18, 2026):

Hi, @zhangleijun111. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that after upgrading to Dify 1.10.1 on a self-hosted Docker setup, you cannot create a knowledge base, unlike in version 1.10.0.
  • The issue likely relates to the new requirement for a properly configured vector store (Weaviate) from version 1.10.1 onward.
  • You confirmed Weaviate is running, but the problem persists, suggesting further log and configuration review is needed.
  • Another user mentioned a possible bug with file upload methods but was unable to reproduce the issue.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify, and if so, you can keep the discussion open by commenting here.
  • Otherwise, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 18, 2026): Hi, @zhangleijun111. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that after upgrading to Dify 1.10.1 on a self-hosted Docker setup, you cannot create a knowledge base, unlike in version 1.10.0. - The issue likely relates to the new requirement for a properly configured vector store (Weaviate) from version 1.10.1 onward. - You confirmed Weaviate is running, but the problem persists, suggesting further log and configuration review is needed. - Another user mentioned a possible bug with file upload methods but was unable to reproduce the issue. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of Dify, and if so, you can keep the discussion open by commenting here. - Otherwise, I will automatically close this issue in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 20:09:00 -05:00
Author
Owner
Copy Link
Copy Source

@davidkhala commented on GitHub (Jan 19, 2026):

@zhangleijun111
根据你的日志，应该是和我之前遇到的是同一个问题
https://github.com/langgenius/dify/issues/29162
它通过这个修复了
https://github.com/langgenius/dify/pull/29297

@davidkhala commented on GitHub (Jan 19, 2026): @zhangleijun111 根据你的日志，应该是和我之前遇到的是同一个问题 https://github.com/langgenius/dify/issues/29162 它通过这个修复了 https://github.com/langgenius/dify/pull/29297
yindo commented 2026-02-21 20:09:00 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 20, 2026):

Hi, @zhangleijun111. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported an issue creating a knowledge base after upgrading to Dify 1.10.1 on a self-hosted Docker setup.
  • The problem seems linked to the new requirement for a configured vector store (Weaviate) introduced in version 1.10.1.
  • You confirmed that Weaviate is running, but the issue persists.
  • I suggested checking model configurations, file upload validity, and logs, and referenced a recent fix (PR #29297) for a similar problem.
  • You were encouraged to verify with the latest version and provide logs if the issue continued.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify, and if so, keep the discussion open by commenting here.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 20, 2026): Hi, @zhangleijun111. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported an issue creating a knowledge base after upgrading to Dify 1.10.1 on a self-hosted Docker setup. - The problem seems linked to the new requirement for a configured vector store (Weaviate) introduced in version 1.10.1. - You confirmed that Weaviate is running, but the issue persists. - I suggested checking model configurations, file upload validity, and logs, and referenced a recent fix (PR #29297) for a similar problem. - You were encouraged to verify with the latest version and provide logs if the issue continued. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of Dify, and if so, keep the discussion open by commenting here. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 stale 🐞 bug 🤔 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#20790
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?