langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The PDF files uploaded via the API don’t seem to be recognized by the MinerU in the knowledge pipeline. #20101

New Issue
Closed
opened 2026-02-21 20:05:50 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 20:05:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @Richie666888 on GitHub (Nov 3, 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.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The PDF files uploaded via the API don’t seem to be recognized by the MinerU in the knowledge pipeline.

✔️ Expected Behavior

normal

❌ Actual Behavior

The PDF files uploaded via the API don’t seem to be recognized by the MinerU in the knowledge pipeline.

Originally created by @Richie666888 on GitHub (Nov 3, 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.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The PDF files uploaded via the API don’t seem to be recognized by the MinerU in the knowledge pipeline. ### ✔️ Expected Behavior normal ### ❌ Actual Behavior The PDF files uploaded via the API don’t seem to be recognized by the MinerU in the knowledge pipeline.
yindo added the 🐞 bug🌚 invalid labels 2026-02-21 20:05:50 -05:00
yindo closed this issue 2026-02-21 20:05:50 -05:00
yindo commented 2026-02-21 20:05:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 3, 2025):

This is a known issue in Dify self-hosted Docker setups: if the FILES_URL environment variable in your .env file is not set to a fully qualified URL (starting with http:// or https:// and pointing to your Dify API endpoint), file URLs generated for uploads will be invalid, causing MinerU to fail to recognize PDFs uploaded via the API. Make sure FILES_URL is set correctly, then restart your Docker containers for the change to take effect. If you need both internal and external access, also set INTERNAL_FILES_URL and SANDBOX_ENABLE_NETWORK as needed, and restart the containers after updating these values. This should resolve the issue with MinerU not recognizing PDF files uploaded via the API in the knowledge pipeline.
Reference

If your PDFs are scanned/image-only, Dify's extractor cannot extract text, which is expected and may also appear as "not recognized" after upload.
Reference

If you see 400 "Invalid user account" errors when uploading, ensure you are using a user-scoped API token with editor/operator privileges, not a dataset-scoped token.
Reference

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Nov 3, 2025): <!-- Answer --> This is a known issue in Dify self-hosted Docker setups: if the `FILES_URL` environment variable in your `.env` file is not set to a fully qualified URL (starting with `http://` or `https://` and pointing to your Dify API endpoint), file URLs generated for uploads will be invalid, causing MinerU to fail to recognize PDFs uploaded via the API. Make sure `FILES_URL` is set correctly, then restart your Docker containers for the change to take effect. If you need both internal and external access, also set `INTERNAL_FILES_URL` and `SANDBOX_ENABLE_NETWORK` as needed, and restart the containers after updating these values. This should resolve the issue with MinerU not recognizing PDF files uploaded via the API in the knowledge pipeline. [Reference](https://github.com/langgenius/dify/issues/27048) If your PDFs are scanned/image-only, Dify's extractor cannot extract text, which is expected and may also appear as "not recognized" after upload. [Reference](https://github.com/langgenius/dify/issues/18473) If you see 400 "Invalid user account" errors when uploading, ensure you are using a user-scoped API token with editor/operator privileges, not a dataset-scoped token. [Reference](https://github.com/langgenius/dify/discussions/26265) <!-- 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/0e66b064-c384-4a32-895b-0211beb42fde?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0e66b064-c384-4a32-895b-0211beb42fde?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0e66b064-c384-4a32-895b-0211beb42fde?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0e66b064-c384-4a32-895b-0211beb42fde?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0e66b064-c384-4a32-895b-0211beb42fde?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0e66b064-c384-4a32-895b-0211beb42fde?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0e66b064-c384-4a32-895b-0211beb42fde?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/27778)
yindo commented 2026-02-21 20:05:50 -05:00
Author
Owner
Copy Link
Copy Source

@Richie666888 commented on GitHub (Nov 3, 2025):

The same file can be correctly recognized by MinerU’s OCR when uploaded manually.

@Richie666888 commented on GitHub (Nov 3, 2025): The same file can be correctly recognized by MinerU’s OCR when uploaded manually.
yindo commented 2026-02-21 20:05:50 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 3, 2025):

This is not the first time you have submitted an issue. Please follow our Contributing Guidelines and provide complete context. This is not a suggestion box.

@crazywoola commented on GitHub (Nov 3, 2025): This is not the first time you have submitted an issue. Please follow our Contributing Guidelines and provide complete context. This is not a suggestion box.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🌚 invalid 🐞 bug
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#20101
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?