dify PDF extractor ERROR:UnsupportedProtocol

Self Checks

[x] This is only for bug report, if you would like to ask a question, please head to Discussions.
[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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[x] Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Deploy dify locally and create a chatflow，Error when using PDF Extractor：

✔️ Expected Behavior

I want to extract the file contents using PDF Extractor normally

❌ Actual Behavior

No response

Mar 20 '25 08:03 sunxiaoyu12

Hello, @sunxiaoyu12! I'm here to help you with any bugs, questions, or contributions. Let's work together to solve the issue you're experiencing.

I couldn't find specific information about the 'UnsupportedProtocol' error in the PDF Extractor within the Dify repository. However, there was a similar closed issue related to URL retrieval errors, which was resolved by updating the length of the original_url column in the database to accommodate longer URLs ^[1]^[2].

For the 'UnsupportedProtocol' error, it might be helpful to check if the URL being used in the PDF Extractor is correctly formatted and includes a supported protocol. If the issue persists, reviewing the code handling URL processing in the PDF Extractor might provide insights into which protocols are supported and how they are determined.

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}

Mar 20 '25 08:03 dosubot[bot]

1.1.1 。minerU haved meet the same thing

Mar 21 '25 07:03 quchenchen

I encountered an issue reading .doc files while using version 1.1.1, so I'm not sure if it's the same problem. Additionally, even after disabling "Deep Thinking" and switching to the DeepSeek V3 model, the issue still persists.

https://github.com/langgenius/dify/issues/16445

Mar 21 '25 08:03 levin950825

i have same problem, please tell me how to fix it 。

Mar 21 '25 08:03 bin-bin-6

More like a BUG.

Mar 21 '25 09:03 levin950825

DIY version: 1.1.2 Mineru tool version: 0.0.1 I also encountered the same prompt in the miner tool. Is there any way to solve it? Or should I go to DIY official plugins to report bugs?

Mar 23 '25 01:03 woqulegenicheng

Please see https://github.com/langgenius/dify-plugin-sdks/issues/58

Mar 23 '25 15:03 fdb02983rhy

Please configure the FILES_URL in the .env file as http://your-ip:port. If you are using docker compose to start all services, please configure the FILES_URL as http://your-ip.

Mar 26 '25 09:03 Gevtolev

Please configure the FILES_URL in the .env file as http://your-ip:port. If you are using docker compose to start all services, please configure the FILES_URL as http://your-ip.

This is indeed an effective solution, but it will cause the dialog preview and the transmission of files within the plugin to both require http requests that depend on IP addresses, and it is hoped that this can be distinguished.

Mar 27 '25 13:03 keepsmilence

请将 .env 文件中的 FILES_URL 配置为 http：//your-ip：port。如果您使用 docker compose 启动所有服务，请将FILES_URL配置为 http://your-ip。

This doesn't apply to me, my dify is on the LAN, MinerU and other file handlers are on the Internet, the LAN where dify is located only has a public Internet exit, no fixed Internet IP

Mar 28 '25 01:03 woqulegenicheng

Please configure the FILES_URL in the .env file as http://your-ip:port. If you are using docker compose to start all services, please configure the FILES_URL as http://your-ip.

very good!!!MinerU plugin is worked.

Apr 02 '25 09:04 BigRou

I have also encountered this problem. Restart the dify container after modifying the Files_URL parameter to the host's IP Then an error appeared:

Apr 25 '25 09:04 moncat2005