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

After upgrading dify, the knowledge base and application data on the web page are gone. #8345

New Issue
Closed
opened 2026-02-21 18:25:11 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:25:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @jiake55 on GitHub (Feb 17, 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

0.10.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

dify 升级后网页端的知识库和应用数据都没有了，我是通过docker本地部署的dify，我根据指引升级dify到v0.10.3后，啥都是正常的，dify登入后网页端没数据了，然后我又恢复备份和volumes退回到原来的版本都不行 之前做的好多东西都没了，搞了好多天了 请问是什么问题呢？I deployed dify locally through docker. After I upgraded dify to v0.10.3 according to the instructions, everything was normal. After logging in to dify, there was no data on the web page. Then I restored the backup and rolled back the volumes to the original version, but it didn't work. A lot of things I did before are gone. I've been working on it for many days. What's the problem?

✔️ Expected Behavior

❌ Actual Behavior

No response

Originally created by @jiake55 on GitHub (Feb 17, 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 0.10.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce dify 升级后网页端的知识库和应用数据都没有了，我是通过docker本地部署的dify，我根据指引升级dify到v0.10.3后，啥都是正常的，dify登入后网页端没数据了，然后我又恢复备份和volumes退回到原来的版本都不行 之前做的好多东西都没了，搞了好多天了 请问是什么问题呢？I deployed dify locally through docker. After I upgraded dify to v0.10.3 according to the instructions, everything was normal. After logging in to dify, there was no data on the web page. Then I restored the backup and rolled back the volumes to the original version, but it didn't work. A lot of things I did before are gone. I've been working on it for many days. What's the problem? ### ✔️ Expected Behavior ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduceoutdated labels 2026-02-21 18:25:11 -05:00
yindo closed this issue 2026-02-21 18:25:11 -05:00
yindo commented 2026-02-21 18:25:11 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 17, 2025):

Hey @jiake55! 👋 I'm here to help you with any bugs, questions, or contributions you have regarding dify. I'm a bot designed to assist you while you wait for a human maintainer. Let's dive in and tackle this issue together!

I found some similar discussions that might be relevant to your issue:

  1. dify 升级后docker容器里的docker-api-1、docker-worker-1 您好，不好意思打扰，我是通过docker本地部署的dify，我根据指引升级dify到v0.10.2后，docker-api-1、docker-worker-1一直restarting，dify也无法登入，请问是什么问题呢？ - This discussion is still open and might provide insights into issues related to Docker deployments after an upgrade [1].

  2. Help! why the dify app&setting not saved after restarting my Windows？ - This is another open discussion that deals with data not being saved, which might be related to your issue [2].

For your specific issue, ensure that your Docker volumes are correctly configured and preserved during the upgrade. The Dify documentation specifies several Docker volume configurations that need to be preserved to prevent data loss. You should verify that these volumes are correctly mapped and that the data is intact in these volumes [3].

Additionally, check your .env file to ensure it is up to date with any changes from the .env.example file. This file is crucial for configuring your deployment and ensuring custom settings persist through upgrades [4].

If you have already restored backups and rolled back volumes without success, it might be worth checking if there are any migration scripts or tools provided by Dify that could help in handling data during upgrades. Dify uses Alembic for database migrations, and there might be specific commands or scripts that need to be run to ensure the database schema is correctly updated [5].

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 (Feb 17, 2025): <!-- Greeting --> Hey @jiake55! 👋 I'm here to help you with any bugs, questions, or contributions you have regarding dify. I'm a bot designed to assist you while you wait for a human maintainer. Let's dive in and tackle this issue together! <!-- Answer --> I found some similar discussions that might be relevant to your issue: 1. [dify 升级后docker容器里的docker-api-1、docker-worker-1 您好，不好意思打扰，我是通过docker本地部署的dify，我根据指引升级dify到v0.10.2后，docker-api-1、docker-worker-1一直restarting，dify也无法登入，请问是什么问题呢？](https://github.com/langgenius/dify/discussions/12312) - This discussion is still open and might provide insights into issues related to Docker deployments after an upgrade <sup>[[1]](https://github.com/langgenius/dify/discussions/12312)</sup>. 2. [Help! why the dify app&setting not saved after restarting my Windows？](https://github.com/langgenius/dify/discussions/13321) - This is another open discussion that deals with data not being saved, which might be related to your issue <sup>[[2]](https://github.com/langgenius/dify/discussions/13321)</sup>. For your specific issue, ensure that your Docker volumes are correctly configured and preserved during the upgrade. The Dify documentation specifies several Docker volume configurations that need to be preserved to prevent data loss. You should verify that these volumes are correctly mapped and that the data is intact in these volumes <sup>[[3]](https://github.com/langgenius/dify/blob/main/docker/docker-compose-template.yaml)</sup>. Additionally, check your `.env` file to ensure it is up to date with any changes from the `.env.example` file. This file is crucial for configuring your deployment and ensuring custom settings persist through upgrades <sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/docker-compose.md)</sup>. If you have already restored backups and rolled back volumes without success, it might be worth checking if there are any migration scripts or tools provided by Dify that could help in handling data during upgrades. Dify uses Alembic for database migrations, and there might be specific commands or scripts that need to be run to ensure the database schema is correctly updated <sup>[[5]](https://github.com/langgenius/dify/blob/main/api/extensions/ext_commands.py)</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/b98fc06a-618f-4eaa-8d39-c9d37711feaf?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b98fc06a-618f-4eaa-8d39-c9d37711feaf?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b98fc06a-618f-4eaa-8d39-c9d37711feaf?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b98fc06a-618f-4eaa-8d39-c9d37711feaf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b98fc06a-618f-4eaa-8d39-c9d37711feaf?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b98fc06a-618f-4eaa-8d39-c9d37711feaf?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b98fc06a-618f-4eaa-8d39-c9d37711feaf?feedback_type=other)</sup>
yindo commented 2026-02-21 18:25:11 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 17, 2025):

Which version did you upgrade from, v0.10.x was a breaking change, things might lost. However we do not have a plan to fix this.

@crazywoola commented on GitHub (Feb 17, 2025): Which version did you upgrade from, v0.10.x was a breaking change, things might lost. However we do not have a plan to fix this.
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 outdated 🐞 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#8345
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?