aihubmix-image plugin error #972

Open
opened 2026-02-16 10:21:09 -05:00 by yindo · 4 comments
Owner

Originally created by @wenjoying on GitHub (Feb 12, 2026).

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.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I encountered an error while using the aihubmix-image plugin (version 0.0.5). The error still occurs even after reinstallation, as shown in the screenshot below

Image

✔️ Expected Behavior

I expected the plugin to work properly.

Actual Behavior

Tool: gpt-image-edit
Outputs: {"type":"text","message":{"text":"Editing image with GPT Image Edit using model: gpt-image-1..."},"meta":null}

2026-02-12 02:42:55,234.234 ERROR [GraphWorker-1] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\"args\":{\"description\":\"GPT Image Edit failed: Error downloading image from URL: Failed to download image from URL: https://ai.xxxxxx.cn/files/79edfd09-b868-47f0-bc7f-5f8555a56047/file-preview?timestamp=1770864082\\u0026nonce=ea50f9488813ad905ed5c0ae806bbfbb\\u0026sign=bcahtzE3W4kE1pnA_qcZV1wcIoH6dZlMPkK6brLOZRg%3D\"},\"error_type\":\"InvokeError\",\"message\":\"GPT Image Edit failed: Error downloading image from URL: Failed to download image from URL: https://ai.xxxx.cn/files/79edfd09-b868-47f0-bc7f-5f8555a56047/file-preview?timestamp=1770864082\\u0026nonce=ea50f9488813ad905ed5c0ae806bbfbb\\u0026sign=bcahtzE3W4kE1pnA_qcZV1wcIoH6dZlMPkK6brLOZRg%3D\"}","error_type":"PluginInvokeError","args":null}', 'data': None}

Originally created by @wenjoying on GitHub (Feb 12, 2026). ### 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.11.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I encountered an error while using the aihubmix-image plugin (version 0.0.5). The error still occurs even after reinstallation, as shown in the screenshot below <img width="788" height="842" alt="Image" src="https://github.com/user-attachments/assets/aa08ee6c-1d51-40ba-a6ce-8ab4e8795d71" /> <!-- Failed to upload "image.png" --> ### ✔️ Expected Behavior I expected the plugin to work properly. ### ❌ Actual Behavior Tool: gpt-image-edit Outputs: {"type":"text","message":{"text":"Editing image with GPT Image Edit using model: gpt-image-1..."},"meta":null}  2026-02-12 02:42:55,234.234 ERROR [GraphWorker-1] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{\\"description\\":\\"GPT Image Edit failed: Error downloading image from URL: Failed to download image from URL: https://ai.xxxxxx.cn/files/79edfd09-b868-47f0-bc7f-5f8555a56047/file-preview?timestamp=1770864082\\\\u0026nonce=ea50f9488813ad905ed5c0ae806bbfbb\\\\u0026sign=bcahtzE3W4kE1pnA_qcZV1wcIoH6dZlMPkK6brLOZRg%3D\\"},\\"error_type\\":\\"InvokeError\\",\\"message\\":\\"GPT Image Edit failed: Error downloading image from URL: Failed to download image from URL: https://ai.xxxx.cn/files/79edfd09-b868-47f0-bc7f-5f8555a56047/file-preview?timestamp=1770864082\\\\u0026nonce=ea50f9488813ad905ed5c0ae806bbfbb\\\\u0026sign=bcahtzE3W4kE1pnA_qcZV1wcIoH6dZlMPkK6brLOZRg%3D\\"}","error_type":"PluginInvokeError","args":null}', 'data': None}
yindo added the bug label 2026-02-16 10:21:09 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Feb 12, 2026):

Hi @wenjoying! I'm Dosu and I’m helping the dify team.

