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

i cant get the URL and remote_url of the upload file #11938

New Issue
Closed
opened 2026-02-21 19:04:51 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:04:51 -05:00
Owner
Copy Link
Copy Source

Originally created by @chengeyouyou on GitHub (Mar 21, 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

1.1.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I have set the storage method to s3, which is a minIo service deployed locally through Docker. But when I upload the file at the start node in the workflow and view the JSON output of the start node, where the URL is“ http://10.1.11.103:9000/files/854fa2ca -0dcf-46cd-9f34-f94a7103e4a7/file-preview? timestamp=1742542823&nonce=1f9594510eb8b6f3f7a8324372263d91&sign=xZyzvZjwFAYZk0Ooep-Wit8OrUlgSCN-uqdGmPwQ22U="， It is not the document address of S3, and the remote_url is empty, so it cannot be obtained. I can see this document in S3

json output of start node : { "file": { "dify_model_identity": "__dify__file__", "id": null, "tenant_id": "f7800d40-e780-4050-9d88-9b80f8d3ca39", "type": "document", "transfer_method": "local_file", "remote_url": "", "related_id": "854fa2ca-0dcf-46cd-9f34-f94a7103e4a7", "filename": "xxxxxxxxxxxxxxxxxxxxxxxxxx.docx", "extension": ".docx", "mime_type": "application/vnd.openxmlformats-officedocument.wordprocessingml.document", "size": 238053, "url": "http://10.1.11.103:9000/files/854fa2ca-0dcf-46cd-9f34-f94a7103e4a7/file-preview?timestamp=1742542823&nonce=1f9594510eb8b6f3f7a8324372263d91&sign=xZyzvZjwFAYZk0Ooep-Wit8OrUlgSCN-uqdGmPwQ22U=" }, "sys.files": [], "sys.user_id": "2c236752-4600-4eaf-b830-839a63e8599e", "sys.app_id": "25426c1d-eab9-4757-862d-f10624ba530b", "sys.workflow_id": "02ddebe2-f631-4580-a512-658f0547d6cc", "sys.workflow_run_id": "a7badcd6-1893-412a-8d5b-c11736cbc852" }

Image

✔️ Expected Behavior

The URL corresponds correctly to the document address of S3, which can be obtained by obtaining the remote_url or URL

❌ Actual Behavior

No response

Originally created by @chengeyouyou on GitHub (Mar 21, 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 1.1.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I have set the storage method to s3, which is a minIo service deployed locally through Docker. But when I upload the file at the start node in the workflow and view the JSON output of the start node, where the URL is“ http://10.1.11.103:9000/files/854fa2ca -0dcf-46cd-9f34-f94a7103e4a7/file-preview? timestamp=1742542823&nonce=1f9594510eb8b6f3f7a8324372263d91&sign=xZyzvZjwFAYZk0Ooep-Wit8OrUlgSCN-uqdGmPwQ22U="， It is not the document address of S3, and the remote_url is empty, so it cannot be obtained. I can see this document in S3 `json output of start node : { "file": { "dify_model_identity": "__dify__file__", "id": null, "tenant_id": "f7800d40-e780-4050-9d88-9b80f8d3ca39", "type": "document", "transfer_method": "local_file", "remote_url": "", "related_id": "854fa2ca-0dcf-46cd-9f34-f94a7103e4a7", "filename": "xxxxxxxxxxxxxxxxxxxxxxxxxx.docx", "extension": ".docx", "mime_type": "application/vnd.openxmlformats-officedocument.wordprocessingml.document", "size": 238053, "url": "http://10.1.11.103:9000/files/854fa2ca-0dcf-46cd-9f34-f94a7103e4a7/file-preview?timestamp=1742542823&nonce=1f9594510eb8b6f3f7a8324372263d91&sign=xZyzvZjwFAYZk0Ooep-Wit8OrUlgSCN-uqdGmPwQ22U=" }, "sys.files": [], "sys.user_id": "2c236752-4600-4eaf-b830-839a63e8599e", "sys.app_id": "25426c1d-eab9-4757-862d-f10624ba530b", "sys.workflow_id": "02ddebe2-f631-4580-a512-658f0547d6cc", "sys.workflow_run_id": "a7badcd6-1893-412a-8d5b-c11736cbc852" }` ![Image](https://github.com/user-attachments/assets/1b0a2e4e-50f4-4591-8b7f-46d654fdd471) ### ✔️ Expected Behavior The URL corresponds correctly to the document address of S3, which can be obtained by obtaining the remote_url or URL ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:04:51 -05:00
yindo closed this issue 2026-02-21 19:04:51 -05:00
yindo commented 2026-02-21 19:04:51 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 21, 2025):

Hey there, @chengeyouyou! 👋 I'm here to help you with bug fixes, questions, and becoming a contributor.

I found some relevant discussions and issues that might help address your problem with the remote_url being empty and the URL not corresponding to the S3 document address:

  1. File URL as returned in dify workflow does not match the file location in s3 (self hosted instance): This discussion highlights a similar issue where the file URL in the Dify workflow does not match the file location in S3. It might provide insights into the discrepancies you're experiencing [1].

  2. How to access file URLs in Dify workflow iterator?: This issue discusses a known problem where file URLs are not accessible in certain workflow scenarios. It suggests modifying the file_manager.py file to ensure the correct URL is returned [2].

  3. How to obtain file URL in Dify workflow?: This issue explains that the remote_url is populated when using the FileTransferMethod.REMOTE_URL. Ensure that your configuration aligns with this method to correctly generate and retrieve the remote_url [3].

To resolve your issue, verify that your configuration is set to use the correct transfer_method and ensure that the URL generation logic in your Dify setup is correctly implemented. If the problem persists, consider checking the code modifications suggested in the issues above.

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 (Mar 21, 2025): <!-- Greeting --> Hey there, @chengeyouyou! 👋 I'm here to help you with bug fixes, questions, and becoming a contributor. <!-- Answer --> I found some relevant discussions and issues that might help address your problem with the `remote_url` being empty and the URL not corresponding to the S3 document address: 1. **[File URL as returned in dify workflow does not match the file location in s3 (self hosted instance)](https://github.com/langgenius/dify/discussions/6729)**: This discussion highlights a similar issue where the file URL in the Dify workflow does not match the file location in S3. It might provide insights into the discrepancies you're experiencing <sup>[[1]](https://github.com/langgenius/dify/discussions/6729)</sup>. 2. **[How to access file URLs in Dify workflow iterator?](https://github.com/langgenius/dify/issues/15587)**: This issue discusses a known problem where file URLs are not accessible in certain workflow scenarios. It suggests modifying the `file_manager.py` file to ensure the correct URL is returned <sup>[[2]](https://github.com/langgenius/dify/issues/15587)</sup>. 3. **[How to obtain file URL in Dify workflow?](https://github.com/langgenius/dify/issues/11769)**: This issue explains that the `remote_url` is populated when using the `FileTransferMethod.REMOTE_URL`. Ensure that your configuration aligns with this method to correctly generate and retrieve the `remote_url` <sup>[[3]](https://github.com/langgenius/dify/issues/11769)</sup>. To resolve your issue, verify that your configuration is set to use the correct `transfer_method` and ensure that the URL generation logic in your Dify setup is correctly implemented. If the problem persists, consider checking the code modifications suggested in the issues above. <!-- 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/1a739804-86e8-4ef5-85d6-68dc2eebbcdf?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/1a739804-86e8-4ef5-85d6-68dc2eebbcdf?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/1a739804-86e8-4ef5-85d6-68dc2eebbcdf?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/1a739804-86e8-4ef5-85d6-68dc2eebbcdf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1a739804-86e8-4ef5-85d6-68dc2eebbcdf?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/1a739804-86e8-4ef5-85d6-68dc2eebbcdf?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1a739804-86e8-4ef5-85d6-68dc2eebbcdf?feedback_type=other)</sup>
yindo commented 2026-02-21 19:04:51 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 21, 2025):

https://github.com/langgenius/dify/issues/14679#issuecomment-2692741739

@crazywoola commented on GitHub (Mar 21, 2025): https://github.com/langgenius/dify/issues/14679#issuecomment-2692741739
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 🐞 bug
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#11938
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?