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

Cannot be used after upgrade (v1.10.1) #20757

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

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

v1.10.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Upgrade from version 1.110.0 to version 1.10.1
Access the /app page

✔️ Expected Behavior

Display the list of applications

❌ Actual Behavior

  • The application list is not displayed.
  • User information is not displayed.
  • Alert message: Error code 500

log file :

api.log

Originally created by @rainsun007 on GitHub (Dec 3, 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 v1.10.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Upgrade from version 1.110.0 to version 1.10.1 Access the /app page ### ✔️ Expected Behavior Display the list of applications ### ❌ Actual Behavior - The application list is not displayed. - User information is not displayed. - Alert message: Error code 500 log file : [api.log](https://github.com/user-attachments/files/23897999/api.log)
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 20:08:50 -05:00
yindo closed this issue 2026-02-21 20:08:50 -05:00
yindo commented 2026-02-21 20:08:51 -05:00
Author
Owner
Copy Link
Copy Source

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

The 500 error on the /app page after upgrading to v1.10.1 is almost certainly due to missing database migrations. This version adds new columns (created_by, updated_by) to the apps, app_model_configs, and sites tables, which are required by the backend API and WebApp Auth features. If these migrations aren't applied, API queries will fail and cause the UI to break with a 500 error example migration.

To fix this, make sure you run all pending database migrations inside your API container. You can do this by running:

docker compose exec api flask upgrade-db

or

docker compose exec api uv run flask db upgrade

If you see migration errors (like missing tables or functions), you may need to stamp your database to the latest migration revision and then upgrade again. Also, ensure that your DB_TYPE environment variable matches your actual database type (e.g., postgresql or mysql) in your .env and docker-compose.yml files reference.

After migrations complete, restart your containers. The /app page should then display the application list and user info as expected discussion troubleshooting.

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 3, 2025): <!-- Answer --> The 500 error on the /app page after upgrading to v1.10.1 is almost certainly due to missing database migrations. This version adds new columns (`created_by`, `updated_by`) to the `apps`, `app_model_configs`, and `sites` tables, which are required by the backend API and WebApp Auth features. If these migrations aren't applied, API queries will fail and cause the UI to break with a 500 error [example migration](https://github.com/langgenius/dify/blob/c7d2a135242bd28518a441f0305b75ffef0a0ff1/api/migrations/versions/2024_08_25_0441-d0187d6a88dd_add_created_by_and_updated_by_to_app_.py). To fix this, make sure you run all pending database migrations inside your API container. You can do this by running: ```bash docker compose exec api flask upgrade-db ``` or ```bash docker compose exec api uv run flask db upgrade ``` If you see migration errors (like missing tables or functions), you may need to stamp your database to the latest migration revision and then upgrade again. Also, ensure that your `DB_TYPE` environment variable matches your actual database type (e.g., `postgresql` or `mysql`) in your `.env` and `docker-compose.yml` files [reference](https://github.com/langgenius/dify/pull/28188). After migrations complete, restart your containers. The /app page should then display the application list and user info as expected [discussion](https://github.com/langgenius/dify/issues/27757) [troubleshooting](https://github.com/langgenius/dify/issues/24567#issuecomment-3223620624). <!-- 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/e2cf9bbd-755f-4bb2-b967-8f09c944e58b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e2cf9bbd-755f-4bb2-b967-8f09c944e58b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e2cf9bbd-755f-4bb2-b967-8f09c944e58b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e2cf9bbd-755f-4bb2-b967-8f09c944e58b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e2cf9bbd-755f-4bb2-b967-8f09c944e58b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e2cf9bbd-755f-4bb2-b967-8f09c944e58b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e2cf9bbd-755f-4bb2-b967-8f09c944e58b?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%20500%20error%20on%20the%20/app%20page%20after%20upgrading%20to%20v1.10.1%20is%20almost%20certainly%20due%20to%20missing%20database%20migrations.%20This%20version%20adds%20new%20columns%20%28%60created_by%60%2C%20%60updated_by%60%29%20to%20the%20%60apps%60%2C%20%60app_model_configs%60%2C%20and%20%60sites%60%20tables%2C%20which%20are%20required%20by%20the%20backend%20API%20and%20WebApp%20Auth%20features.%20If%20these%20migrations%20aren%27t%20applied%2C%20API%20queries%20will%20fail%20and%20cause%20the%20UI%20to%20break%20with%20a%20500%20error%C2%A0%5Bexample%20migration%5D%28https%3A//github.com/langgenius/dify/blob/c7d2a135242bd28518a441f0305b75ffef0a0ff1/api/migrations/versions/2024_08_25_0441-d0187d6a88dd_add_created_by_and_updated_by_to_app_.py%29.%0A%0ATo%20fix%20this%2C%20make%20sure%20you%20run%20all%20pending%20database%20migrations%20inside%20your%20API%20container.%20You%20can%20do%20this%20by%20running%3A%0A%0A%60%60%60bash%0Adocker%20compose%20exec%20api%20flask%20upgrade-db%0A%60%60%60%0Aor%0A%60%60%60bash%0Adocker%20compose%20exec%20api%20uv%20run%20flask%20db%20upgrade%0A%60%60%60%0A%0AIf%20you%20see%20migration%20errors%20%28like%20missing%20tables%20or%20functions%29%2C%20you%20may%20need%20to%20stamp%20your%20database%20to%20the%20latest%20migration%20revision%20and%20then%20upgrade%20again.%20Also%2C%20ensure%20that%20your%20%60DB_TYPE%60%20environment%20variable%20matches%20your%20actual%20database%20type%20%28e.g.%2C%20%60postgresql%60%20or%20%60mysql%60%29%20in%20your%20%60.env%60%20and%20%60docker-compose.yml%60%20files%C2%A0%5Breference%5D%28https%3A//github.com/langgenius/dify/pull/28188%29.%0A%0AAfter%20migrations%20complete%2C%20restart%20your%20containers.%20The%20/app%20page%20should%20then%20display%20the%20application%20list%20and%20user%20info%20as%20expected%C2%A0%5Bdiscussion%5D%28https%3A//github.com/langgenius/dify/issues/27757%29%C2%A0%5Btroubleshooting%5D%28https%3A//github.com/langgenius/dify/issues/24567%23issuecomment-3223620624%29.)&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/29059)
yindo commented 2026-02-21 20:08:51 -05:00
Author
Owner
Copy Link
Copy Source

@rainsun007 commented on GitHub (Dec 7, 2025):

@crazywoola

docker compose exec api flask upgrade-db
and
docker compose --profile postgresql up -d

We've tried everything, but the problem still hasn't been solved.

@rainsun007 commented on GitHub (Dec 7, 2025): @crazywoola `docker compose exec api flask upgrade-db ` and `docker compose --profile postgresql up -d` We've tried everything, but the problem still hasn't 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 🐞 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#20757
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?