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

git clone and cd docker module, run docker compose up -d, into into localhost report Internal Server Error #21536

New Issue
Closed
opened 2026-02-21 20:13:01 -05:00 by yindo · 27 comments
yindo commented 2026-02-21 20:13:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @hxhsome on GitHub (Jan 8, 2026).

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

main

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

git clone and cd docker module, run docker compose up -d, into into localhost report Internal Server Error

Image Image

✔️ Expected Behavior

dify is stabled

❌ Actual Behavior

No response

Originally created by @hxhsome on GitHub (Jan 8, 2026). ### 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 main ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce git clone and cd docker module, run docker compose up -d, into into localhost report Internal Server Error <img width="2386" height="700" alt="Image" src="https://github.com/user-attachments/assets/c0e17bb0-f815-4be3-89d0-28fe7e8bd727" /> <img width="3348" height="1088" alt="Image" src="https://github.com/user-attachments/assets/471bab02-1506-457e-8514-46ab357c1add" /> ### ✔️ Expected Behavior dify is stabled ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:13:01 -05:00
yindo closed this issue 2026-02-21 20:13:01 -05:00
yindo commented 2026-02-21 20:13:01 -05:00
Author
Owner
Copy Link
Copy Source

@hxhsome commented on GitHub (Jan 8, 2026):

Image
@hxhsome commented on GitHub (Jan 8, 2026): <img width="3808" height="1496" alt="Image" src="https://github.com/user-attachments/assets/0d34f0aa-7006-4ef4-ae1b-440c9dc74e15" />
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @hxhsome! I'm Dosu and I’m helping the dify team.

The Internal Server Error at /install is likely caused by a backend service failure, most probably due to the MySQL container exiting with code 137, which usually means it was killed because of insufficient memory or other resource constraints on your Docker host (source). This prevents the API from connecting to the database and causes the error you see in the browser.

Here’s what you should do next:

  1. Check your system’s available memory and disk space—make sure you have at least 6GB free (source).
  2. Run docker compose ps to see which containers are running or exited.
  3. Run docker compose logs api, docker compose logs db_mysql, and docker compose logs worker to get error messages and stack traces from the main containers.
  4. Check the API container log at /app/logs/server.log (inside the container) for backend error details.
  5. Make sure your storage directory (./volumes/app/storage) is writable by the container. If needed, run chown -R 1001:1001 ./volumes/app/storage on your host (source).
  6. Double-check your .env file for correct database settings. By default, Dify uses PostgreSQL, so if you want to use MySQL, make sure all related variables are set correctly (source).

