dify icon indicating copy to clipboard operation
dify copied to clipboard

Picture URL cannot be referenced

Open zhujie1990 opened this issue 10 months ago • 3 comments

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

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Picture URL cannot be referenced

✔️ Expected Behavior

Dify is unable to use image URLs for analysis, and the log error is as follows:2025-03-05 05:55:52.783 WARNING [Dummy-3] [ssrf_proxy.py:62] - Request to URL /files/9da2e8e6-5570-44b0-9c11-4563c8add0cc/file-preview?timestamp=1741154148&nonce=28f786e15a7915c7ecdd7e558fa7cdae&sign=N89jjU3QJfjITFhNwDzgFy6lY4Or_jtToMzxnUaGOv8= failed on attempt 4: Request URL is missing an ' http://' or ' https://' protocol.

FILES_URL= https://daw.ki3ngfeinecn.com/ How should I do it I have multiple images from different paths to analyzeThe error is as follows: Client error '400 Bad Request' for url 'https://daw.ki3ngfedinecn.com/fdfs/group1/M00/3E/files/955579d6-cf6c-48d6-b452-f6ec709b3fb4/file-preview?timestamp=1741227001&nonce=964fe487a8568ee7283f6e372875a442&sign=RCt9sYai-_0dmuwMhpuCq3sTJ01nIfxbDgAlHkZY1dg=' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400

❌ Actual Behavior

No response

zhujie1990 avatar Mar 06 '25 02:03 zhujie1990

To resolve the issue where Dify is unable to reference picture URLs due to a missing 'http://' or 'https://' protocol, resulting in a '400 Bad Request' error, ensure that all image URLs include the required protocol prefix ('http://' or 'https://'). This is a known limitation in Dify 0.15.3 when running in a self-hosted Docker environment. Additionally, consider using cloud-hosted images instead of local uploads to avoid this issue [1][2].

There are similar discussions and issues related to this problem:

  1. Unable to open image: /files/tools - This discussion is unsolved and was last updated on 2024-11-05.
  2. Unable to open image: /files/tools - This discussion is unsolved and was last updated on 2024-11-04.
  3. How to access image in knowledge repository? - This discussion is unsolved and was last updated on 2024-09-09.

Make sure your FILES_URL is correctly set with the appropriate protocol in your configuration.

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

dosubot[bot] avatar Mar 06 '25 02:03 dosubot[bot]

[volcengine_maas] Error: PluginInvokeError: {"args":{},"error_type":"ArkBadRequestError","message":"Error code: 400 - {'error': {'code': 'InvalidParameter.UnsupportedImageFormat', 'message': 'The request failed because the image format is not supported by the API. Request id: 02174441864151118eed0f78db1b735472d7048ab7ee678f7944c', 'param': 'image_url', 'type': 'BadRequest'}}, request_id: 20250412084401vc8StqpH6p32fw3xsvDx"}

dify 1.1.3

URLs: https://

filwu8 avatar Apr 12 '25 00:04 filwu8

@crazywoola, the user has indicated that they are still encountering a '400 Bad Request' error related to unsupported image formats in Dify 1.1.3. Could you please assist them with this issue?

dosubot[bot] avatar Apr 12 '25 00:04 dosubot[bot]