Looking at the error message and the aihubmix-image plugin code, this appears to be a network connectivity issue between the plugin and your Dify file storage URL (https://ai.xxxxxx.cn/files/...).

The plugin has a 30-second timeout for downloading images, and the error occurs when the HTTP request fails for any reason (timeout, connection error, SSL issues, or non-200 response).

Possible causes:

  1. The plugin container cannot reach your Dify internal file URLs (network isolation issue)
  2. The signed URL may have expired before the plugin could download it
  3. SSL certificate verification issues between containers

Workarounds to try:

  • Instead of using Dify file references, try providing the image as a base64-encoded string
  • Check if your plugin container has network access to your Dify API server
  • If using Docker, ensure the plugin container and Dify containers are on the same network

There have been recent improvements to image handling in this plugin, so updating to the latest version may also help if a newer version is available.

To reply, just mention @dosu.


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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 12, 2026): <!-- Greeting --> Hi @wenjoying! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> Looking at the error message and the [aihubmix-image plugin code](https://github.com/langgenius/dify-official-plugins/blob/4e51c74d48fa6d3bd1c864858f65faf6e56aa2be/tools/aihubmix_image/tools/gpt-image-edit.py#L139-L149), this appears to be a network connectivity issue between the plugin and your Dify file storage URL (`https://ai.xxxxxx.cn/files/...`). The plugin has a 30-second timeout for downloading images, and the error occurs when the HTTP request fails for any reason (timeout, connection error, SSL issues, or non-200 response). **Possible causes:** 1. The plugin container cannot reach your Dify internal file URLs (network isolation issue) 2. The signed URL may have expired before the plugin could download it 3. SSL certificate verification issues between containers **Workarounds to try:** - Instead of using Dify file references, try providing the image as a base64-encoded string - Check if your plugin container has network access to your Dify API server - If using Docker, ensure the plugin container and Dify containers are on the same network There have been [recent improvements to image handling](https://github.com/langgenius/dify-official-plugins/pull/2429) in this plugin, so updating to the latest version may also help if a newer version is available. <!-- 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/c51cb643-c71b-4718-b65d-f749d9a48897?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c51cb643-c71b-4718-b65d-f749d9a48897?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c51cb643-c71b-4718-b65d-f749d9a48897?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c51cb643-c71b-4718-b65d-f749d9a48897?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c51cb643-c71b-4718-b65d-f749d9a48897?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c51cb643-c71b-4718-b65d-f749d9a48897?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c51cb643-c71b-4718-b65d-f749d9a48897?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Looking%20at%20the%20error%20message%20and%20the%20%5Baihubmix-image%20plugin%20code%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/4e51c74d48fa6d3bd1c864858f65faf6e56aa2be/tools/aihubmix_image/tools/gpt-image-edit.py%23L139-L149%29%2C%20this%20appears%20to%20be%20a%20network%20connectivity%20issue%20between%20the%20plugin%20and%20your%20Dify%20file%20storage%20URL%20%28%60https%3A//ai.xxxxxx.cn/files/...%60%29.%0A%0AThe%20plugin%20has%20a%2030-second%20timeout%20for%20downloading%20images%2C%20and%20the%20error%20occurs%20when%20the%20HTTP%20request%20fails%20for%20any%20reason%20%28timeout%2C%20connection%20error%2C%20SSL%20issues%2C%20or%20non-200%20response%29.%0A%0A%2A%2APossible%20causes%3A%2A%2A%0A1.%20The%20plugin%20container%20cannot%20reach%20your%20Dify%20internal%20file%20URLs%20%28network%20isolation%20issue%29%0A2.%20The%20signed%20URL%20may%20have%20expired%20before%20the%20plugin%20could%20download%20it%0A3.%20SSL%20certificate%20verification%20issues%20between%20containers%0A%0A%2A%2AWorkarounds%20to%20try%3A%2A%2A%0A-%20Instead%20of%20using%20Dify%20file%20references%2C%20try%20providing%20the%20image%20as%20a%20base64-encoded%20string%0A-%20Check%20if%20your%20plugin%20container%20has%20network%20access%20to%20your%20Dify%20API%20server%0A-%20If%20using%20Docker%2C%20ensure%20the%20plugin%20container%20and%20Dify%20containers%20are%20on%20the%20same%20network%0A%0AThere%20have%20been%20%5Brecent%20improvements%20to%20image%20handling%5D%28https%3A//github.com/langgenius/dify-official-plugins/pull/2429%29%20in%20this%20plugin%2C%20so%20updating%20to%20the%20latest%20version%20may%20also%20help%20if%20a%20newer%20version%20is%20available.)&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/32279)
Author
Owner

@wenjoying commented on GitHub (Feb 12, 2026):

1.The file has not expired and is accessible in the browser. However, the plugin consistently throws an error no matter how many times I attempt to invoke it, and switching to other versions also results in errors; only version 0.0.2 works normally.
2.The plugin container and Dify are on the same network.
3.The length of the base64-encoded string will most likely exceed the parameter length limit.

@wenjoying commented on GitHub (Feb 12, 2026): 1.The file has not expired and is accessible in the browser. However, the plugin consistently throws an error no matter how many times I attempt to invoke it, and switching to other versions also results in errors; only version 0.0.2 works normally. 2.The plugin container and Dify are on the same network. 3.The length of the base64-encoded string will most likely exceed the parameter length limit.
Author
Owner

@dosubot[bot] commented on GitHub (Feb 12, 2026):

Thanks for the additional details. This is helpful.

Looking at the version history, PR langgenius/dify#2410 (v0.0.2 → v0.0.3) introduced significant changes to how image inputs are processed. The plugin now handles Dify file transfer variables differently, with separate logic for remote_url vs local_file transfer methods.

One key observation: the current image download code makes plain HTTP requests without any authentication headers:

response = requests.get(image_file, timeout=30)

If Dify's internal file URLs require authentication (common for security), this would explain why the URL works in your browser (session cookies) but fails in the plugin. Since v0.0.2 may have handled image input differently (possibly receiving base64 directly rather than URLs), this authentication gap wouldn't have affected older versions.

This appears to be a regression or limitation in how v0.0.3+ handles Dify internal file URLs. It would be worth filing this as an issue on the dify-official-plugins repository, as the plugin may need to either:

  1. Accept authentication context when downloading internal Dify files
  2. Use Dify's file transfer mechanism to get base64 data instead of URLs

To reply, just mention @dosu.


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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 12, 2026): <!-- Answer --> Thanks for the additional details. This is helpful. Looking at the version history, [PR langgenius/dify#2410](https://github.com/langgenius/dify-official-plugins/pull/2410) (v0.0.2 → v0.0.3) introduced significant changes to how image inputs are processed. The plugin now handles Dify file transfer variables differently, with separate logic for `remote_url` vs `local_file` transfer methods. One key observation: the [current image download code](https://github.com/langgenius/dify-official-plugins/blob/4e51c74d48fa6d3bd1c864858f65faf6e56aa2be/tools/aihubmix_image/tools/gpt-image-edit.py#L143) makes plain HTTP requests **without any authentication headers**: ```python response = requests.get(image_file, timeout=30) ``` If Dify's internal file URLs require authentication (common for security), this would explain why the URL works in your browser (session cookies) but fails in the plugin. Since v0.0.2 may have handled image input differently (possibly receiving base64 directly rather than URLs), this authentication gap wouldn't have affected older versions. This appears to be a regression or limitation in how v0.0.3+ handles Dify internal file URLs. It would be worth filing this as an issue on the [dify-official-plugins](https://github.com/langgenius/dify-official-plugins) repository, as the plugin may need to either: 1. Accept authentication context when downloading internal Dify files 2. Use Dify's file transfer mechanism to get base64 data instead of URLs <!-- 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/7f50d690-5886-4a18-805e-2cc2a9eafa4b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7f50d690-5886-4a18-805e-2cc2a9eafa4b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7f50d690-5886-4a18-805e-2cc2a9eafa4b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7f50d690-5886-4a18-805e-2cc2a9eafa4b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7f50d690-5886-4a18-805e-2cc2a9eafa4b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7f50d690-5886-4a18-805e-2cc2a9eafa4b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7f50d690-5886-4a18-805e-2cc2a9eafa4b?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Thanks%20for%20the%20additional%20details.%20This%20is%20helpful.%0A%0ALooking%20at%20the%20version%20history%2C%20%5BPR%20%232410%5D%28https%3A//github.com/langgenius/dify-official-plugins/pull/2410%29%20%28v0.0.2%20%E2%86%92%20v0.0.3%29%20introduced%20significant%20changes%20to%20how%20image%20inputs%20are%20processed.%20The%20plugin%20now%20handles%20Dify%20file%20transfer%20variables%20differently%2C%20with%20separate%20logic%20for%20%60remote_url%60%20vs%20%60local_file%60%20transfer%20methods.%0A%0AOne%20key%20observation%3A%20the%20%5Bcurrent%20image%20download%20code%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/4e51c74d48fa6d3bd1c864858f65faf6e56aa2be/tools/aihubmix_image/tools/gpt-image-edit.py%23L143%29%20makes%20plain%20HTTP%20requests%20%2A%2Awithout%20any%20authentication%20headers%2A%2A%3A%0A%60%60%60python%0Aresponse%20%3D%20requests.get%28image_file%2C%20timeout%3D30%29%0A%60%60%60%0A%0AIf%20Dify%27s%20internal%20file%20URLs%20require%20authentication%20%28common%20for%20security%29%2C%20this%20would%20explain%20why%20the%20URL%20works%20in%20your%20browser%20%28session%20cookies%29%20but%20fails%20in%20the%20plugin.%20Since%20v0.0.2%20may%20have%20handled%20image%20input%20differently%20%28possibly%20receiving%20base64%20directly%20rather%20than%20URLs%29%2C%20this%20authentication%20gap%20wouldn%27t%20have%20affected%20older%20versions.%0A%0AThis%20appears%20to%20be%20a%20regression%20or%20limitation%20in%20how%20v0.0.3%2B%20handles%20Dify%20internal%20file%20URLs.%20It%20would%20be%20worth%20filing%20this%20as%20an%20issue%20on%20the%20%5Bdify-official-plugins%5D%28https%3A//github.com/langgenius/dify-official-plugins%29%20repository%2C%20as%20the%20plugin%20may%20need%20to%20either%3A%0A1.%20Accept%20authentication%20context%20when%20downloading%20internal%20Dify%20files%0A2.%20Use%20Dify%27s%20file%20transfer%20mechanism%20to%20get%20base64%20data%20instead%20of%20URLs)&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/32279)
Author
Owner

@dosubot[bot] commented on GitHub (Feb 12, 2026):

Based on research into the plugin code, here's what I found about your two errors:

1. Gemini "No images returned in the response"
The Gemini tool silently skips images that fail to convert, so this error means all image parts in the API response failed to process. This could be due to the AIHubMix API returning data in an unexpected format.

2. GPT Image Edit "Failed to download image from URL"
The error shows the plugin couldn't download your Dify file URL. In self-hosted Docker setups, this often happens when the plugin container can't reach the URL due to network configuration (the URL https://ai.xxxxxx.cn/files/... may not be accessible from within the Docker network).

Troubleshooting suggestions:

  • Verify your Docker container can reach external URLs (test with curl from inside the container)
  • Check if your Dify domain is resolvable from the plugin container
  • Ensure your AIHubMix API key is valid and has sufficient quota
  • Recent timeouts were extended to 300 seconds for large images - verify you're on the latest plugin version

Could you share the raw API response or test if network requests work from your Docker container? That would help narrow down whether this is a network issue or an API response format problem.

To reply, just mention @dosu.


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

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 12, 2026): <!-- Answer --> Based on research into the plugin code, here's what I found about your two errors: **1. Gemini "No images returned in the response"** The [Gemini tool silently skips images that fail to convert](https://github.com/langgenius/dify-official-plugins/blob/4e51c74d48fa6d3bd1c864858f65faf6e56aa2be/tools/aihubmix_image/tools/gemini-3-pro-image-preview.py#L244-L264), so this error means all image parts in the API response failed to process. This could be due to the AIHubMix API returning data in an unexpected format. **2. GPT Image Edit "Failed to download image from URL"** The error shows the plugin couldn't download your Dify file URL. In self-hosted Docker setups, this often happens when the plugin container can't reach the URL due to network configuration (the URL `https://ai.xxxxxx.cn/files/...` may not be accessible from within the Docker network). **Troubleshooting suggestions:** - Verify your Docker container can reach external URLs (test with `curl` from inside the container) - Check if your Dify domain is resolvable from the plugin container - Ensure your AIHubMix API key is valid and has sufficient quota - [Recent timeouts were extended to 300 seconds](https://github.com/langgenius/dify-official-plugins/pull/2401) for large images - verify you're on the latest plugin version Could you share the raw API response or test if network requests work from your Docker container? That would help narrow down whether this is a network issue or an API response format problem. <!-- 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/5233e450-eafe-475c-86d5-0b3311826ad9?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5233e450-eafe-475c-86d5-0b3311826ad9?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5233e450-eafe-475c-86d5-0b3311826ad9?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5233e450-eafe-475c-86d5-0b3311826ad9?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5233e450-eafe-475c-86d5-0b3311826ad9?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5233e450-eafe-475c-86d5-0b3311826ad9?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5233e450-eafe-475c-86d5-0b3311826ad9?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Based%20on%20research%20into%20the%20plugin%20code%2C%20here%27s%20what%20I%20found%20about%20your%20two%20errors%3A%0A%0A%2A%2A1.%20Gemini%20%22No%20images%20returned%20in%20the%20response%22%2A%2A%20%20%0AThe%20%5BGemini%20tool%20silently%20skips%20images%20that%20fail%20to%20convert%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/4e51c74d48fa6d3bd1c864858f65faf6e56aa2be/tools/aihubmix_image/tools/gemini-3-pro-image-preview.py%23L244-L264%29%2C%20so%20this%20error%20means%20all%20image%20parts%20in%20the%20API%20response%20failed%20to%20process.%20This%20could%20be%20due%20to%20the%20AIHubMix%20API%20returning%20data%20in%20an%20unexpected%20format.%0A%0A%2A%2A2.%20GPT%20Image%20Edit%20%22Failed%20to%20download%20image%20from%20URL%22%2A%2A%20%20%0AThe%20error%20shows%20the%20plugin%20couldn%27t%20download%20your%20Dify%20file%20URL.%20In%20self-hosted%20Docker%20setups%2C%20this%20often%20happens%20when%20the%20plugin%20container%20can%27t%20reach%20the%20URL%20due%20to%20network%20configuration%20%28the%20URL%20%60https%3A//ai.xxxxxx.cn/files/...%60%20may%20not%20be%20accessible%20from%20within%20the%20Docker%20network%29.%0A%0A%2A%2ATroubleshooting%20suggestions%3A%2A%2A%0A-%20Verify%20your%20Docker%20container%20can%20reach%20external%20URLs%20%28test%20with%20%60curl%60%20from%20inside%20the%20container%29%0A-%20Check%20if%20your%20Dify%20domain%20is%20resolvable%20from%20the%20plugin%20container%0A-%20Ensure%20your%20AIHubMix%20API%20key%20is%20valid%20and%20has%20sufficient%20quota%0A-%20%5BRecent%20timeouts%20were%20extended%20to%20300%20seconds%5D%28https%3A//github.com/langgenius/dify-official-plugins/pull/2401%29%20for%20large%20images%20-%20verify%20you%27re%20on%20the%20latest%20plugin%20version%0A%0ACould%20you%20share%20the%20raw%20API%20response%20or%20test%20if%20network%20requests%20work%20from%20your%20Docker%20container%3F%20That%20would%20help%20narrow%20down%20whether%20this%20is%20a%20network%20issue%20or%20an%20API%20response%20format%20problem.)&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-official-plugins/issues/2584)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#972