If you share the output of the above logs and your .env (with sensitive info redacted), I can help pinpoint the exact cause.

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 (Jan 8, 2026): <!-- Greeting --> Hi @hxhsome! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The Internal Server Error at /install is likely caused by a backend service failure, most probably due to the MySQL container exiting with code 137, which usually means it was killed because of insufficient memory or other resource constraints on your Docker host ([source](https://github.com/langgenius/dify/issues/29606#issuecomment-3648948785)). This prevents the API from connecting to the database and causes the error you see in the browser. Here’s what you should do next: 1. Check your system’s available memory and disk space—make sure you have at least 6GB free ([source](https://github.com/langgenius/dify-docs/issues/246)). 2. Run `docker compose ps` to see which containers are running or exited. 3. Run `docker compose logs api`, `docker compose logs db_mysql`, and `docker compose logs worker` to get error messages and stack traces from the main containers. 4. Check the API container log at `/app/logs/server.log` (inside the container) for backend error details. 5. Make sure your storage directory (`./volumes/app/storage`) is writable by the container. If needed, run `chown -R 1001:1001 ./volumes/app/storage` on your host ([source](https://github.com/langgenius/dify/issues/29669#issuecomment-3654056467)). 6. Double-check your `.env` file for correct database settings. By default, Dify uses PostgreSQL, so if you want to use MySQL, make sure all related variables are set correctly ([source](https://github.com/langgenius/dify/blob/98df99b0ca2f13db64eba18e37489db5c534eadd/docker/.env.example#L0-L1292)). If you share the output of the above logs and your `.env` (with sensitive info redacted), I can help pinpoint the exact cause. <!-- 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/f9c4d143-3dba-43c1-9eb6-799ca51cf253?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f9c4d143-3dba-43c1-9eb6-799ca51cf253?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f9c4d143-3dba-43c1-9eb6-799ca51cf253?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f9c4d143-3dba-43c1-9eb6-799ca51cf253?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f9c4d143-3dba-43c1-9eb6-799ca51cf253?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f9c4d143-3dba-43c1-9eb6-799ca51cf253?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f9c4d143-3dba-43c1-9eb6-799ca51cf253?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%20Internal%20Server%20Error%20at%20/install%20is%20likely%20caused%20by%20a%20backend%20service%20failure%2C%20most%20probably%20due%20to%20the%20MySQL%20container%20exiting%20with%20code%20137%2C%20which%20usually%20means%20it%20was%20killed%20because%20of%20insufficient%20memory%20or%20other%20resource%20constraints%20on%20your%20Docker%20host%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/29606%23issuecomment-3648948785%29%29.%20This%20prevents%20the%20API%20from%20connecting%20to%20the%20database%20and%20causes%20the%20error%20you%20see%20in%20the%20browser.%0A%0AHere%E2%80%99s%20what%20you%20should%20do%20next%3A%0A1.%20Check%20your%20system%E2%80%99s%20available%20memory%20and%20disk%20space%E2%80%94make%20sure%20you%20have%20at%20least%206GB%20free%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify-docs/issues/246%29%29.%0A2.%20Run%20%60docker%20compose%20ps%60%20to%20see%20which%20containers%20are%20running%20or%20exited.%0A3.%20Run%20%60docker%20compose%20logs%20api%60%2C%20%60docker%20compose%20logs%20db_mysql%60%2C%20and%20%60docker%20compose%20logs%20worker%60%20to%20get%20error%20messages%20and%20stack%20traces%20from%20the%20main%20containers.%0A4.%20Check%20the%20API%20container%20log%20at%20%60/app/logs/server.log%60%20%28inside%20the%20container%29%20for%20backend%20error%20details.%0A5.%20Make%20sure%20your%20storage%20directory%20%28%60./volumes/app/storage%60%29%20is%20writable%20by%20the%20container.%20If%20needed%2C%20run%20%60chown%20-R%201001%3A1001%20./volumes/app/storage%60%20on%20your%20host%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/29669%23issuecomment-3654056467%29%29.%0A6.%20Double-check%20your%20%60.env%60%20file%20for%20correct%20database%20settings.%20By%20default%2C%20Dify%20uses%20PostgreSQL%2C%20so%20if%20you%20want%20to%20use%20MySQL%2C%20make%20sure%20all%20related%20variables%20are%20set%20correctly%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/98df99b0ca2f13db64eba18e37489db5c534eadd/docker/.env.example%23L0-L1292%29%29.%0A%0AIf%20you%20share%20the%20output%20of%20the%20above%20logs%20and%20your%20%60.env%60%20%28with%20sensitive%20info%20redacted%29%2C%20I%20can%20help%20pinpoint%20the%20exact%20cause.)&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/30768)
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@hxhsome commented on GitHub (Jan 9, 2026):

Image Image Image
@hxhsome commented on GitHub (Jan 9, 2026): <img width="3450" height="896" alt="Image" src="https://github.com/user-attachments/assets/53333ca5-3bc0-4f33-83b7-bbe4103f76d0" /> <img width="2974" height="1246" alt="Image" src="https://github.com/user-attachments/assets/c2f35d04-0db1-4322-a2d1-3d99ad96245a" /> <img width="3038" height="1274" alt="Image" src="https://github.com/user-attachments/assets/7266d452-6bf1-4de1-b4e4-2e0a700743aa" />
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@hxhsome commented on GitHub (Jan 9, 2026):

use all default setting

@hxhsome commented on GitHub (Jan 9, 2026): use all default setting
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 9, 2026):

use all default setting

the postgresql docker is not start, please check it

@fatelei commented on GitHub (Jan 9, 2026): > use all default setting the postgresql docker is not start, please check it
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@huxianghao commented on GitHub (Jan 9, 2026):

use all default setting

the postgresql docker is not start, please check it

Do I need to install a separate postgre image? I'm running docker compose up -d directly under the docker directory

@huxianghao commented on GitHub (Jan 9, 2026): > > use all default setting > > the postgresql docker is not start, please check it Do I need to install a separate postgre image? I'm running docker compose up -d directly under the docker directory
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 9, 2026):

use all default setting

the postgresql docker is not start, please check it

Do I need to install a separate postgre image? I'm running docker compose up -d directly under the docker directory

no，dify compose has postgresql config

Image
@fatelei commented on GitHub (Jan 9, 2026): > > > use all default setting > > > > > > the postgresql docker is not start, please check it > > Do I need to install a separate postgre image? I'm running docker compose up -d directly under the docker directory no，dify compose has postgresql config <img width="1642" height="1046" alt="Image" src="https://github.com/user-attachments/assets/dc935033-a049-4bb3-b498-e00d4897af96" />
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@huxianghao commented on GitHub (Jan 9, 2026):

