mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
Add OpenAI-API-compatible Rerank error 400 Client Error #92
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fancywus on GitHub (Mar 19, 2025).
Self Checks
Dify version
0.15.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Expected Behavior
add reranker model config success
❌ Actual Behavior
Add OpenAI-API-compatible Rerank error 400 Client Error
@dosubot[bot] commented on GitHub (Mar 19, 2025):
Hey @fancywus! I'm here to assist you with any bugs, questions, or contributions you have for Dify. Let's tackle this issue together!
To resolve the 400 Client Error when adding an OpenAI-API-compatible reranker model in Dify version 0.15.3 using Docker, you should upgrade to Dify version 1.0.0 or higher. Additionally, ensure that the OpenAI-API-compatible plugin is version 0.0.6 or higher. The fix for the issue related to the
top_nparameter has been implemented in these versions, eliminating the need for manual code modification [1].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
@fancywus commented on GitHub (Mar 20, 2025):
Is there any other solution besides upgrading the version? As version 1.0 is a major upgrade, we are currently not considering exaggerating the version upgrade.
@fancywus commented on GitHub (Mar 20, 2025):
I saw you mentioned elsewhere that the reranker.py file could solve the problem. I tried using the default settings but it still didn't work. After I made the modifications, I restarted the Docker service, but it still reported an error.

@dosubot[bot] commented on GitHub (Aug 17, 2025):
Hi, @fancywus. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
top_nparameter.Next Steps:
Thank you for your understanding and contribution!