dify icon indicating copy to clipboard operation
dify copied to clipboard

The page crashed after the model was selected

Open zyoung1212 opened this issue 10 months ago • 2 comments

Self Checks

  • [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
  • [x] I have searched for existing issues search for existing issues, including closed ones.
  • [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • [x] Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Install Volcengine model provider
  2. Choose some model
  3. Page crashed.

Image Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

zyoung1212 avatar Mar 23 '25 06:03 zyoung1212

@zyoung1212 Hello there! I'm here to assist you with any bugs, questions, or contributions while waiting for a human maintainer. Let's tackle this issue together!

I found a similar thread discussing client-side exceptions in Dify's React-based frontend, which might be relevant to your issue. The thread titled Application error: a client-side exception has occurred (see the browser console for more information) is still open and was last updated on February 27, 2025 [1].

Common causes of client-side exceptions in Dify's frontend include issues related to React error #31, which can occur when creating a knowledge base and uploading a text file. This error can be resolved by reinstalling the Docker service and redeploying Dify [2]. Although your error is #185, similar troubleshooting steps might help.

Additionally, there is a known issue with the Volcengine model provider integration in Dify version 1.1.2, where a StringDataRightTruncation error occurs due to the provider_name exceeding the character limit. This issue has been fixed in a subsequent update, and updating Dify to a version that includes PR #14597 might resolve related errors [3].

Consider checking the browser console for more detailed error information and ensure that your Docker setup is correctly configured.

To continue talking to Dosu, mention @dosu.


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

dosubot[bot] avatar Mar 23 '25 06:03 dosubot[bot]

Can you provide more logs of the frontend?

crazywoola avatar Mar 24 '25 01:03 crazywoola