use all default setting

the postgresql docker is not start, please check it

Do I need to install a separate postgre image? I'm running docker compose up -d directly under the docker directory

no，dify compose has postgresql config

Image

I don't think there is a need to get a separate postgre image, but after I use docker compose up -d, the error means that postgre cannot be connected. Why is the error now connected to postgre?

@huxianghao commented on GitHub (Jan 9, 2026): > > > > use all default setting > > > > > > > > > the postgresql docker is not start, please check it > > > > > > Do I need to install a separate postgre image? I'm running docker compose up -d directly under the docker directory > > no，dify compose has postgresql config > > <img alt="Image" width="1642" height="1046" src="https://private-user-images.githubusercontent.com/961094/533750941-dc935033-a049-4bb3-b498-e00d4897af96.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5Mzk3NTIsIm5iZiI6MTc2NzkzOTQ1MiwicGF0aCI6Ii85NjEwOTQvNTMzNzUwOTQxLWRjOTM1MDMzLWEwNDktNGJiMy1iNDk4LWUwMGQ0ODk3YWY5Ni5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjE3MzJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hNWU4OTVjNDUzZTFhOThhYjQ2ZDE3ZDllYzMzZDYzZTBjNjg1MTQwYjc2NjIyZWNhNTg0MjAyYmUyNDI5YmNmJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.itYomCdGn6EQ3rAZXg9U6wK7B93Aj68xv-b9A_FEC-g"> I don't think there is a need to get a separate postgre image, but after I use docker compose up -d, the error means that postgre cannot be connected. Why is the error now connected to postgre?
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@huxianghao commented on GitHub (Jan 9, 2026):

Image Except for the mysql image, the others are automatically downloaded by executing docker compose up -d
@huxianghao commented on GitHub (Jan 9, 2026): <img width="1722" height="482" alt="Image" src="https://github.com/user-attachments/assets/0dda0301-f158-4d8f-819f-bd0e86671cdd" /> Except for the mysql image, the others are automatically downloaded by executing docker compose up -d
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 9, 2026):

docker ps -a

@fatelei commented on GitHub (Jan 9, 2026): docker ps -a
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@huxianghao commented on GitHub (Jan 9, 2026):

Image This screenshot is attached to the question, except that mysql is opened by me alone, and it has nothing to do with dify
@huxianghao commented on GitHub (Jan 9, 2026): <img width="1893" height="532" alt="Image" src="https://github.com/user-attachments/assets/99134b5a-a742-4a5f-ad02-d12292800813" /> This screenshot is attached to the question, except that mysql is opened by me alone, and it has nothing to do with dify
yindo commented 2026-02-21 20:13:02 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 9, 2026):

Image This screenshot is attached to the question, except that mysql is opened by me alone, and it has nothing to do with dify

docker compose up -d db_postgres

@fatelei commented on GitHub (Jan 9, 2026): > <img alt="Image" width="1893" height="532" src="https://private-user-images.githubusercontent.com/208585483/533754468-99134b5a-a742-4a5f-ad02-d12292800813.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDAyODUsIm5iZiI6MTc2NzkzOTk4NSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU0NDY4LTk5MTM0YjVhLWE3NDItNGE1Zi1hZDAyLWQxMjI5MjgwMDgxMy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjI2MjVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wMzU3ZjQ3OTNjOTI0ZGRhNjVhYTUzNDcxYzMzZWI3MzZjNTg3NjNmZDY3ZWZmYmQyYzhlOTQwNGE3YTJkNTYzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.pM171KiTSXn710cY56QK61VX3_Z-XAUsHcmwzW62WtM"> This screenshot is attached to the question, except that mysql is opened by me alone, and it has nothing to do with dify docker compose up -d db_postgres
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 9, 2026):

cd to dify docker directory

@fatelei commented on GitHub (Jan 9, 2026): cd to dify docker directory
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@huxianghao commented on GitHub (Jan 9, 2026):

Image

docker compose up -d db_postgres Run, enter the logs of localhost in your browser

Image
@huxianghao commented on GitHub (Jan 9, 2026): <img width="1910" height="733" alt="Image" src="https://github.com/user-attachments/assets/314e7b75-6d90-4f87-a03e-9d686e5cddf5" /> docker compose up -d db_postgres Run, enter the logs of localhost in your browser <img width="1914" height="1018" alt="Image" src="https://github.com/user-attachments/assets/8899e369-a3c2-4a4e-8aef-b974dd68c195" />
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 9, 2026):

