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

Video upload to S3 but can't get url as input #7095

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

Originally created by @JimmySunCreater on GitHub (Dec 6, 2024).

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

0.13.1

Cloud or Self Hosted

Cloud

Steps to reproduce

screenshot-20241206-185838
screenshot-20241206-185735
I have upload the video data successfully and have url in the output, but I can't get it from input which is start.videodata.url, I think it's a bug.

✔️ Expected Behavior

I can get it from input which is start.videodata.url.

❌ Actual Behavior

I can't get it from input which is start.videodata.url, I think it's a bug.

Originally created by @JimmySunCreater on GitHub (Dec 6, 2024). ### 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 0.13.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce ![screenshot-20241206-185838](https://github.com/user-attachments/assets/4b169d8f-8366-4e0c-9a16-37e11151994b) ![screenshot-20241206-185735](https://github.com/user-attachments/assets/a543defe-b6b2-4047-b6d3-b65ec200a1bb) I have upload the video data successfully and have url in the output, but I can't get it from input which is start.videodata.url, I think it's a bug. ### ✔️ Expected Behavior I can get it from input which is start.videodata.url. ### ❌ Actual Behavior I can't get it from input which is start.videodata.url, I think it's a bug.
yindo added the 🐞 bugcloud labels 2026-02-21 18:18:53 -05:00
yindo closed this issue 2026-02-21 18:18:53 -05:00
yindo commented 2026-02-21 18:18:53 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 6, 2024):

Hey @JimmySunCreater! 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!

I found a similar unsolved discussion that might be relevant to your issue: Should we allow access to the signed URL in the workflow? [1]. This discussion might provide insights or potential solutions related to accessing URLs in Dify workflows.

Regarding your issue, ensure that the signature in the URL is correctly generated and verified. The verify_file_signature function checks if the signature matches the expected value. If the signature does not match, access will be denied. Also, check that the upload_file_id, timestamp, nonce, and sign parameters are correctly passed and calculated. Additionally, verify that the timestamp is within the allowed timeout period defined by dify_config.FILES_ACCESS_TIMEOUT [2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Dec 6, 2024): <!-- Greeting --> Hey @JimmySunCreater! 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! <!-- Answer --> I found a similar unsolved discussion that might be relevant to your issue: [Should we allow access to the signed URL in the workflow?](https://github.com/langgenius/dify/discussions/10687) <sup>[[1]](https://github.com/langgenius/dify/discussions/10687)</sup>. This discussion might provide insights or potential solutions related to accessing URLs in Dify workflows. Regarding your issue, ensure that the signature in the URL is correctly generated and verified. The `verify_file_signature` function checks if the signature matches the expected value. If the signature does not match, access will be denied. Also, check that the `upload_file_id`, `timestamp`, `nonce`, and `sign` parameters are correctly passed and calculated. Additionally, verify that the timestamp is within the allowed timeout period defined by `dify_config.FILES_ACCESS_TIMEOUT` <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/file/helpers.py)</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/b347a145-807a-46eb-8562-994077c64577?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b347a145-807a-46eb-8562-994077c64577?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b347a145-807a-46eb-8562-994077c64577?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b347a145-807a-46eb-8562-994077c64577?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b347a145-807a-46eb-8562-994077c64577?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/b347a145-807a-46eb-8562-994077c64577?feedback_type=other)</sup>
yindo commented 2026-02-21 18:18:54 -05:00
Author
Owner
Copy Link
Copy Source

@JimmySunCreater commented on GitHub (Dec 6, 2024):

Attach 1 more picture
screenshot-20241206-190346

@JimmySunCreater commented on GitHub (Dec 6, 2024): Attach 1 more picture ![screenshot-20241206-190346](https://github.com/user-attachments/assets/0ee38569-13be-4522-a618-059fa42b1d4d)
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 cloud 🐞 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#7095
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?