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

Workflow "start" paste url not support s3 pre-signed URL #4798

New Issue
Closed
opened 2026-02-21 18:08:04 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:08:04 -05:00
Owner
Copy Link
Copy Source

Originally created by @SIN1109 on GitHub (Jul 26, 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).
  • 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.14

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Create empty workflow "Start" -> "LLM" -> "End"

Start part, use paste image link, input a presigned URL will report error

✔️ Expected Behavior

can accept the pre-signed URL

❌ Actual Behavior

Report error "URL does not exist"
image

Originally created by @SIN1109 on GitHub (Jul 26, 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] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.14 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Create empty workflow "Start" -> "LLM" -> "End" Start part, use paste image link, input a presigned URL will report error ### ✔️ Expected Behavior can accept the pre-signed URL ### ❌ Actual Behavior Report error "URL does not exist" <img width="1216" alt="image" src="https://github.com/user-attachments/assets/45366e07-c5a0-4657-bd52-9eaf284d7fae">
yindo added the 🐞 bug🌊 feat:workflow labels 2026-02-21 18:08:04 -05:00
yindo closed this issue 2026-02-21 18:08:04 -05:00
yindo commented 2026-02-21 18:08:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 26, 2024):

To resolve the issue where the "Start" workflow in Dify version 0.6.14 does not support S3 pre-signed URLs and reports "URL does not exist," ensure that the S3 storage configuration is correctly set up in your .env file. Here is the relevant section from the provided docker-compose.yaml:

# The S3 storage configurations, only available when STORAGE_TYPE is `s3`.
S3_ENDPOINT: 'https://xxx.r2.cloudflarestorage.com'
S3_BUCKET_NAME: 'difyai'
S3_ACCESS_KEY: 'ak-difyai'
S3_SECRET_KEY: 'sk-difyai'
S3_REGION: 'us-east-1'

Make sure to replace the placeholders with your actual S3 configuration details:

  1. Set STORAGE_TYPE to s3.
  2. Provide the correct S3_ENDPOINT, S3_BUCKET_NAME, S3_ACCESS_KEY, S3_SECRET_KEY, and S3_REGION.

If the issue persists, verify that the pre-signed URL is correctly generated and accessible. Ensure that the URL is not expired and that the permissions for the S3 bucket allow access to the file [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 26, 2024): <!-- Answer --> To resolve the issue where the "Start" workflow in Dify version 0.6.14 does not support S3 pre-signed URLs and reports "URL does not exist," ensure that the S3 storage configuration is correctly set up in your `.env` file. Here is the relevant section from the provided `docker-compose.yaml`: ```yaml # The S3 storage configurations, only available when STORAGE_TYPE is `s3`. S3_ENDPOINT: 'https://xxx.r2.cloudflarestorage.com' S3_BUCKET_NAME: 'difyai' S3_ACCESS_KEY: 'ak-difyai' S3_SECRET_KEY: 'sk-difyai' S3_REGION: 'us-east-1' ``` Make sure to replace the placeholders with your actual S3 configuration details: 1. Set `STORAGE_TYPE` to `s3`. 2. Provide the correct `S3_ENDPOINT`, `S3_BUCKET_NAME`, `S3_ACCESS_KEY`, `S3_SECRET_KEY`, and `S3_REGION`. If the issue persists, verify that the pre-signed URL is correctly generated and accessible. Ensure that the URL is not expired and that the permissions for the S3 bucket allow access to the file <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/.env.example)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
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 🌊 feat:workflow 🐞 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#4798
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?