Image docker compose up -d db_postgres Run, enter the logs of localhost in your browser Image

need do database migration

docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade'
@fatelei commented on GitHub (Jan 9, 2026): > <img alt="Image" width="1910" height="733" src="https://private-user-images.githubusercontent.com/208585483/533756134-314e7b75-6d90-4f87-a03e-9d686e5cddf5.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2MTM0LTMxNGU3Yjc1LTZkOTAtNGY4Ny1hMDNlLTlkNjg2ZTVjZGRmNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lZjhmNTI4NGI5Nzc4NjFmZWE2NmQ5M2NiODBlNmM1MmMyNmM4NTY5Y2U2NTc3ODJkYzk1ZDJmZTRjODMzOGFiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.wxAX2utQoJU5yphcILrNMGVFs-36o_7APVaWK1LS7JQ"> > docker compose up -d db_postgres Run, enter the logs of localhost in your browser > > <img alt="Image" width="1914" height="1018" src="https://private-user-images.githubusercontent.com/208585483/533756801-8899e369-a3c2-4a4e-8aef-b974dd68c195.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2ODAxLTg4OTllMzY5LWEzYzItNGE0ZS04YWVmLWI5NzRkZDY4YzE5NS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iY2M1ZDcyOTFmNGY3YmZkNjAwOTdlYWQyNWM3NzVmN2YzMjNmNmMzM2M2MDZhOGU3YTQ5YzVlNDRlNTBiZTgxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.iS2zxeJDojcB0osy8kI-b4lh5kMjXfqQbUCCR5McmJ8"> need do database migration ``` docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade' ```
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@huxianghao commented on GitHub (Jan 9, 2026):

Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly

@huxianghao commented on GitHub (Jan 9, 2026): Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 9, 2026):

Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly

me too

@fatelei commented on GitHub (Jan 9, 2026): > Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly me too
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 9, 2026):

Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly

i find it

db_postgres:
  image: postgres:15-alpine
  profiles:
    - postgresql

because there is a profiles config, it means postgresql start on demand, if you want to auto start postgresql, you should

export COMPOSE_PROFILES=postgresql
docker compose up -d
@fatelei commented on GitHub (Jan 9, 2026): > Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly i find it ``` db_postgres: image: postgres:15-alpine profiles: - postgresql ``` because there is a profiles config, it means postgresql start on demand, if you want to auto start postgresql, you should ``` export COMPOSE_PROFILES=postgresql docker compose up -d ```
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@huxianghao commented on GitHub (Jan 9, 2026):

Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly

i find it

db_postgres:
  image: postgres:15-alpine
  profiles:
    - postgresql

because there is a profiles config, it means postgresql start on demand, if you want to auto start postgresql, you should

export COMPOSE_PROFILES=postgresql
docker compose up -d

So back to the question, shouldn't redis database be used by default?

@huxianghao commented on GitHub (Jan 9, 2026): > > Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly > > i find it > > ``` > db_postgres: > image: postgres:15-alpine > profiles: > - postgresql > ``` > > because there is a profiles config, it means postgresql start on demand, if you want to auto start postgresql, you should > > ``` > export COMPOSE_PROFILES=postgresql > docker compose up -d > ``` So back to the question, shouldn't redis database be used by default?
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 9, 2026):

Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly

i find it

db_postgres:
  image: postgres:15-alpine
  profiles:
    - postgresql

because there is a profiles config, it means postgresql start on demand, if you want to auto start postgresql, you should

export COMPOSE_PROFILES=postgresql
docker compose up -d

So back to the question, shouldn't redis database be used by default?

i see the redis docker is started, dify will use this redis

@fatelei commented on GitHub (Jan 9, 2026): > > > Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly > > > > > > i find it > > ``` > > db_postgres: > > image: postgres:15-alpine > > profiles: > > - postgresql > > ``` > > > > > > > > > > > > > > > > > > > > > > > > because there is a profiles config, it means postgresql start on demand, if you want to auto start postgresql, you should > > ``` > > export COMPOSE_PROFILES=postgresql > > docker compose up -d > > ``` > > So back to the question, shouldn't redis database be used by default? i see the redis docker is started, dify will use this redis
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@huxianghao commented on GitHub (Jan 9, 2026):

Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly

i find it

db_postgres:
  image: postgres:15-alpine
  profiles:
    - postgresql

because there is a profiles config, it means postgresql start on demand, if you want to auto start postgresql, you should

export COMPOSE_PROFILES=postgresql
docker compose up -d

So back to the question, shouldn't redis database be used by default?

i see the redis docker is started, dify will use this redis

At present, I am testing that after using docker compose up -d, the error is that I can't connect with postgre. Only resolved the error after starting and initializing postgre with the script you gave me

@huxianghao commented on GitHub (Jan 9, 2026): > > > > Now it's good, thank you very much. But I still can't understand why docker compose up -d can't be used directly > > > > > > > > > i find it > > > ``` > > > db_postgres: > > > image: postgres:15-alpine > > > profiles: > > > - postgresql > > > ``` > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > because there is a profiles config, it means postgresql start on demand, if you want to auto start postgresql, you should > > > ``` > > > export COMPOSE_PROFILES=postgresql > > > docker compose up -d > > > ``` > > > > > > So back to the question, shouldn't redis database be used by default? > > i see the redis docker is started, dify will use this redis At present, I am testing that after using docker compose up -d, the error is that I can't connect with postgre. Only resolved the error after starting and initializing postgre with the script you gave me
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@SeymourNeal commented on GitHub (Jan 10, 2026):

Image docker compose up -d db_postgres Run, enter the logs of localhost in your browser Image

need do database migration

docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade'

same error, but was not solved with that

Image Image Image
@SeymourNeal commented on GitHub (Jan 10, 2026): > > <img alt="Image" width="1910" height="733" src="https://private-user-images.githubusercontent.com/208585483/533756134-314e7b75-6d90-4f87-a03e-9d686e5cddf5.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2MTM0LTMxNGU3Yjc1LTZkOTAtNGY4Ny1hMDNlLTlkNjg2ZTVjZGRmNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lZjhmNTI4NGI5Nzc4NjFmZWE2NmQ5M2NiODBlNmM1MmMyNmM4NTY5Y2U2NTc3ODJkYzk1ZDJmZTRjODMzOGFiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.wxAX2utQoJU5yphcILrNMGVFs-36o_7APVaWK1LS7JQ"> > > docker compose up -d db_postgres Run, enter the logs of localhost in your browser > > <img alt="Image" width="1914" height="1018" src="https://private-user-images.githubusercontent.com/208585483/533756801-8899e369-a3c2-4a4e-8aef-b974dd68c195.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2ODAxLTg4OTllMzY5LWEzYzItNGE0ZS04YWVmLWI5NzRkZDY4YzE5NS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iY2M1ZDcyOTFmNGY3YmZkNjAwOTdlYWQyNWM3NzVmN2YzMjNmNmMzM2M2MDZhOGU3YTQ5YzVlNDRlNTBiZTgxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.iS2zxeJDojcB0osy8kI-b4lh5kMjXfqQbUCCR5McmJ8"> > > need do database migration > > ``` > docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade' > ``` same error, but was not solved with that <img width="2029" height="1311" alt="Image" src="https://github.com/user-attachments/assets/ac9ca792-d24d-4442-9cff-c2efc6f97f2a" /> <img width="2419" height="1173" alt="Image" src="https://github.com/user-attachments/assets/e8ca114e-9718-4a5d-8ba2-a37d35481a72" /> <img width="2555" height="1359" alt="Image" src="https://github.com/user-attachments/assets/770a28fd-77aa-459f-8091-a204db355d2d" />
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 10, 2026):

Image docker compose up -d db_postgres Run, enter the logs of localhost in your browser Image

need do database migration

docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade'

same error, but was not solved with that

Image Image Image

database should be db_postgres not postgres

