"File validation failed for file" error occurs when "Upload File Types" is "URL"

[fujita-h]

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.12.1

Cloud or Self Hosted

Cloud, Self Hosted (Source)

Steps to reproduce

1. Create new workflow
2. Open start node, add single image file input named valiable 'file' and set Upload File Type to "URL"
3. Add End node, just output file.name
4. Run flow, with url https://cloud.dify.ai/logo/logo-site.png

✔️ Expected Behavior

Complete the flow

❌ Actual Behavior

"File validation failed for file" error occurs

[fujita-h]

This problem does not occur if Upload File Type is set to "Both".

[fujita-h]

related #10845, #11028

[dosubot]

I found a similar closed issue that might be relevant to your problem: File upload variable extension validation not match the setting. This issue was resolved by a pull request that addressed a problem with file uploads, specifically for mp3 files ^[1].

For your specific issue with the "File Validation failed for file" error when using "URL" as the upload file type, consider checking the following:

1. File Type and Extension Validation: Ensure that the file type and extension are correctly configured to accept URLs. There might be a mismatch in the expected file type or extension settings.

2. Configuration Settings: Verify that your configuration settings align with the requirements for using URLs as file inputs. This includes checking any recent changes or updates in the Dify platform that might affect URL handling.

3. Logs and Error Messages: Review any logs or error messages for additional clues about why the validation is failing. This can help identify if there are specific conditions or missing configurations causing the issue.

If the problem persists, you might want to follow up on the related issue #10845 mentioned in your report for any updates or solutions that might be applicable.

To continue talking to Dosu, mention @dosu.