Using MinerU in Dify reports a ConnectError

[fruitage]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues Dify issues & Dify Official Plugins, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.11.1

Plugin version

0.5.1

Cloud or Self Hosted

Cloud, Self Hosted (Source)

Steps to reproduce

It worked fine in version 1.7.2, but after upgrading Dify to version 1.11.1, using a locally deployed mineru-api throws a ConnectError.

✔️ Error log

An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: ConnectError, error details: [Errno -2] Name or service not known

FAIL
运行时间
1.048s
总 token 数
0 Tokens
An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: ConnectError, error details: [Errno -2] Name or service not known
流程中有 1 个节点运行异常，请前往追踪查看日志。

[dosubot]

Hi @fruitage! I'm Dosu and I’m helping the dify-official-plugins team.

The ConnectError ([Errno -2] Name or service not known) after upgrading is caused by stricter validation in recent MinerU plugin and Dify versions: the plugin now requires the base_url for your local mineru-api to be a resolvable LAN IP address, not localhost or 127.0.0.1. Any hostname that can't be resolved from the Dify environment will trigger this error immediately.

To fix this:

1. Find the current LAN IP of the machine running mineru-api (e.g., 192.168.x.x).
2. Update the MinerU plugin's base_url in Dify to use this IP and the correct port (e.g., http://192.168.x.x:8888).
3. Set server_type to local and leave the token blank.
4. Make sure mineru-api is running and accessible from the Dify environment (test with curl or browser from the Dify container/host).
5. If your local IP changed (for example, after switching networks), update both the plugin's base_url and, if needed, the FILES_URL in Dify's .env file, then restart Dify for changes to take effect.

If you still see the error after these steps, check for network or firewall issues between Dify and mineru-api, and try running network diagnostics from within the Dify environment to confirm connectivity.

References:

• MinerU plugin README: LAN IP requirement and troubleshooting
• MinerU plugin code: stricter base_url validation and error handling

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}