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

can‘t start install page with new self-hosted docker #21565

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

Originally created by @pzc163 on GitHub (Jan 10, 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

1.11.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

as screenshot show ,can‘t start install page for new self-hosted with docker

Image

✔️ Expected Behavior

fix this problem

❌ Actual Behavior

No response

Originally created by @pzc163 on GitHub (Jan 10, 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 1.11.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce as screenshot show ,can‘t start install page for new self-hosted with docker <img width="3070" height="708" alt="Image" src="https://github.com/user-attachments/assets/74e35577-1566-4409-93cb-fc5d954c7d9c" /> ### ✔️ Expected Behavior fix this problem ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:13:14 -05:00
yindo closed this issue 2026-02-21 20:13:14 -05:00
yindo commented 2026-02-21 20:13:14 -05:00
Author
Owner
Copy Link
Copy Source

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

The install page in Dify relies on several backend API endpoints and environment variables. If you see only the logo and copyright, it usually means the frontend can't reach the backend APIs it needs to load the install form.

Here’s a checklist to help you troubleshoot:

  1. Check Docker Compose port mappings: Make sure your docker-compose.yaml exposes all required ports, especially 5001 for the API service. For example, under the api service, you should have:

    ports:
  - "5001:5001"

    Not exposing this port can cause connection errors and a non-functional UI (reference).

  2. Verify environment variables: In your .env file, ensure these are set correctly:

    • For Docker Compose: FILES_URL=http://api:5001
    • For other methods: FILES_URL=http://<host>:5001
      Incorrect values here can break file uploads and some API calls (reference).

  3. Frontend API prefix: The frontend depends on environment variables like NEXT_PUBLIC_API_PREFIX and NEXT_PUBLIC_BASE_PATH. If these are misconfigured, the frontend won’t be able to reach the backend. They are injected into the frontend at build time and must match your Docker/proxy setup (reference).

  4. Check container health: Make sure all containers (frontend, backend/API, database) are running and healthy. If the backend or database is down, the install page cannot function.

  5. Browser and Docker logs: Open your browser’s developer console and look for failed network requests or JavaScript errors when loading the install page. Also, check the logs for your frontend and backend containers for any errors related to /setup, /init, or /system-features endpoints.

  6. Recent code changes: There was a recent fix related to the install/setup flow and password handling (reference). Make sure your containers are using the latest images for version 1.11.2.

If you still see only the minimal UI, please share any errors from your browser console and the logs from your backend container. This will help pinpoint whether it’s a networking, configuration, or backend issue.

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 10, 2026): <!-- Answer --> The install page in Dify relies on several backend API endpoints and environment variables. If you see only the logo and copyright, it usually means the frontend can't reach the backend APIs it needs to load the install form. Here’s a checklist to help you troubleshoot: 1. **Check Docker Compose port mappings:** Make sure your `docker-compose.yaml` exposes all required ports, especially `5001` for the API service. For example, under the `api` service, you should have: ``` ports: - "5001:5001" ``` Not exposing this port can cause connection errors and a non-functional UI [(reference)](https://github.com/langgenius/dify-official-plugins/issues/1816). 2. **Verify environment variables:** In your `.env` file, ensure these are set correctly: - For Docker Compose: `FILES_URL=http://api:5001` - For other methods: `FILES_URL=http://<host>:5001` Incorrect values here can break file uploads and some API calls [(reference)](https://github.com/langgenius/dify-official-plugins/issues/1816). 3. **Frontend API prefix:** The frontend depends on environment variables like `NEXT_PUBLIC_API_PREFIX` and `NEXT_PUBLIC_BASE_PATH`. If these are misconfigured, the frontend won’t be able to reach the backend. They are injected into the frontend at build time and must match your Docker/proxy setup [(reference)](https://github.com/langgenius/dify/blob/a2e03b811e581674603617a4b13d9d25760c44be/web/app/layout.tsx#L43-L130). 4. **Check container health:** Make sure all containers (frontend, backend/API, database) are running and healthy. If the backend or database is down, the install page cannot function. 5. **Browser and Docker logs:** Open your browser’s developer console and look for failed network requests or JavaScript errors when loading the install page. Also, check the logs for your frontend and backend containers for any errors related to `/setup`, `/init`, or `/system-features` endpoints. 6. **Recent code changes:** There was a recent fix related to the install/setup flow and password handling [(reference)](https://github.com/langgenius/dify/pull/30523). Make sure your containers are using the latest images for version 1.11.2. If you still see only the minimal UI, please share any errors from your browser console and the logs from your backend container. This will help pinpoint whether it’s a networking, configuration, or backend issue. <!-- 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/965ace5d-c1e0-4553-a04e-4388cdec9949?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/965ace5d-c1e0-4553-a04e-4388cdec9949?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/965ace5d-c1e0-4553-a04e-4388cdec9949?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/965ace5d-c1e0-4553-a04e-4388cdec9949?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/965ace5d-c1e0-4553-a04e-4388cdec9949?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/965ace5d-c1e0-4553-a04e-4388cdec9949?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/965ace5d-c1e0-4553-a04e-4388cdec9949?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%20install%20page%20in%20Dify%20relies%20on%20several%20backend%20API%20endpoints%20and%20environment%20variables.%20If%20you%20see%20only%20the%20logo%20and%20copyright%2C%20it%20usually%20means%20the%20frontend%20can%27t%20reach%20the%20backend%20APIs%20it%20needs%20to%20load%20the%20install%20form.%0A%0AHere%E2%80%99s%20a%20checklist%20to%20help%20you%20troubleshoot%3A%0A%0A1.%20%2A%2ACheck%20Docker%20Compose%20port%20mappings%3A%2A%2A%20Make%20sure%20your%20%60docker-compose.yaml%60%20exposes%20all%20required%20ports%2C%20especially%20%605001%60%20for%20the%20API%20service.%20For%20example%2C%20under%20the%20%60api%60%20service%2C%20you%20should%20have%3A%0A%20%20%20%60%60%60%0A%20%20%20ports%3A%0A%20%20%20%20%20-%20%225001%3A5001%22%0A%20%20%20%60%60%60%0A%20%20%20Not%20exposing%20this%20port%20can%20cause%20connection%20errors%20and%20a%20non-functional%20UI%20%5B%28reference%29%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1816%29.%0A%0A2.%20%2A%2AVerify%20environment%20variables%3A%2A%2A%20In%20your%20%60.env%60%20file%2C%20ensure%20these%20are%20set%20correctly%3A%0A%20%20%20-%20For%20Docker%20Compose%3A%20%60FILES_URL%3Dhttp%3A//api%3A5001%60%0A%20%20%20-%20For%20other%20methods%3A%20%60FILES_URL%3Dhttp%3A//%3Chost%3E%3A5001%60%0A%20%20%20Incorrect%20values%20here%20can%20break%20file%20uploads%20and%20some%20API%20calls%20%5B%28reference%29%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1816%29.%0A%0A3.%20%2A%2AFrontend%20API%20prefix%3A%2A%2A%20The%20frontend%20depends%20on%20environment%20variables%20like%20%60NEXT_PUBLIC_API_PREFIX%60%20and%20%60NEXT_PUBLIC_BASE_PATH%60.%20If%20these%20are%20misconfigured%2C%20the%20frontend%20won%E2%80%99t%20be%20able%20to%20reach%20the%20backend.%20They%20are%20injected%20into%20the%20frontend%20at%20build%20time%20and%20must%20match%20your%20Docker/proxy%20setup%20%5B%28reference%29%5D%28https%3A//github.com/langgenius/dify/blob/a2e03b811e581674603617a4b13d9d25760c44be/web/app/layout.tsx%23L43-L130%29.%0A%0A4.%20%2A%2ACheck%20container%20health%3A%2A%2A%20Make%20sure%20all%20containers%20%28frontend%2C%20backend/API%2C%20database%29%20are%20running%20and%20healthy.%20If%20the%20backend%20or%20database%20is%20down%2C%20the%20install%20page%20cannot%20function.%0A%0A5.%20%2A%2ABrowser%20and%20Docker%20logs%3A%2A%2A%20Open%20your%20browser%E2%80%99s%20developer%20console%20and%20look%20for%20failed%20network%20requests%20or%20JavaScript%20errors%20when%20loading%20the%20install%20page.%20Also%2C%20check%20the%20logs%20for%20your%20frontend%20and%20backend%20containers%20for%20any%20errors%20related%20to%20%60/setup%60%2C%20%60/init%60%2C%20or%20%60/system-features%60%20endpoints.%0A%0A6.%20%2A%2ARecent%20code%20changes%3A%2A%2A%20There%20was%20a%20recent%20fix%20related%20to%20the%20install/setup%20flow%20and%20password%20handling%20%5B%28reference%29%5D%28https%3A//github.com/langgenius/dify/pull/30523%29.%20Make%20sure%20your%20containers%20are%20using%20the%20latest%20images%20for%20version%201.11.2.%0A%0AIf%20you%20still%20see%20only%20the%20minimal%20UI%2C%20please%20share%20any%20errors%20from%20your%20browser%20console%20and%20the%20logs%20from%20your%20backend%20container.%20This%20will%20help%20pinpoint%20whether%20it%E2%80%99s%20a%20networking%2C%20configuration%2C%20or%20backend%20issue.)&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/30819)
yindo commented 2026-02-21 20:13:14 -05:00
Author
Owner
Copy Link
Copy Source

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

below is environment variables for .env file and dify-api container log,error still happen
FILES_URL=http://api:5001

INTERNAL_FILES_URL is used for plugin daemon communication within Docker network.

Set this to the internal Docker service URL for proper plugin file access.

Example: INTERNAL_FILES_URL=http://api:5001

INTERNAL_FILES_URL=http://api:5001

(base) magicyang@GEM12:~/project/dify$ docker logs -f dify-api-1
Running migrations
2026-01-11 04:09:43.243 INFO [MainThread] [utils.py:164] - NumExpr defaulting to 16 threads.
2026-01-11 04:09:46.984 INFO [MainThread] [ext_logstore.py:39] - Logstore extension disabled: required Aliyun SLS environment variables not set
Preparing database migration...
Database migration skipped
[2026-01-11 04:09:49 +0000] [1] [INFO] Starting gunicorn 23.0.0
[2026-01-11 04:09:49 +0000] [1] [INFO] Listening at: http://0.0.0.0:5001 (1)
[2026-01-11 04:09:49 +0000] [1] [INFO] Using worker: gevent
[2026-01-11 04:09:49 +0000] [60] [INFO] Booting worker with pid: 60
gRPC patched with gevent.
psycopg2 patched with gevent.
2026-01-11 04:09:51.175 INFO [MainThread] [utils.py:164] - NumExpr defaulting to 16 threads.
2026-01-11 04:09:52.159 INFO [MainThread] [ext_logstore.py:39] - Logstore extension disabled: required Aliyun SLS environment variables not set

Image
@pzc163 commented on GitHub (Jan 10, 2026): below is environment variables for .env file and dify-api container log,error still happen FILES_URL=http://api:5001 # INTERNAL_FILES_URL is used for plugin daemon communication within Docker network. # Set this to the internal Docker service URL for proper plugin file access. # Example: INTERNAL_FILES_URL=http://api:5001 INTERNAL_FILES_URL=http://api:5001 (base) magicyang@GEM12:~/project/dify$ docker logs -f dify-api-1 Running migrations 2026-01-11 04:09:43.243 INFO [MainThread] [utils.py:164] - NumExpr defaulting to 16 threads. 2026-01-11 04:09:46.984 INFO [MainThread] [ext_logstore.py:39] - Logstore extension disabled: required Aliyun SLS environment variables not set Preparing database migration... Database migration skipped [2026-01-11 04:09:49 +0000] [1] [INFO] Starting gunicorn 23.0.0 [2026-01-11 04:09:49 +0000] [1] [INFO] Listening at: http://0.0.0.0:5001 (1) [2026-01-11 04:09:49 +0000] [1] [INFO] Using worker: gevent [2026-01-11 04:09:49 +0000] [60] [INFO] Booting worker with pid: 60 gRPC patched with gevent. psycopg2 patched with gevent. 2026-01-11 04:09:51.175 INFO [MainThread] [utils.py:164] - NumExpr defaulting to 16 threads. 2026-01-11 04:09:52.159 INFO [MainThread] [ext_logstore.py:39] - Logstore extension disabled: required Aliyun SLS environment variables not set <img width="2374" height="650" alt="Image" src="https://github.com/user-attachments/assets/34668267-efe0-4bf7-8404-a04bdac651be" />
yindo commented 2026-02-21 20:13:14 -05:00
Author
Owner
Copy Link
Copy Source

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

is there any problem with container dify-init_permissions-1?
Image

@pzc163 commented on GitHub (Jan 10, 2026): is there any problem with container dify-init_permissions-1? <img width="3456" height="766" alt="Image" src="https://github.com/user-attachments/assets/443b2085-7154-4a97-b7e9-ea3ab1874a1b" />
yindo commented 2026-02-21 20:13:14 -05:00
Author
Owner
Copy Link
Copy Source

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

Yes, there are likely configuration problems causing your install page to not load. Based on your environment variables and container status, here’s what stands out:

  • FILES_URL and INTERNAL_FILES_URL are both set to http://api:5001. This is only correct for internal Docker communication. For browser access, FILES_URL must be set to the external address you use in your browser, for example: FILES_URL=http://192.168.90.109:8010. INTERNAL_FILES_URL should remain http://api:5001 for internal plugins. If both are set to the internal address, the frontend and external tools cannot access files or APIs properly (source, source).

  • The frontend relies on environment variables like CONSOLE_API_URL and APP_API_URL (in your .env) to construct API endpoints. These must be set to the base URL (host and port only, no sub-paths) of your web/proxy service, e.g., http://192.168.90.109:8010. If you include sub-paths like /console/api, the frontend will generate invalid URLs and fail to communicate with the backend, resulting in a blank or minimal install page (source, source).

  • After correcting your .env file, you must restart all Docker containers for changes to take effect.

  • If you are running a proxy (like Clash) on your host, it can block local Docker connections and prevent the install page from loading. Try disabling the proxy or using the direct IP/127.0.0.1 (source).

  • If the install page still fails, check the logs of your web/frontend container for errors, and open your browser’s developer console to look for failed network requests to /setup or /system-features.

  • If you recently upgraded Dify, use the dify-env-sync.sh script to sync your .env file with the latest .env.example to avoid missing required variables (source).

Let me know if you need help with the exact .env values or want to share your frontend logs or browser errors for further 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 (Jan 10, 2026): <!-- Answer --> Yes, there are likely configuration problems causing your install page to not load. Based on your environment variables and container status, here’s what stands out: - FILES_URL and INTERNAL_FILES_URL are both set to http://api:5001. This is only correct for internal Docker communication. For browser access, FILES_URL must be set to the external address you use in your browser, for example: FILES_URL=http://192.168.90.109:8010. INTERNAL_FILES_URL should remain http://api:5001 for internal plugins. If both are set to the internal address, the frontend and external tools cannot access files or APIs properly ([source](https://github.com/langgenius/dify/issues/25490), [source](https://github.com/langgenius/dify/issues/28888)). - The frontend relies on environment variables like CONSOLE_API_URL and APP_API_URL (in your .env) to construct API endpoints. These must be set to the base URL (host and port only, no sub-paths) of your web/proxy service, e.g., http://192.168.90.109:8010. If you include sub-paths like /console/api, the frontend will generate invalid URLs and fail to communicate with the backend, resulting in a blank or minimal install page ([source](https://github.com/langgenius/dify/issues/20365), [source](https://github.com/langgenius/dify/blob/a2e03b811e581674603617a4b13d9d25760c44be/web/docker/entrypoint.sh#L15-L44)). - After correcting your .env file, you must restart all Docker containers for changes to take effect. - If you are running a proxy (like Clash) on your host, it can block local Docker connections and prevent the install page from loading. Try disabling the proxy or using the direct IP/127.0.0.1 ([source](https://github.com/langgenius/dify/issues/16801)). - If the install page still fails, check the logs of your web/frontend container for errors, and open your browser’s developer console to look for failed network requests to /setup or /system-features. - If you recently upgraded Dify, use the dify-env-sync.sh script to sync your .env file with the latest .env.example to avoid missing required variables ([source](https://github.com/langgenius/dify/pull/29845)). Let me know if you need help with the exact .env values or want to share your frontend logs or browser errors for further troubleshooting. <!-- 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/fd6beb50-8f6e-4ed8-b1c6-9ff895ccf19e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/fd6beb50-8f6e-4ed8-b1c6-9ff895ccf19e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/fd6beb50-8f6e-4ed8-b1c6-9ff895ccf19e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/fd6beb50-8f6e-4ed8-b1c6-9ff895ccf19e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/fd6beb50-8f6e-4ed8-b1c6-9ff895ccf19e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/fd6beb50-8f6e-4ed8-b1c6-9ff895ccf19e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/fd6beb50-8f6e-4ed8-b1c6-9ff895ccf19e?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=Yes%2C%20there%20are%20likely%20configuration%20problems%20causing%20your%20install%20page%20to%20not%20load.%20Based%20on%20your%20environment%20variables%20and%20container%20status%2C%20here%E2%80%99s%20what%20stands%20out%3A%0A%0A-%20FILES_URL%20and%20INTERNAL_FILES_URL%20are%20both%20set%20to%20http%3A//api%3A5001.%20This%20is%20only%20correct%20for%20internal%20Docker%20communication.%20For%20browser%20access%2C%20FILES_URL%20must%20be%20set%20to%20the%20external%20address%20you%20use%20in%20your%20browser%2C%20for%20example%3A%20FILES_URL%3Dhttp%3A//192.168.90.109%3A8010.%20INTERNAL_FILES_URL%20should%20remain%20http%3A//api%3A5001%20for%20internal%20plugins.%20If%20both%20are%20set%20to%20the%20internal%20address%2C%20the%20frontend%20and%20external%20tools%20cannot%20access%20files%20or%20APIs%20properly%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/25490%29%2C%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/28888%29%29.%0A%0A-%20The%20frontend%20relies%20on%20environment%20variables%20like%20CONSOLE_API_URL%20and%20APP_API_URL%20%28in%20your%20.env%29%20to%20construct%20API%20endpoints.%20These%20must%20be%20set%20to%20the%20base%20URL%20%28host%20and%20port%20only%2C%20no%20sub-paths%29%20of%20your%20web/proxy%20service%2C%20e.g.%2C%20http%3A//192.168.90.109%3A8010.%20If%20you%20include%20sub-paths%20like%20/console/api%2C%20the%20frontend%20will%20generate%20invalid%20URLs%20and%20fail%20to%20communicate%20with%20the%20backend%2C%20resulting%20in%20a%20blank%20or%20minimal%20install%20page%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/20365%29%2C%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/a2e03b811e581674603617a4b13d9d25760c44be/web/docker/entrypoint.sh%23L15-L44%29%29.%0A%0A-%20After%20correcting%20your%20.env%20file%2C%20you%20must%20restart%20all%20Docker%20containers%20for%20changes%20to%20take%20effect.%0A%0A-%20If%20you%20are%20running%20a%20proxy%20%28like%20Clash%29%20on%20your%20host%2C%20it%20can%20block%20local%20Docker%20connections%20and%20prevent%20the%20install%20page%20from%20loading.%20Try%20disabling%20the%20proxy%20or%20using%20the%20direct%20IP/127.0.0.1%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/16801%29%29.%0A%0A-%20If%20the%20install%20page%20still%20fails%2C%20check%20the%20logs%20of%20your%20web/frontend%20container%20for%20errors%2C%20and%20open%20your%20browser%E2%80%99s%20developer%20console%20to%20look%20for%20failed%20network%20requests%20to%20/setup%20or%20/system-features.%0A%0A-%20If%20you%20recently%20upgraded%20Dify%2C%20use%20the%20dify-env-sync.sh%20script%20to%20sync%20your%20.env%20file%20with%20the%20latest%20.env.example%20to%20avoid%20missing%20required%20variables%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/pull/29845%29%29.%0A%0ALet%20me%20know%20if%20you%20need%20help%20with%20the%20exact%20.env%20values%20or%20want%20to%20share%20your%20frontend%20logs%20or%20browser%20errors%20for%20further%20troubleshooting.)&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/30819)
yindo commented 2026-02-21 20:13:14 -05:00
Author
Owner
Copy Link
Copy Source

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

Thanks for your reply,I have figure it out,it may be some error with nginx

@pzc163 commented on GitHub (Jan 10, 2026): Thanks for your reply,I have figure it out,it may be some error with nginx
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#21565
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?