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

Applicationerror #20519

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

Originally created by @wzn1KhUGCtAj on GitHub (Nov 24, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.10

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Expected Behavior

Image

❌ Actual Behavior

No response

Originally created by @wzn1KhUGCtAj on GitHub (Nov 24, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.10 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1880" height="1248" alt="Image" src="https://github.com/user-attachments/assets/8568eac8-0621-4bcb-90d2-fcc80b8cab43" /> ### ✔️ Expected Behavior <img width="1880" height="1248" alt="Image" src="https://github.com/user-attachments/assets/43fec719-36e5-4914-927b-1715b92db73f" /> ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 20:07:48 -05:00
yindo closed this issue 2026-02-21 20:07:48 -05:00
yindo commented 2026-02-21 20:07:48 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 24, 2025):

The "Application error: a client-side exception has occurred" message in Dify (self-hosted via Docker) is usually triggered by a frontend JavaScript error, often due to misconfiguration or a failed API/network request. The most common causes are:

  • Misconfigured Docker port mappings, especially if the API service port (like 5001) isn't exposed in your docker-compose.yaml. Adding ports: - "5001:5001" to the relevant service can resolve backend connection issues that cause frontend errors (example).
  • Incorrect or missing environment variables, particularly NEXT_PUBLIC_* variables (such as NEXT_PUBLIC_API_PREFIX, NEXT_PUBLIC_COOKIE_DOMAIN, etc.), which the frontend uses to connect to the backend. Double-check your .env and Docker environment files for typos or missing values (reference).
  • Plugin or YAML schema errors, especially if you have custom plugins or agent strategies. Invalid or misformatted YAML (like using type: selector instead of type: select) can crash the UI (details).
  • Resource loading issues, such as the code editor trying to load files from an incorrect path. This was recently fixed by ensuring resources load from local paths (see PR #28500).

To troubleshoot:

  1. Open your browser's developer console and check for any error messages or stack traces—these will pinpoint the exact cause.
  2. Check the Docker logs for your frontend and backend containers for errors at startup or during requests.
  3. Verify your docker-compose.yaml exposes all necessary ports and that your .env files are correct.
  4. If you use custom plugins or YAML configs, validate their structure against official examples.

If the issue persists, please share the browser console error details and any relevant Docker logs. This will help narrow down the root cause. If you're running an older release, consider updating to the latest version, as several frontend error-handling bugs have been fixed recently.

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 (Nov 24, 2025): <!-- Answer --> The "Application error: a client-side exception has occurred" message in Dify (self-hosted via Docker) is usually triggered by a frontend JavaScript error, often due to misconfiguration or a failed API/network request. The most common causes are: - Misconfigured Docker port mappings, especially if the API service port (like 5001) isn't exposed in your `docker-compose.yaml`. Adding `ports: - "5001:5001"` to the relevant service can resolve backend connection issues that cause frontend errors [(example)](https://github.com/langgenius/dify-official-plugins/issues/1816). - Incorrect or missing environment variables, particularly `NEXT_PUBLIC_*` variables (such as `NEXT_PUBLIC_API_PREFIX`, `NEXT_PUBLIC_COOKIE_DOMAIN`, etc.), which the frontend uses to connect to the backend. Double-check your `.env` and Docker environment files for typos or missing values [(reference)](https://github.com/langgenius/dify/blob/15ea27868e0512b7dbca633d93b1808fbdb7d575/web/app/layout.tsx#L38-L106). - Plugin or YAML schema errors, especially if you have custom plugins or agent strategies. Invalid or misformatted YAML (like using `type: selector` instead of `type: select`) can crash the UI [(details)](https://github.com/langgenius/dify-official-plugins/issues/1953). - Resource loading issues, such as the code editor trying to load files from an incorrect path. This was recently fixed by ensuring resources load from local paths [(see PR #28500)](https://github.com/langgenius/dify/pull/28500). To troubleshoot: 1. Open your browser's developer console and check for any error messages or stack traces—these will pinpoint the exact cause. 2. Check the Docker logs for your frontend and backend containers for errors at startup or during requests. 3. Verify your `docker-compose.yaml` exposes all necessary ports and that your `.env` files are correct. 4. If you use custom plugins or YAML configs, validate their structure against official examples. If the issue persists, please share the browser console error details and any relevant Docker logs. This will help narrow down the root cause. If you're running an older release, consider updating to the latest version, as several frontend error-handling bugs have been fixed recently. <!-- 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/9992e132-ad54-4efa-82e0-1f9154111c53?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9992e132-ad54-4efa-82e0-1f9154111c53?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9992e132-ad54-4efa-82e0-1f9154111c53?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9992e132-ad54-4efa-82e0-1f9154111c53?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9992e132-ad54-4efa-82e0-1f9154111c53?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9992e132-ad54-4efa-82e0-1f9154111c53?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9992e132-ad54-4efa-82e0-1f9154111c53?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%20%22Application%20error%3A%20a%20client-side%20exception%20has%20occurred%22%20message%20in%20Dify%20%28self-hosted%20via%20Docker%29%20is%20usually%20triggered%20by%20a%20frontend%20JavaScript%20error%2C%20often%20due%20to%20misconfiguration%20or%20a%20failed%20API/network%20request.%20The%20most%20common%20causes%20are%3A%0A%0A-%20Misconfigured%20Docker%20port%20mappings%2C%20especially%20if%20the%20API%20service%20port%20%28like%205001%29%20isn%27t%20exposed%20in%20your%20%60docker-compose.yaml%60.%20Adding%20%60ports%3A%20-%20%225001%3A5001%22%60%20to%20the%20relevant%20service%20can%20resolve%20backend%20connection%20issues%20that%20cause%20frontend%20errors%20%5B%28example%29%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1816%29.%0A-%20Incorrect%20or%20missing%20environment%20variables%2C%20particularly%20%60NEXT_PUBLIC_%2A%60%20variables%20%28such%20as%20%60NEXT_PUBLIC_API_PREFIX%60%2C%20%60NEXT_PUBLIC_COOKIE_DOMAIN%60%2C%20etc.%29%2C%20which%20the%20frontend%20uses%20to%20connect%20to%20the%20backend.%20Double-check%20your%20%60.env%60%20and%20Docker%20environment%20files%20for%20typos%20or%20missing%20values%20%5B%28reference%29%5D%28https%3A//github.com/langgenius/dify/blob/15ea27868e0512b7dbca633d93b1808fbdb7d575/web/app/layout.tsx%23L38-L106%29.%0A-%20Plugin%20or%20YAML%20schema%20errors%2C%20especially%20if%20you%20have%20custom%20plugins%20or%20agent%20strategies.%20Invalid%20or%20misformatted%20YAML%20%28like%20using%20%60type%3A%20selector%60%20instead%20of%20%60type%3A%20select%60%29%20can%20crash%20the%20UI%20%5B%28details%29%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1953%29.%0A-%20Resource%20loading%20issues%2C%20such%20as%20the%20code%20editor%20trying%20to%20load%20files%20from%20an%20incorrect%20path.%20This%20was%20recently%20fixed%20by%20ensuring%20resources%20load%20from%20local%20paths%20%5B%28see%20PR%20%2328500%29%5D%28https%3A//github.com/langgenius/dify/pull/28500%29.%0A%0ATo%20troubleshoot%3A%0A1.%20Open%20your%20browser%27s%20developer%20console%20and%20check%20for%20any%20error%20messages%20or%20stack%20traces%E2%80%94these%20will%20pinpoint%20the%20exact%20cause.%0A2.%20Check%20the%20Docker%20logs%20for%20your%20frontend%20and%20backend%20containers%20for%20errors%20at%20startup%20or%20during%20requests.%0A3.%20Verify%20your%20%60docker-compose.yaml%60%20exposes%20all%20necessary%20ports%20and%20that%20your%20%60.env%60%20files%20are%20correct.%0A4.%20If%20you%20use%20custom%20plugins%20or%20YAML%20configs%2C%20validate%20their%20structure%20against%20official%20examples.%0A%0AIf%20the%20issue%20persists%2C%20please%20share%20the%20browser%20console%20error%20details%20and%20any%20relevant%20Docker%20logs.%20This%20will%20help%20narrow%20down%20the%20root%20cause.%20If%20you%27re%20running%20an%20older%20release%2C%20consider%20updating%20to%20the%20latest%20version%2C%20as%20several%20frontend%20error-handling%20bugs%20have%20been%20fixed%20recently.)&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/28599)
yindo commented 2026-02-21 20:07:48 -05:00
Author
Owner
Copy Link
Copy Source

@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025):

I directly used the pulled configuration and ran it with docker compose up -d. I pulled all the images again and reconfigured everything, but this issue still occurs after setting it up.

@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025): I directly used the pulled configuration and ran it with docker compose up -d. I pulled all the images again and reconfigured everything, but this issue still occurs after setting it up.
yindo commented 2026-02-21 20:07:48 -05:00
Author
Owner
Copy Link
Copy Source

