You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Request failed with status code: 500
Error: {"code": "internal_server_error", "message": "The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.", "status": 500}
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered:
I found a similar closed issue related to an "Internal Server Error" when using the Get Conversation History Messages API endpoint. This issue was resolved by a pull request that fixed a specific field handling [1].
For your specific case, ensure that the upload_file_id is correctly obtained by uploading the file through the File Upload API before making the request. The upload_file_id should not be a file path but an ID returned from the upload process. Additionally, verify that all server configurations, such as database and Redis settings, are correctly set up in your self-hosted environment [2].
Please provide the container logs instead. If you are using source code to start it, please make sure you can handle it by yourself, otherwise please do not use source code to start it.
We assume you have the ability to resolve issues, especially this backend error, you should provide the container logs.
Self Checks
Dify version
0.15
Cloud or Self Hosted
Self Hosted (Source)
Steps to reproduce
errors"
Request failed with status code: 500
Error: {"code": "internal_server_error", "message": "The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.", "status": 500}
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: