langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

When using the start node of the workflow, I encountered an error after entering the image URL. #8421

New Issue
Closed
opened 2026-02-21 18:25:37 -05:00 by yindo · 6 comments
yindo commented 2026-02-21 18:25:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @ajistyle on GitHub (Feb 19, 2025).

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 search for existing issues, 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

v0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

workflow -- start node -- input image URL.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @ajistyle on GitHub (Feb 19, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version v0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce workflow -- start node -- input image URL. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🌚 invalid🤔 cant-reproduce labels 2026-02-21 18:25:37 -05:00
yindo closed this issue 2026-02-21 18:25:37 -05:00
yindo commented 2026-02-21 18:25:37 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 19, 2025):

An error for what？

@crazywoola commented on GitHub (Feb 19, 2025): An error for what？
yindo commented 2026-02-21 18:25:37 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 19, 2025):

Hello @ajistyle! I'm here to help you with any bugs, questions, or contributions you have for the Dify project. Let me know how I can assist you while we wait for a human maintainer.

To address the issue with the start node in the workflow when handling image URLs in Dify v0.15.3, ensure that your configuration settings are correct. Specifically, for a self-hosted setup using Docker, you need to:

  1. Set the MULTIMODAL_SEND_IMAGE_FORMAT to 'url' in your environment settings.
  2. Ensure that FILES_URL is configured with an externally accessible address.

These settings are crucial for processing images via URLs. Additionally, when accessing the image URL after an upload, use the remote_url property in code nodes to retrieve the image URL, as file.url may return null in this context [1][2].

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] commented on GitHub (Feb 19, 2025): <!-- Greeting --> Hello @ajistyle! I'm here to help you with any bugs, questions, or contributions you have for the Dify project. Let me know how I can assist you while we wait for a human maintainer. <!-- Answer --> To address the issue with the start node in the workflow when handling image URLs in Dify v0.15.3, ensure that your configuration settings are correct. Specifically, for a self-hosted setup using Docker, you need to: 1. Set the `MULTIMODAL_SEND_IMAGE_FORMAT` to 'url' in your environment settings. 2. Ensure that `FILES_URL` is configured with an externally accessible address. These settings are crucial for processing images via URLs. Additionally, when accessing the image URL after an upload, use the `remote_url` property in code nodes to retrieve the image URL, as `file.url` may return null in this context <sup>[[1]](https://github.com/langgenius/dify/issues/13658)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/11543)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/d9a4eae1-3226-4240-be42-bd431f65d6e1?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/d9a4eae1-3226-4240-be42-bd431f65d6e1?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/d9a4eae1-3226-4240-be42-bd431f65d6e1?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/d9a4eae1-3226-4240-be42-bd431f65d6e1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d9a4eae1-3226-4240-be42-bd431f65d6e1?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/d9a4eae1-3226-4240-be42-bd431f65d6e1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d9a4eae1-3226-4240-be42-bd431f65d6e1?feedback_type=other)</sup>
yindo commented 2026-02-21 18:25:37 -05:00
Author
Owner
Copy Link
Copy Source

@ajistyle commented on GitHub (Feb 19, 2025):

error：

docker logs -f docker-api-1

2025-02-19 08:57:57.258 INFO [Dummy-363] [_client.py:1038] - HTTP Request: GET http://10.1.21.28:8001/logo/logo-site.png "HTTP/1.1 200 OK"
2025-02-19 08:57:58.422 WARNING [Dummy-364] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 1: Request URL is missing an 'http://' or 'https://' protocol.
2025-02-19 08:57:59.056 WARNING [Dummy-364] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 2: Request URL is missing an 'http://' or 'https://' protocol.
2025-02-19 08:58:00.174 WARNING [Dummy-364] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 3: Request URL is missing an 'http://' or 'https://' protocol.
2025-02-19 08:58:02.299 WARNING [Dummy-364] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 4: Request URL is missing an 'http://' or 'https://' protocol.
2025-02-19 09:00:13.528 WARNING [Dummy-365] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 1: Request URL is missing an 'http://' or 'https://' protocol.
2025-02-19 09:00:14.238 WARNING [Dummy-365] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 2: Request URL is missing an 'http://' or 'https://' protocol.
2025-02-19 09:00:15.361 WARNING [Dummy-365] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 3: Request URL is missing an 'http://' or 'https://' protocol.
2025-02-19 09:00:17.495 WARNING [Dummy-365] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 4: Request URL is missing an 'http://' or 'https://' protocol.
@ajistyle commented on GitHub (Feb 19, 2025): error： docker logs -f docker-api-1 ``` 2025-02-19 08:57:57.258 INFO [Dummy-363] [_client.py:1038] - HTTP Request: GET http://10.1.21.28:8001/logo/logo-site.png "HTTP/1.1 200 OK" 2025-02-19 08:57:58.422 WARNING [Dummy-364] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 1: Request URL is missing an 'http://' or 'https://' protocol. 2025-02-19 08:57:59.056 WARNING [Dummy-364] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 2: Request URL is missing an 'http://' or 'https://' protocol. 2025-02-19 08:58:00.174 WARNING [Dummy-364] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 3: Request URL is missing an 'http://' or 'https://' protocol. 2025-02-19 08:58:02.299 WARNING [Dummy-364] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 4: Request URL is missing an 'http://' or 'https://' protocol. 2025-02-19 09:00:13.528 WARNING [Dummy-365] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 1: Request URL is missing an 'http://' or 'https://' protocol. 2025-02-19 09:00:14.238 WARNING [Dummy-365] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 2: Request URL is missing an 'http://' or 'https://' protocol. 2025-02-19 09:00:15.361 WARNING [Dummy-365] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 3: Request URL is missing an 'http://' or 'https://' protocol. 2025-02-19 09:00:17.495 WARNING [Dummy-365] [ssrf_proxy.py:62] - Request to URL /files/5bc85243-d68d-488e-90ba-c7ce743932f2/file-preview?timestamp=1739955477&nonce=787383f0342242c42af7b6d8cc3acfc4&sign=sjzx_H6etiKq_YTTdk6MP9jGFLxX4qRFRtRlDoA1L2A= failed on attempt 4: Request URL is missing an 'http://' or 'https://' protocol. ```
yindo commented 2026-02-21 18:25:37 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 19, 2025):

You can not get the image url in downstream node.

@crazywoola commented on GitHub (Feb 19, 2025): You can not get the image url in downstream node.
yindo commented 2026-02-21 18:25:37 -05:00
Author
Owner
Copy Link
Copy Source

@ajistyle commented on GitHub (Feb 19, 2025):

You can not get the image url in downstream node.

yes what should i do?

@ajistyle commented on GitHub (Feb 19, 2025): > You can not get the image url in downstream node. yes what should i do?
yindo commented 2026-02-21 18:25:37 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 19, 2025):

Nothing, we doesn't support this feature.

@crazywoola commented on GitHub (Feb 19, 2025): Nothing, we doesn't support this feature.
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 🤔 cant-reproduce
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#8421
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?