@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025):

Image The error occurred when I clicked on the log annotation to view the detailed LLM output.
@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025): <img width="2519" height="319" alt="Image" src="https://github.com/user-attachments/assets/18df1022-a89a-4978-ae76-2337155d65ce" /> The error occurred when I clicked on the log annotation to view the detailed LLM output.
yindo commented 2026-02-21 20:07:49 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 24, 2025):

This kind of client-side exception when viewing detailed LLM output is often caused by a JavaScript error triggered by malformed or missing data from the backend, or by unguarded property access in the frontend code. Similar issues have been reported when special characters or unexpected data structures appear in logs or annotations, causing the UI to crash with an "application error" page (example).

Recent frontend changes have adjusted how log annotations and details are rendered, but in version 1.10, the frontend may still be vulnerable to these issues if the backend returns data that doesn't match what the UI expects (code reference).

To pinpoint the cause, please open your browser's developer console and check for any error messages or stack traces when the exception occurs. The most common errors are "Cannot read properties of undefined" or similar TypeErrors. Also, check your Docker logs for both frontend and backend containers for any errors at the time of the crash.

Make sure your frontend and backend images are both version 1.10 and not mismatched, as version mismatches are a common source of frontend exceptions (see similar issue). Try clearing your browser cache or using a different browser to rule out caching issues.

If you find any specific error messages in the browser console or logs, please share them—they will help narrow down the root cause and suggest a targeted fix. If you are able to upgrade, newer versions of Dify have added more frontend guards and bug fixes for these types of errors.

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 (Nov 24, 2025): <!-- Answer --> This kind of client-side exception when viewing detailed LLM output is often caused by a JavaScript error triggered by malformed or missing data from the backend, or by unguarded property access in the frontend code. Similar issues have been reported when special characters or unexpected data structures appear in logs or annotations, causing the UI to crash with an "application error" page [(example)](https://github.com/langgenius/dify/issues/21219). Recent frontend changes have adjusted how log annotations and details are rendered, but in version 1.10, the frontend may still be vulnerable to these issues if the backend returns data that doesn't match what the UI expects [(code reference)](https://github.com/langgenius/dify/blob/15ea27868e0512b7dbca633d93b1808fbdb7d575/web/app/components/app/log/list.tsx#L196-L1114). To pinpoint the cause, please open your browser's developer console and check for any error messages or stack traces when the exception occurs. The most common errors are "Cannot read properties of undefined" or similar TypeErrors. Also, check your Docker logs for both frontend and backend containers for any errors at the time of the crash. Make sure your frontend and backend images are both version 1.10 and not mismatched, as version mismatches are a common source of frontend exceptions [(see similar issue)](https://github.com/langgenius/dify/issues/12532). Try clearing your browser cache or using a different browser to rule out caching issues. If you find any specific error messages in the browser console or logs, please share them—they will help narrow down the root cause and suggest a targeted fix. If you are able to upgrade, newer versions of Dify have added more frontend guards and bug fixes for these types of errors. <!-- 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/93bc15cc-5293-41dc-b22c-879e8855db5c?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/93bc15cc-5293-41dc-b22c-879e8855db5c?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/93bc15cc-5293-41dc-b22c-879e8855db5c?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/93bc15cc-5293-41dc-b22c-879e8855db5c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/93bc15cc-5293-41dc-b22c-879e8855db5c?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/93bc15cc-5293-41dc-b22c-879e8855db5c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/93bc15cc-5293-41dc-b22c-879e8855db5c?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=This%20kind%20of%20client-side%20exception%20when%20viewing%20detailed%20LLM%20output%20is%20often%20caused%20by%20a%20JavaScript%20error%20triggered%20by%20malformed%20or%20missing%20data%20from%20the%20backend%2C%20or%20by%20unguarded%20property%20access%20in%20the%20frontend%20code.%20Similar%20issues%20have%20been%20reported%20when%20special%20characters%20or%20unexpected%20data%20structures%20appear%20in%20logs%20or%20annotations%2C%20causing%20the%20UI%20to%20crash%20with%20an%20%22application%20error%22%20page%20%5B%28example%29%5D%28https%3A//github.com/langgenius/dify/issues/21219%29.%0A%0ARecent%20frontend%20changes%20have%20adjusted%20how%20log%20annotations%20and%20details%20are%20rendered%2C%20but%20in%20version%201.10%2C%20the%20frontend%20may%20still%20be%20vulnerable%20to%20these%20issues%20if%20the%20backend%20returns%20data%20that%20doesn%27t%20match%20what%20the%20UI%20expects%20%5B%28code%20reference%29%5D%28https%3A//github.com/langgenius/dify/blob/15ea27868e0512b7dbca633d93b1808fbdb7d575/web/app/components/app/log/list.tsx%23L196-L1114%29.%0A%0ATo%20pinpoint%20the%20cause%2C%20please%20open%20your%20browser%27s%20developer%20console%20and%20check%20for%20any%20error%20messages%20or%20stack%20traces%20when%20the%20exception%20occurs.%20The%20most%20common%20errors%20are%20%22Cannot%20read%20properties%20of%20undefined%22%20or%20similar%20TypeErrors.%20Also%2C%20check%20your%20Docker%20logs%20for%20both%20frontend%20and%20backend%20containers%20for%20any%20errors%20at%20the%20time%20of%20the%20crash.%0A%0AMake%20sure%20your%20frontend%20and%20backend%20images%20are%20both%20version%201.10%20and%20not%20mismatched%2C%20as%20version%20mismatches%20are%20a%20common%20source%20of%20frontend%20exceptions%20%5B%28see%20similar%20issue%29%5D%28https%3A//github.com/langgenius/dify/issues/12532%29.%20Try%20clearing%20your%20browser%20cache%20or%20using%20a%20different%20browser%20to%20rule%20out%20caching%20issues.%0A%0AIf%20you%20find%20any%20specific%20error%20messages%20in%20the%20browser%20console%20or%20logs%2C%20please%20share%20them%E2%80%94they%20will%20help%20narrow%20down%20the%20root%20cause%20and%20suggest%20a%20targeted%20fix.%20If%20you%20are%20able%20to%20upgrade%2C%20newer%20versions%20of%20Dify%20have%20added%20more%20frontend%20guards%20and%20bug%20fixes%20for%20these%20types%20of%20errors.)&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/28599)
yindo commented 2026-02-21 20:07:49 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 24, 2025):

Please provide the logs instead.

@crazywoola commented on GitHub (Nov 24, 2025): Please provide the logs instead.
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#20519
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?