[Bug]: LookupError('Model(XXX___VLLM) not authorized')

[SpringYear]

Self Checks

• [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] Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• [x] Please do not modify this template :) and fill in all the required fields.

RAGFlow workspace code commit ID

I don't know how to fill this in

RAGFlow image version

v0.18.0 full

Other environment information

No response

Actual behavior

When I was testing using the rerank Model, it reported the error LookupError('Model(bge-reranker-v2-m3___VLLM) not authorized'), and I confirmed that my rerank model was running normally

Expected behavior

No response

Steps to reproduce

Additional information

No response

[SpringYear]

[dosubot[bot]]

The error LookupError('Model(bge-reranker-v2-m3___VLLM) not authorized') usually means the rerank model ID you selected is not recognized or authorized by RAGFlow. This can happen if the rerank_id is incorrect or not supported in your current setup.

To resolve this:

• Make sure you are using a valid rerank model ID. Known valid rerank models include:
  • BAAI/bge-reranker-v2-m3
  • maidalun1020/bce-reranker-base_v1
• You can check the list of valid rerank models by opening the "Rerank model" dropdown menu on the Retrieval Testing page in the UI. All options listed there are valid rerank_ids.
• If you try to use an invalid rerank_id, RAGFlow will raise a LookupError with the message "Model(xxx) not authorized" (source).

For the RAGFlow workspace code commit ID, you should enter the commit ID associated with the issue you are reporting. This is usually a short hash like 26d3480e. You can find this in your git history or from the commit log (source).

If your rerank model is running but you still see this error, double-check the exact rerank_id you are using and compare it to the valid options in the dropdown menu. If the problem persists, please provide the exact rerank_id value you are using for further troubleshooting.

To continue talking to Dosu, mention @dosu-bot.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[SpringYear]

The above picture has already shown that I opened the "Rerank model" drop-down menu on the Retrieval Testing page and selected the valid re-ranking model. But it still reported errors

[SpringYear]

I have found the reason. The rerank model needs to be set up at the administrator of the knowledge base