langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 22:11:36 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

external Ragflow knowledge #7634

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

Originally created by @CellMook on GitHub (Jan 9, 2025).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.15.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Dify connects to the external Ragflow knowledge base. Testing the Ragflow API with Postman works without issues, but after connecting Dify, when performing a recall test, an error occurs on the page. The error message is: 'Application error: a client-side exception has occurred (see the browser console for more information).

PixPin_2025-01-10_10-17-53
PixPin_2025-01-10_10-18-10

✔️ Expected Behavior

Identify the cause and fix the bug.

❌ Actual Behavior

No response

Originally created by @CellMook on GitHub (Jan 9, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.15.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Dify connects to the external Ragflow knowledge base. Testing the Ragflow API with Postman works without issues, but after connecting Dify, when performing a recall test, an error occurs on the page. The error message is: 'Application error: a client-side exception has occurred (see the browser console for more information). ![PixPin_2025-01-10_10-17-53](https://github.com/user-attachments/assets/576f9ce7-176e-4bc7-9698-0e8a9694fb6e) ![PixPin_2025-01-10_10-18-10](https://github.com/user-attachments/assets/79f20fe5-0021-4d78-88f0-6755c8497628) ### ✔️ Expected Behavior Identify the cause and fix the bug. ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:21:35 -05:00
yindo commented 2026-02-21 18:21:35 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 9, 2025):

Hey @CellMook! 👋 I'm here to help you with bugs, answer questions, and even guide you on becoming a contributor. Let's squash those bugs together!

I found a similar closed issue that might be relevant to your problem: Application error: a client-side exception has occurred (see the browser console for more information). This issue was resolved by a pull request that addressed the client-side exception [1].

For troubleshooting client-side exceptions in Dify, you can follow these steps:

  1. Verify the Content Security Policy (CSP) configuration by checking the CSP_WHITELIST environment variable in your .env file.
  2. Ensure all necessary domains are included in the CSP whitelist.
  3. Check that any optional input fields in the workflow are properly initialized.
  4. Verify that objects related to _dfy_model_identity are not null before property access.
  5. Consider upgrading to Dify version 0.14.0 or later if you encounter issues when accessing a workflow after publishing it as a tool.
  6. If upgrading is not an option, try recreating the workflow, as this has been reported to sometimes resolve the issue [2].

These steps might help you identify and resolve the client-side exception you're experiencing.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Jan 9, 2025): <!-- Greeting --> Hey @CellMook! 👋 I'm here to help you with bugs, answer questions, and even guide you on becoming a contributor. Let's squash those bugs together! <!-- Answer --> I found a similar closed issue that might be relevant to your problem: [Application error: a client-side exception has occurred (see the browser console for more information)](https://github.com/langgenius/dify/issues/10199). This issue was resolved by a pull request that addressed the client-side exception <sup>[[1]](https://github.com/langgenius/dify/issues/10199)</sup>. For troubleshooting client-side exceptions in Dify, you can follow these steps: 1. Verify the Content Security Policy (CSP) configuration by checking the `CSP_WHITELIST` environment variable in your `.env` file. 2. Ensure all necessary domains are included in the CSP whitelist. 3. Check that any optional input fields in the workflow are properly initialized. 4. Verify that objects related to `_dfy_model_identity` are not null before property access. 5. Consider upgrading to Dify version 0.14.0 or later if you encounter issues when accessing a workflow after publishing it as a tool. 6. If upgrading is not an option, try recreating the workflow, as this has been reported to sometimes resolve the issue <sup>[[2]](https://github.com/langgenius/dify/issues/11563)</sup>. These steps might help you identify and resolve the client-side exception you're experiencing. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/08dd45a8-bcaa-4012-b7e0-032e881db4ba?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/08dd45a8-bcaa-4012-b7e0-032e881db4ba?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/08dd45a8-bcaa-4012-b7e0-032e881db4ba?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/08dd45a8-bcaa-4012-b7e0-032e881db4ba?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/08dd45a8-bcaa-4012-b7e0-032e881db4ba?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/08dd45a8-bcaa-4012-b7e0-032e881db4ba?feedback_type=other)</sup>
yindo commented 2026-02-21 18:21:35 -05:00
Author
Owner
Copy Link
Copy Source

@CellMook commented on GitHub (Jan 10, 2025):

error:
2117-facb83e7cbe5e185.js:1 TypeError: Cannot read properties of undefined (reading 'name')
at page-dfd31e1e568d1ab4.js:1:22674
at rE (fd9d1056-014bed05f3bb9932.js:1:40344)
at l$ (fd9d1056-014bed05f3bb9932.js:1:59319)
at lU (fd9d1056-014bed05f3bb9932.js:1:58164)
at lI (fd9d1056-014bed05f3bb9932.js:1:57769)
at iZ (fd9d1056-014bed05f3bb9932.js:1:121847)
at ia (fd9d1056-014bed05f3bb9932.js:1:95165)
at fd9d1056-014bed05f3bb9932.js:1:94987
at il (fd9d1056-014bed05f3bb9932.js:1:94994)
at oJ (fd9d1056-014bed05f3bb9932.js:1:92350)

@CellMook commented on GitHub (Jan 10, 2025): error: 2117-facb83e7cbe5e185.js:1 TypeError: Cannot read properties of undefined (reading 'name') at page-dfd31e1e568d1ab4.js:1:22674 at rE (fd9d1056-014bed05f3bb9932.js:1:40344) at l$ (fd9d1056-014bed05f3bb9932.js:1:59319) at lU (fd9d1056-014bed05f3bb9932.js:1:58164) at lI (fd9d1056-014bed05f3bb9932.js:1:57769) at iZ (fd9d1056-014bed05f3bb9932.js:1:121847) at ia (fd9d1056-014bed05f3bb9932.js:1:95165) at fd9d1056-014bed05f3bb9932.js:1:94987 at il (fd9d1056-014bed05f3bb9932.js:1:94994) at oJ (fd9d1056-014bed05f3bb9932.js:1:92350)
yindo commented 2026-02-21 18:21:35 -05:00
Author
Owner
Copy Link
Copy Source

@yangluoshen commented on GitHub (Jan 12, 2025):

Encounter the same problem.

@yangluoshen commented on GitHub (Jan 12, 2025): Encounter the same problem.
yindo commented 2026-02-21 18:21:35 -05:00
Author
Owner
Copy Link
Copy Source

@yuanbaobaoo commented on GitHub (Jan 22, 2025):

Have you found a solution ？

@yuanbaobaoo commented on GitHub (Jan 22, 2025): Have you found a solution ？
yindo commented 2026-02-21 18:21:35 -05:00
Author
Owner
Copy Link
Copy Source

@openproix commented on GitHub (Apr 25, 2025):

I'm having the same problem, why is this question closed?

@openproix commented on GitHub (Apr 25, 2025): I'm having the same problem, why is this question closed?
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
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#7634
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?