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

The chat window uploads attachments and sends information to the LLM #8236

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

Originally created by @zhuojiuya on GitHub (Feb 13, 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

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The chat window sticks uploaded pictures
Image

This was uploaded via the attachment feature

Image

Image

At present, the project has been deployed to the public network server, and the same problem will occur when calling the API of the application

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @zhuojiuya on GitHub (Feb 13, 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 0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The chat window sticks uploaded pictures ![Image](https://github.com/user-attachments/assets/a95452ce-bdde-4afd-81d7-4e079ec1bb55) This was uploaded via the attachment feature ![Image](https://github.com/user-attachments/assets/6c25a293-c8a6-4d0e-ae9d-348488f45740) ![Image](https://github.com/user-attachments/assets/410a4838-574b-462a-86a2-a4af7d6549b6) At present, the project has been deployed to the public network server, and the same problem will occur when calling the API of the application ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bugstale labels 2026-02-21 18:24:38 -05:00
yindo closed this issue 2026-02-21 18:24:38 -05:00
yindo commented 2026-02-21 18:24:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 13, 2025):

To resolve the issue of the chat window sticking uploaded images and encountering a 400 error due to an unsupported image format in a self-hosted Dify version 0.15.3 deployment, you can follow these steps:

  1. Supported Image Formats: Ensure your image is in one of the supported formats: JPG, JPEG, PNG, GIF, WEBP, or SVG (including uppercase variants).

  2. Configuration Settings:

    • Configure the MULTIMODAL_SEND_IMAGE_FORMAT setting to either 'base64' or 'url' in your environment settings.
    • If using the URL format, ensure FILES_URL is configured with an externally accessible address.

  3. Vision Configuration: Make sure the 'vision' configuration is declared in your YAML file. You should see an eye icon in the interface indicating that the vision capability is enabled.

  4. File Upload Feature: Enable the comprehensive "file upload" feature instead of the standalone "image upload" feature. This can be done by selecting the "file upload" option and choosing the "image" file type in the chatflow settings. This ensures better handling of various file types and improves the app experience.

Additionally, ensure that the image upload function is enabled in the 'Features' section of the application orchestration page. The standalone image upload feature has been replaced by the more comprehensive file upload feature, which supports a variety of file types, including images. Transitioning to this feature will help resolve the unsupported image format error and improve the application experience [1].

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 13, 2025): <!-- Answer --> To resolve the issue of the chat window sticking uploaded images and encountering a 400 error due to an unsupported image format in a self-hosted Dify version 0.15.3 deployment, you can follow these steps: 1. **Supported Image Formats**: Ensure your image is in one of the supported formats: JPG, JPEG, PNG, GIF, WEBP, or SVG (including uppercase variants). 2. **Configuration Settings**: - Configure the `MULTIMODAL_SEND_IMAGE_FORMAT` setting to either 'base64' or 'url' in your environment settings. - If using the URL format, ensure `FILES_URL` is configured with an externally accessible address. 3. **Vision Configuration**: Make sure the 'vision' configuration is declared in your YAML file. You should see an eye icon in the interface indicating that the vision capability is enabled. 4. **File Upload Feature**: Enable the comprehensive "file upload" feature instead of the standalone "image upload" feature. This can be done by selecting the "file upload" option and choosing the "image" file type in the chatflow settings. This ensures better handling of various file types and improves the app experience. Additionally, ensure that the image upload function is enabled in the 'Features' section of the application orchestration page. The standalone image upload feature has been replaced by the more comprehensive file upload feature, which supports a variety of file types, including images. Transitioning to this feature will help resolve the unsupported image format error and improve the application experience <sup>[[1]](https://github.com/langgenius/dify/issues/13658)</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/f21c1a37-a1fa-46e2-ac47-8ac9eba8dc0b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f21c1a37-a1fa-46e2-ac47-8ac9eba8dc0b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f21c1a37-a1fa-46e2-ac47-8ac9eba8dc0b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f21c1a37-a1fa-46e2-ac47-8ac9eba8dc0b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f21c1a37-a1fa-46e2-ac47-8ac9eba8dc0b?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/f21c1a37-a1fa-46e2-ac47-8ac9eba8dc0b?feedback_type=other) | [Bug Report](https://app.dosu.dev/response-feedback/f21c1a37-a1fa-46e2-ac47-8ac9eba8dc0b?feedback_type=bug_report)</sup>
yindo commented 2026-02-21 18:24:38 -05:00
Author
Owner
Copy Link
Copy Source

@zhuojiuya commented on GitHub (Feb 13, 2025):

@dosu
None of the methods you offer will work

@zhuojiuya commented on GitHub (Feb 13, 2025): @dosu None of the methods you offer will work
yindo commented 2026-02-21 18:24:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 13, 2025):

This is a tough nut to crack, could really use your help on this, @takatost.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 13, 2025): <!-- Answer --> This is a tough nut to crack, could really use your help on this, @takatost. <!-- 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/0d046c73-f4d2-49a9-959a-039f183dddcf?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/0d046c73-f4d2-49a9-959a-039f183dddcf?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/0d046c73-f4d2-49a9-959a-039f183dddcf?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/0d046c73-f4d2-49a9-959a-039f183dddcf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0d046c73-f4d2-49a9-959a-039f183dddcf?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/0d046c73-f4d2-49a9-959a-039f183dddcf?feedback_type=other) | [Bug Report](https://app.dosu.dev/response-feedback/0d046c73-f4d2-49a9-959a-039f183dddcf?feedback_type=bug_report)</sup>
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 stale 🐞 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#8236
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?