@fatelei commented on GitHub (Jan 10, 2026): > > > <img alt="Image" width="1910" height="733" src="https://private-user-images.githubusercontent.com/208585483/533756134-314e7b75-6d90-4f87-a03e-9d686e5cddf5.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2MTM0LTMxNGU3Yjc1LTZkOTAtNGY4Ny1hMDNlLTlkNjg2ZTVjZGRmNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lZjhmNTI4NGI5Nzc4NjFmZWE2NmQ5M2NiODBlNmM1MmMyNmM4NTY5Y2U2NTc3ODJkYzk1ZDJmZTRjODMzOGFiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.wxAX2utQoJU5yphcILrNMGVFs-36o_7APVaWK1LS7JQ"> > > > docker compose up -d db_postgres Run, enter the logs of localhost in your browser > > > <img alt="Image" width="1914" height="1018" src="https://private-user-images.githubusercontent.com/208585483/533756801-8899e369-a3c2-4a4e-8aef-b974dd68c195.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2ODAxLTg4OTllMzY5LWEzYzItNGE0ZS04YWVmLWI5NzRkZDY4YzE5NS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iY2M1ZDcyOTFmNGY3YmZkNjAwOTdlYWQyNWM3NzVmN2YzMjNmNmMzM2M2MDZhOGU3YTQ5YzVlNDRlNTBiZTgxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.iS2zxeJDojcB0osy8kI-b4lh5kMjXfqQbUCCR5McmJ8"> > > > > > > need do database migration > > ``` > > docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade' > > ``` > > same error, but was not solved with that > > <img alt="Image" width="2000" height="1311" src="https://private-user-images.githubusercontent.com/183902802/534224837-ac9ca792-d24d-4442-9cff-c2efc6f97f2a.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgwNTM4MTEsIm5iZiI6MTc2ODA1MzUxMSwicGF0aCI6Ii8xODM5MDI4MDIvNTM0MjI0ODM3LWFjOWNhNzkyLWQyNGQtNDQ0Mi05Y2ZmLWMyZWZjNmY5N2YyYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExMFQxMzU4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hY2YyNTIzOWQ5YzQ2YTVkOWQzOWI4ZDBmNzBkOTJjNjc4YzM5MWJjNjY1ZGIwNzg4ODJmYmI2NmUxZjZhMjZhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.qy-qqOPh3cfSP4WLzWQbAtOwYAnIqvOfIsGo9rlk3AI"> <img alt="Image" width="2000" height="1173" src="https://private-user-images.githubusercontent.com/183902802/534225021-e8ca114e-9718-4a5d-8ba2-a37d35481a72.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgwNTM4MTEsIm5iZiI6MTc2ODA1MzUxMSwicGF0aCI6Ii8xODM5MDI4MDIvNTM0MjI1MDIxLWU4Y2ExMTRlLTk3MTgtNGE1ZC04YmEyLWEzN2QzNTQ4MWE3Mi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExMFQxMzU4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01M2VhNDFlODMwMDhiODAwYmUxYjdhNTBmOGRjNjU4ODYyYjM0OGQ3NmYxMTk4ZmQ1ZDcxNzhjMDJlZTRkZDc5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.b585hjRZOcXgm6PwH1xva88ETBCu6Zzj8Ao8WUUDgms"> <img alt="Image" width="2000" height="1359" src="https://private-user-images.githubusercontent.com/183902802/534225036-770a28fd-77aa-459f-8091-a204db355d2d.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgwNTM4MTEsIm5iZiI6MTc2ODA1MzUxMSwicGF0aCI6Ii8xODM5MDI4MDIvNTM0MjI1MDM2LTc3MGEyOGZkLTc3YWEtNDU5Zi04MDkxLWEyMDRkYjM1NWQyZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExMFQxMzU4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yN2MzMGY0ZjU3MTM5YzA5NGM2MzE1NzI2YzhlY2Q0NWY0NGU0MDUyMWEyNTIxZGU1MmRkNzk1MjdkYmRjNTFiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.AiE8q9PTJ7yzyG9Cp5RGGZ79GUyCEVqT7jMneiKNREQ"> database should be db_postgres not postgres
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@SeymourNeal commented on GitHub (Jan 10, 2026):

Image docker compose up -d db_postgres Run, enter the logs of localhost in your browser Image

need do database migration

docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade'

same error, but was not solved with that
Image Image Image

database should be db_postgres not postgres

how do i change that?

