a client-side exception has occurred (see the browser console for more information),,,,,

[zhangxiaolin718]

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).
• 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.11

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When I send a message, the model replies and this interface appears

✔️ Expected Behavior

Continue the conversation

❌ Actual Behavior

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

[dosubot]

@zhangxiaolin718 Hello there! I'm Dosu, a bot here to help you with bugs, questions, and contributions. Feel free to reach out to me while you wait for a human maintainer. 🤖

To resolve the "Minified React error #31" in your self-hosted Dify version 0.6.11 (Docker), follow these steps:

1. Check Browser Console: Examine the browser console for specific error messages. These messages can provide clues about what's causing the script to fail.

2. Verify Dify Configuration: Ensure your Dify configuration is correct, particularly that the difyChatbotConfig object is properly set up and that the chatbotUrl is correctly defined.

3. Docker Setup: Verify your Docker setup to ensure it's not restricting network access or interaction with Chrome's storage API, which could affect script execution. Also, review any CORS policies and Content Security Policies (CSP) that might be blocking requests to the chatbot URL from your domain.

4. Update Dify: Consider updating Dify to the latest version to benefit from any bug fixes or improvements.

5. Locale Settings: Check and configure the locale settings in your Docker environment. This can typically be done by setting the appropriate environment variables in your Docker Compose configuration. Here is how you can set the locale environment variables:

   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
   LC_ALL=en_US.UTF-8

   Restart your Docker containers to apply the changes:

   docker compose down
   docker compose up -d

6. Connection Address: Ensure that the connection address is set to http://host.docker.internal:19530/ instead of using 127.0.0.1:19530, and that Docker's WSL 2 based engine is configured to add *.docker.internal names to the host's etc/hosts file.

If the issue persists, the specific error messages from the browser console will be crucial for further diagnosis ^[1][2][3].

To continue talking to Dosu, mention @dosu.

[crazywoola]

Please upgrade to latest version, we have fixed this error in later versions.

[darkmirrors]

@crazywoola the problem still happen in 0.6.16，when i use suggested-questions， the client will creshed