Closed SIN1109 closed 4 weeks ago
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:
STORAGE_TYPE
to s3
.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.
Self Checks
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"