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

Application error: a client-side exception has occurred (see the browser console for more information). #1098

New Issue
Closed
opened 2026-02-21 17:29:58 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 17:29:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @yanzu888 on GitHub (Feb 23, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • Pleas do not modify this template :) and fill in all the required fields.

Dify version

0.5.6

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Access your own application by sharing the address and start a new conversation. Opening a new window to access will have a very high probability of popping up this error message. It seems that this malfunction is easy to occur in chat applications with historical conversations. Amazingly, if you keep refreshing the page after opening F12, this error will not occur.

image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @yanzu888 on GitHub (Feb 23, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Pleas do not modify this template :) and fill in all the required fields. ### Dify version 0.5.6 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Access your own application by sharing the address and start a new conversation. Opening a new window to access will have a very high probability of popping up this error message. It seems that this malfunction is easy to occur in chat applications with historical conversations. Amazingly, if you keep refreshing the page after opening F12, this error will not occur. ![image](https://github.com/langgenius/dify/assets/20461842/65936980-dbd4-4bb5-b4ae-bd49239937bc) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 17:29:58 -05:00
yindo closed this issue 2026-02-21 17:29:58 -05:00
yindo commented 2026-02-21 17:29:58 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 23, 2024):

🤖

Hey @yanzu888, nice to see you back here! Hope you're doing well.

Based on the information you've provided, it seems like you're encountering a client-side exception when trying to start a new conversation in your self-hosted Dify version 0.5.6 application, especially in chat applications with historical conversations. Unfortunately, without specific error messages or details about the client-side exception, it's challenging to provide a specific solution.

However, I can suggest some general steps to debug and potentially resolve the issue:

  1. Check the browser console for error messages: When the exception occurs, the browser console might display error messages that could provide clues about what's causing the issue.

  2. Review the code related to starting a new conversation: In the provided context, this seems to be handled by the handleStartChat function. Ensure that all necessary data is available and correctly handled when this function is called.

  3. Ensure the state of the application is correctly updated: When starting a new conversation, several state variables are updated in the handleStartChat function, such as setCurrInputs, setChatStarted, and setChatList.

  4. Review the code related to fetching and handling historical conversations: If the issue only occurs in chat applications with historical conversations, it might be related to how these conversations are loaded or handled.

You can refer to the source code here: web/app/components/share/chatbot/index.tsx

Also, I found some similar issues that were resolved in the past:

  1. Refresh error after updating dify 0.5.6
  2. Shared web app can not be opened again in the same browser
  3. Application error: a client-side exception has occurred (see the browser console for more information)

These issues were resolved by a pull request: fix: config not exists

If the issue persists, could you please provide more details about the exception and the specific circumstances in which it occurs? This could help in identifying a more specific solution.

Sources

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot[bot] commented on GitHub (Feb 23, 2024): _🤖_ <!-- Greeting --> Hey @yanzu888, nice to see you back here! Hope you're doing well. <!-- Answer --> Based on the information you've provided, it seems like you're encountering a client-side exception when trying to start a new conversation in your self-hosted Dify version 0.5.6 application, especially in chat applications with historical conversations. Unfortunately, without specific error messages or details about the client-side exception, it's challenging to provide a specific solution. However, I can suggest some general steps to debug and potentially resolve the issue: 1. **Check the browser console for error messages**: When the exception occurs, the browser console might display error messages that could provide clues about what's causing the issue. 2. **Review the code related to starting a new conversation**: In the provided context, this seems to be handled by the `handleStartChat` function. Ensure that all necessary data is available and correctly handled when this function is called. 3. **Ensure the state of the application is correctly updated**: When starting a new conversation, several state variables are updated in the `handleStartChat` function, such as `setCurrInputs`, `setChatStarted`, and `setChatList`. 4. **Review the code related to fetching and handling historical conversations**: If the issue only occurs in chat applications with historical conversations, it might be related to how these conversations are loaded or handled. You can refer to the source code here: [web/app/components/share/chatbot/index.tsx](https://github.com/langgenius/dify/blob/main/web/app/components/share/chatbot/index.tsx) Also, I found some similar issues that were resolved in the past: 1. [Refresh error after updating dify 0.5.6](https://github.com/langgenius/dify/issues/2502) 2. [Shared web app can not be opened again in the same browser](https://github.com/langgenius/dify/issues/2510) 3. [Application error: a client-side exception has occurred (see the browser console for more information)](https://github.com/langgenius/dify/issues/1783) These issues were resolved by a pull request: [fix: config not exists](https://github.com/langgenius/dify/pull/2513) If the issue persists, could you please provide more details about the exception and the specific circumstances in which it occurs? This could help in identifying a more specific solution. ## Sources - [Refresh error after updating dify 0.5.6](https://github.com/langgenius/dify/issues/2502) - [Shared web app can not be opened again in the same browser](https://github.com/langgenius/dify/issues/2510) - [Application error: a client-side exception has occurred (see the browser console for more information)](https://github.com/langgenius/dify/issues/1783) - [web/app/components/share/chatbot/index.tsx](https://github.com/langgenius/dify/blob/main/web/app/components/share/chatbot/index.tsx) - [web/app/components/app/configuration/debug/index.tsx](https://github.com/langgenius/dify/blob/main/web/app/components/app/configuration/debug/index.tsx) <!-- Dosu Comment Footer --> <details open> <summary> #### About Dosu </summary> This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. </details>
yindo commented 2026-02-21 17:29:58 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 23, 2024):

Fixed in this pr https://github.com/langgenius/dify/pull/2513, we haven't release the new version. It should be fixed in v0.5.7.

@crazywoola commented on GitHub (Feb 23, 2024): Fixed in this pr https://github.com/langgenius/dify/pull/2513, we haven't release the new version. It should be fixed in v0.5.7.
yindo commented 2026-02-21 17:29:58 -05:00
Author
Owner
Copy Link
Copy Source

@Upcreat commented on GitHub (May 11, 2024):

Fixed in this pr #2513, we haven't release the new version. It should be fixed in v0.5.7.

The same problem occurred with version 0.6.7

@Upcreat commented on GitHub (May 11, 2024): > Fixed in this pr #2513, we haven't release the new version. It should be fixed in v0.5.7. The same problem occurred with version 0.6.7
yindo commented 2026-02-21 17:29:58 -05:00
Author
Owner
Copy Link
Copy Source

@AlexSu1108 commented on GitHub (Jul 4, 2024):

The same problem occurred with version 0.6.12-fix1(current version) and 0.6.9

@AlexSu1108 commented on GitHub (Jul 4, 2024): The same problem occurred with version 0.6.12-fix1(current version) and 0.6.9
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#1098
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?