web url error?
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
0.15.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Expected Behavior
如果用chatbot的连接访问应用,开始聊天后刷新100%出现如图错误,chat连接没有这个错误?
If you use the chatbot connection to access the application and refresh 100% after starting the chat, there will be an error as shown in the figure, but the chat connection does not have this error?
❌ Actual Behavior
Hope to fix it
I found a similar unsolved discussion regarding issues with the embedded chatbot after upgrading to version 0.15.3. You can view it here [1].
Regarding the issue you're experiencing, in version 0.15.3 of Dify, there was a change that affected the embedded chatbot functionality. The getPrevChatList function was removed during code refactoring, which led to a TypeError when the function was still being called in some parts of the code. This error typically occurs when refreshing the chatbot page after starting a chat, as you've described. The error message '(0 , g.getPrevChatList) is not a function' would appear, causing the page to fail to load properly.
To resolve this issue, it is recommended to update your web container to use the fixed Docker tag 'release-0.15.3-fix1'. You can do this by modifying your docker-compose.yaml file to use the following image: langgenius/dify-web:release-0.15.3-fix1. This hotfix specifically addresses the TypeError issue [2][3][4].
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
The 2 endpoint are different.
The bug has been resolved. See bot's reply.