Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal Server Error When Clicking 'Like' in Chat Conversations #12057

Closed
5 tasks done
kevintsai1202 opened this issue Dec 25, 2024 · 3 comments · Fixed by #12058
Closed
5 tasks done

Internal Server Error When Clicking 'Like' in Chat Conversations #12057

kevintsai1202 opened this issue Dec 25, 2024 · 3 comments · Fixed by #12058
Labels
🐞 bug Something isn't working good first issue Good first issue for newcomers

Comments

@kevintsai1202
Copy link

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.14.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

圖片
When I click "like" during a chat conversation, an "Internal Server Error" appears at the top of the screen.
However, clicking "like" in the conversation under the logs (admin feedback) works normally.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added the 🐞 bug Something isn't working label Dec 25, 2024
Copy link

dosubot bot commented Dec 25, 2024

The "Internal Server Error" when clicking "like" in chat conversations could be related to the server-side endpoint or API handling the feedback action. The POST /messages/:message_id/feedbacks endpoint is responsible for processing feedback like "likes" or "dislikes" in chat conversations [1].

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

  1. Check Server Logs: Review the server logs for any error messages or stack traces that occur when the "like" action is triggered. This can provide more insight into what might be causing the internal server error.

  2. Verify Endpoint Configuration: Ensure that the endpoint POST /messages/:message_id/feedbacks is correctly configured and accessible in your self-hosted environment. Check for any misconfigurations in the API routes or permissions.

  3. Environment Variables: Confirm that all necessary environment variables and configurations for the feedback feature are correctly set in your Docker environment. Although specific configurations weren't found, ensuring that your environment matches the expected setup for Dify is crucial.

  4. Error Handling: Review the error handling mechanisms in place for server-side actions related to chat interactions. Ensure that any custom error handling logic does not interfere with the feedback process [2].

  5. Version Compatibility: Make sure that your Dify version (0.14.2) is compatible with the current setup and that there are no known issues with this version related to the feedback functionality.

If these steps do not resolve the issue, further investigation into the specific server-side implementation and configurations may be necessary.

To continue talking to Dosu, mention @dosu.


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

@yihong0618
Copy link
Contributor

Thanks will check

yihong0618 added a commit to yihong0618/dify that referenced this issue Dec 25, 2024
Signed-off-by: yihong0618 <zouzou0208@gmail.com>
@yihong0618
Copy link
Contributor

sorry for that bring by me and fixed #12058

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working good first issue Good first issue for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants