langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Error message when using minerU tool #463

New Issue
Closed
opened 2026-02-16 10:19:29 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 10:19:29 -05:00
Owner
Copy Link
Copy Source

Originally created by @tianshiqingge on GitHub (Jul 21, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.6.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The minerU tool reported an error when adding the AIP key, but adding the same API key to another DIFY server is not a problem. What is the problem?

Image

✔️ Expected Behavior

The minerU tool reported an error when adding the AIP key

❌ Actual Behavior

No response

Originally created by @tianshiqingge on GitHub (Jul 21, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.6.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The minerU tool reported an error when adding the AIP key, but adding the same API key to another DIFY server is not a problem. What is the problem? <img width="398" height="504" alt="Image" src="https://github.com/user-attachments/assets/541a7e80-0b75-4dc1-8eac-012d33cec57a" /> ### ✔️ Expected Behavior The minerU tool reported an error when adding the AIP key ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-16 10:19:29 -05:00
yindo commented 2026-02-16 10:19:29 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 21, 2025):

The error you're seeing (ToolProviderCredentialValidationError) usually means there's a mismatch or missing field in the credentials for the minerU tool. Even if the API key is correct, the credential schema (fields like auth_type, api_key_value, or header/query param names) must match exactly between your Dify servers. Recent changes in Dify now support both header and query parameter authentication, with defaults set to Authorization for headers and key for query params—if your Docker .env or tool config differs between servers, this can cause validation to fail even with the same key [source].

Check these on both servers:

  • The credential schema for the minerU tool (especially auth_type and api_key_value) matches exactly.
  • The .env file and Docker configs use the same service URLs (localhost vs 127.0.0.1 can matter after recent updates) [source].
  • If minerU is an MCP tool, make sure the MCP server/tool definitions are synced and re-authorize if needed [source].

If you still get the error, compare the full credential JSON/schema for minerU on both servers—any drift will cause this error. Let me know if you want a step-by-step checklist for comparing configs.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 21, 2025): <!-- Answer --> The error you're seeing (ToolProviderCredentialValidationError) usually means there's a mismatch or missing field in the credentials for the minerU tool. Even if the API key is correct, the credential schema (fields like `auth_type`, `api_key_value`, or header/query param names) must match exactly between your Dify servers. Recent changes in Dify now support both header and query parameter authentication, with defaults set to `Authorization` for headers and `key` for query params—if your Docker `.env` or tool config differs between servers, this can cause validation to fail even with the same key [[source](https://github.com/langgenius/dify/pull/21656)]. Check these on both servers: - The credential schema for the minerU tool (especially `auth_type` and `api_key_value`) matches exactly. - The `.env` file and Docker configs use the same service URLs (`localhost` vs `127.0.0.1` can matter after recent updates) [[source](https://github.com/langgenius/dify/pull/22550)]. - If minerU is an MCP tool, make sure the MCP server/tool definitions are synced and re-authorize if needed [[source](https://github.com/crazywoola/dify-docs-mintlify/blob/a6647b33df40ace51422b11f355ec6e2618bc05e/en/guides/tools/mcp.mdx)]. If you still get the error, compare the full credential JSON/schema for minerU on both servers—any drift will cause this error. Let me know if you want a step-by-step checklist for comparing configs. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/6bcb3322-8193-4781-9324-6a595200a7d2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6bcb3322-8193-4781-9324-6a595200a7d2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6bcb3322-8193-4781-9324-6a595200a7d2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6bcb3322-8193-4781-9324-6a595200a7d2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6bcb3322-8193-4781-9324-6a595200a7d2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6bcb3322-8193-4781-9324-6a595200a7d2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6bcb3322-8193-4781-9324-6a595200a7d2?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/22732)
yindo commented 2026-02-16 10:19:29 -05:00
Author
Owner
Copy Link
Copy Source

@tianshiqingge commented on GitHub (Jul 21, 2025):

@dosu Please tell me what to do

@tianshiqingge commented on GitHub (Jul 21, 2025): @dosu Please tell me what to do
yindo commented 2026-02-16 10:19:29 -05:00
Author
Owner
Copy Link
Copy Source

@lichangfeng-1 commented on GitHub (Jul 22, 2025):

Plugin Name
mineu2

Function Description
现有的插件存在api对接失败的问题
我是本地部署的 dify 和 minerU2，
dify的现有的0.2 版本 minerU插件信息：
PARSE FILE：
输入：
{
"file": {
"dify_model_identity": "dify__file",
"id": null,
"tenant_id": "739f5fff-6xxxxxxxxxxxxxx42",
"type": "document",
"transfer_method": "local_file",
"remote_url": "xxxxx",[这个地址可以在局域网打开，是 一个我上传的pdf文件]
"filename": "3.行业应用篇-DeepSeek入门宝典.pdf",
"extension": ".pdf",
"mime_type": "application/pdf",
"size": 1325796,
"url": "xxxxxx"
}
}
输出：
{
"text": "Failed to parse file. result: {"detail":[{"type":"missing","loc":["body","files"],"msg":"Field required","input":null}]}",
"files": [],
"json": [
{
"data": []
}
]
}

minerU2 后台日志：
INFO:"POST /file_parse?parse_method=auto&return_layout=False&return_info=False&return_content_list=True&return_images=True HTTP/1.1" 422 Unprocessable Entity

Image
Official Website URL
https://github.com/opendatalab/mineru

@lichangfeng-1 commented on GitHub (Jul 22, 2025): Plugin Name mineu2 Function Description 现有的插件存在api对接失败的问题 我是本地部署的 dify 和 minerU2， dify的现有的0.2 版本 minerU插件信息： PARSE FILE： 输入： { "file": { "dify_model_identity": "dify__file", "id": null, "tenant_id": "739f5fff-6xxxxxxxxxxxxxx42", "type": "document", "transfer_method": "local_file", "remote_url": "xxxxx",[这个地址可以在局域网打开，是 一个我上传的pdf文件] "filename": "3.行业应用篇-DeepSeek入门宝典.pdf", "extension": ".pdf", "mime_type": "application/pdf", "size": 1325796, "url": "xxxxxx" } } 输出： { "text": "Failed to parse file. result: {"detail":[{"type":"missing","loc":["body","files"],"msg":"Field required","input":null}]}", "files": [], "json": [ { "data": [] } ] } minerU2 后台日志： INFO:"POST /file_parse?parse_method=auto&return_layout=False&return_info=False&return_content_list=True&return_images=True HTTP/1.1" 422 Unprocessable Entity Image Official Website URL https://github.com/opendatalab/mineru
yindo commented 2026-02-16 10:19:29 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 20, 2025):

Hi, @tianshiqingge. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported an error with the minerU tool on a self-hosted Dify 1.6.0 Docker setup when adding an API key, despite the key working on another server.
  • The problem likely involves mismatched credential schemas or configuration differences between your servers, such as auth_type or API key field names.
  • Another user noted similar API connection failures with the minerU2 plugin, sharing error logs about missing required fields during file parsing.
  • The discussion has focused on credential validation and ensuring configuration consistency to fix the integration issue.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If I do not hear back within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 20, 2025): Hi, @tianshiqingge. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported an error with the minerU tool on a self-hosted Dify 1.6.0 Docker setup when adding an API key, despite the key working on another server. - The problem likely involves mismatched credential schemas or configuration differences between your servers, such as `auth_type` or API key field names. - Another user noted similar API connection failures with the minerU2 plugin, sharing error logs about missing required fields during file parsing. - The discussion has focused on credential validation and ensuring configuration consistency to fix the integration issue. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If I do not hear back within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#463
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?