@SeymourNeal commented on GitHub (Jan 10, 2026): > > > > <img alt="Image" width="1910" height="733" src="https://private-user-images.githubusercontent.com/208585483/533756134-314e7b75-6d90-4f87-a03e-9d686e5cddf5.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2MTM0LTMxNGU3Yjc1LTZkOTAtNGY4Ny1hMDNlLTlkNjg2ZTVjZGRmNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lZjhmNTI4NGI5Nzc4NjFmZWE2NmQ5M2NiODBlNmM1MmMyNmM4NTY5Y2U2NTc3ODJkYzk1ZDJmZTRjODMzOGFiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.wxAX2utQoJU5yphcILrNMGVFs-36o_7APVaWK1LS7JQ"> > > > > docker compose up -d db_postgres Run, enter the logs of localhost in your browser > > > > <img alt="Image" width="1914" height="1018" src="https://private-user-images.githubusercontent.com/208585483/533756801-8899e369-a3c2-4a4e-8aef-b974dd68c195.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2ODAxLTg4OTllMzY5LWEzYzItNGE0ZS04YWVmLWI5NzRkZDY4YzE5NS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iY2M1ZDcyOTFmNGY3YmZkNjAwOTdlYWQyNWM3NzVmN2YzMjNmNmMzM2M2MDZhOGU3YTQ5YzVlNDRlNTBiZTgxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.iS2zxeJDojcB0osy8kI-b4lh5kMjXfqQbUCCR5McmJ8"> > > > > > > > > > need do database migration > > > ``` > > > docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade' > > > ``` > > > > > > same error, but was not solved with that > > <img alt="Image" width="2000" height="1311" src="https://private-user-images.githubusercontent.com/183902802/534224837-ac9ca792-d24d-4442-9cff-c2efc6f97f2a.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgwNTM4MTEsIm5iZiI6MTc2ODA1MzUxMSwicGF0aCI6Ii8xODM5MDI4MDIvNTM0MjI0ODM3LWFjOWNhNzkyLWQyNGQtNDQ0Mi05Y2ZmLWMyZWZjNmY5N2YyYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExMFQxMzU4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hY2YyNTIzOWQ5YzQ2YTVkOWQzOWI4ZDBmNzBkOTJjNjc4YzM5MWJjNjY1ZGIwNzg4ODJmYmI2NmUxZjZhMjZhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.qy-qqOPh3cfSP4WLzWQbAtOwYAnIqvOfIsGo9rlk3AI"> <img alt="Image" width="2000" height="1173" src="https://private-user-images.githubusercontent.com/183902802/534225021-e8ca114e-9718-4a5d-8ba2-a37d35481a72.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgwNTM4MTEsIm5iZiI6MTc2ODA1MzUxMSwicGF0aCI6Ii8xODM5MDI4MDIvNTM0MjI1MDIxLWU4Y2ExMTRlLTk3MTgtNGE1ZC04YmEyLWEzN2QzNTQ4MWE3Mi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExMFQxMzU4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01M2VhNDFlODMwMDhiODAwYmUxYjdhNTBmOGRjNjU4ODYyYjM0OGQ3NmYxMTk4ZmQ1ZDcxNzhjMDJlZTRkZDc5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.b585hjRZOcXgm6PwH1xva88ETBCu6Zzj8Ao8WUUDgms"> <img alt="Image" width="2000" height="1359" src="https://private-user-images.githubusercontent.com/183902802/534225036-770a28fd-77aa-459f-8091-a204db355d2d.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgwNTM4MTEsIm5iZiI6MTc2ODA1MzUxMSwicGF0aCI6Ii8xODM5MDI4MDIvNTM0MjI1MDM2LTc3MGEyOGZkLTc3YWEtNDU5Zi04MDkxLWEyMDRkYjM1NWQyZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExMFQxMzU4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yN2MzMGY0ZjU3MTM5YzA5NGM2MzE1NzI2YzhlY2Q0NWY0NGU0MDUyMWEyNTIxZGU1MmRkNzk1MjdkYmRjNTFiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.AiE8q9PTJ7yzyG9Cp5RGGZ79GUyCEVqT7jMneiKNREQ"> > > database should be db_postgres not postgres how do i change that?
yindo commented 2026-02-21 20:13:03 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 10, 2026):

in directory docker, there is .env file, if you do not have this file, copy .env.example to .env

Image
@fatelei commented on GitHub (Jan 10, 2026): in directory docker, there is .env file, if you do not have this file, copy .env.example to .env <img width="728" height="366" alt="Image" src="https://github.com/user-attachments/assets/d1583ae1-523f-4047-aa2b-1b2acc273bd0" />
yindo commented 2026-02-21 20:13:04 -05:00
Author
Owner
Copy Link
Copy Source

@pzc163 commented on GitHub (Jan 10, 2026):

same error,can‘t open install page with new docker self-hosted 1.11.2 version
Image

@pzc163 commented on GitHub (Jan 10, 2026): same error,can‘t open install page with new docker self-hosted 1.11.2 version <img width="3014" height="632" alt="Image" src="https://github.com/user-attachments/assets/ba844e0e-7ffc-498b-95ad-c055aa74c4ff" />
yindo commented 2026-02-21 20:13:04 -05:00
Author
Owner
Copy Link
Copy Source

@SeymourNeal commented on GitHub (Jan 11, 2026):

Image docker compose up -d db_postgres Run, enter the logs of localhost in your browser Image

need do database migration

docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade'

same error, but was not solved with that
Image Image Image

database should be db_postgres not postgres

It works, thanks!
p.s. by the way if somebody has the same issue with me, don't forget restart docker-compose using "docker-compose down and docker-compose up -d "to restart after changing the db name.

@SeymourNeal commented on GitHub (Jan 11, 2026): > > > > <img alt="Image" width="1910" height="733" src="https://private-user-images.githubusercontent.com/208585483/533756134-314e7b75-6d90-4f87-a03e-9d686e5cddf5.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2MTM0LTMxNGU3Yjc1LTZkOTAtNGY4Ny1hMDNlLTlkNjg2ZTVjZGRmNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lZjhmNTI4NGI5Nzc4NjFmZWE2NmQ5M2NiODBlNmM1MmMyNmM4NTY5Y2U2NTc3ODJkYzk1ZDJmZTRjODMzOGFiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.wxAX2utQoJU5yphcILrNMGVFs-36o_7APVaWK1LS7JQ"> > > > > docker compose up -d db_postgres Run, enter the logs of localhost in your browser > > > > <img alt="Image" width="1914" height="1018" src="https://private-user-images.githubusercontent.com/208585483/533756801-8899e369-a3c2-4a4e-8aef-b974dd68c195.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc5NDEyNTEsIm5iZiI6MTc2Nzk0MDk1MSwicGF0aCI6Ii8yMDg1ODU0ODMvNTMzNzU2ODAxLTg4OTllMzY5LWEzYzItNGE0ZS04YWVmLWI5NzRkZDY4YzE5NS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEwOVQwNjQyMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iY2M1ZDcyOTFmNGY3YmZkNjAwOTdlYWQyNWM3NzVmN2YzMjNmNmMzM2M2MDZhOGU3YTQ5YzVlNDRlNTBiZTgxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.iS2zxeJDojcB0osy8kI-b4lh5kMjXfqQbUCCR5McmJ8"> > > > > > > > > > need do database migration > > > ``` > > > docker exec docker-api-1 sh -lc 'UV_CACHE_DIR=/tmp/uv uv run --project api flask db upgrade' > > > ``` > > > > > > same error, but was not solved with that > > <img alt="Image" width="2000" height="1311" src="https://private-user-images.githubusercontent.com/183902802/534224837-ac9ca792-d24d-4442-9cff-c2efc6f97f2a.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgwNTM4MTEsIm5iZiI6MTc2ODA1MzUxMSwicGF0aCI6Ii8xODM5MDI4MDIvNTM0MjI0ODM3LWFjOWNhNzkyLWQyNGQtNDQ0Mi05Y2ZmLWMyZWZjNmY5N2YyYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExMFQxMzU4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hY2YyNTIzOWQ5YzQ2YTVkOWQzOWI4ZDBmNzBkOTJjNjc4YzM5MWJjNjY1ZGIwNzg4ODJmYmI2NmUxZjZhMjZhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.qy-qqOPh3cfSP4WLzWQbAtOwYAnIqvOfIsGo9rlk3AI"> <img alt="Image" width="2000" height="1173" src="https://private-user-images.githubusercontent.com/183902802/534225021-e8ca114e-9718-4a5d-8ba2-a37d35481a72.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgwNTM4MTEsIm5iZiI6MTc2ODA1MzUxMSwicGF0aCI6Ii8xODM5MDI4MDIvNTM0MjI1MDIxLWU4Y2ExMTRlLTk3MTgtNGE1ZC04YmEyLWEzN2QzNTQ4MWE3Mi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExMFQxMzU4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01M2VhNDFlODMwMDhiODAwYmUxYjdhNTBmOGRjNjU4ODYyYjM0OGQ3NmYxMTk4ZmQ1ZDcxNzhjMDJlZTRkZDc5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.b585hjRZOcXgm6PwH1xva88ETBCu6Zzj8Ao8WUUDgms"> <img alt="Image" width="2000" height="1359" src="https://private-user-images.githubusercontent.com/183902802/534225036-770a28fd-77aa-459f-8091-a204db355d2d.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgwNTM4MTEsIm5iZiI6MTc2ODA1MzUxMSwicGF0aCI6Ii8xODM5MDI4MDIvNTM0MjI1MDM2LTc3MGEyOGZkLTc3YWEtNDU5Zi04MDkxLWEyMDRkYjM1NWQyZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDExMFQxMzU4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yN2MzMGY0ZjU3MTM5YzA5NGM2MzE1NzI2YzhlY2Q0NWY0NGU0MDUyMWEyNTIxZGU1MmRkNzk1MjdkYmRjNTFiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.AiE8q9PTJ7yzyG9Cp5RGGZ79GUyCEVqT7jMneiKNREQ"> > > database should be db_postgres not postgres It works, thanks! p.s. by the way if somebody has the same issue with me, don't forget restart docker-compose using "docker-compose down and docker-compose up -d "to restart after changing the db name.
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#21536
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?