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

Upload file failed #21939

New Issue
Closed
opened 2026-02-21 20:14:56 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:14:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @Clubiy on GitHub (Jan 27, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.11.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

There was an error while uploading the file during the conversation. Upload the file was unsuccessful. Checking the communication status of the network interface shows an internal service error. It was normal to use version 1.11.1 before, but it was faild to upload files after upgrading to 1.11.4.

Image

✔️ Expected Behavior

Upload file success.

❌ Actual Behavior

Upload file faild.

Originally created by @Clubiy on GitHub (Jan 27, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.11.4 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce There was an error while uploading the file during the conversation. Upload the file was unsuccessful. Checking the communication status of the network interface shows an internal service error. It was normal to use version 1.11.1 before, but it was faild to upload files after upgrading to 1.11.4. <img width="1165" height="679" alt="Image" src="https://github.com/user-attachments/assets/24b237e5-7097-4ddd-acc4-4c7f77a3f15f" /> ### ✔️ Expected Behavior Upload file success. ### ❌ Actual Behavior Upload file faild.
yindo added the 🐞 bug label 2026-02-21 20:14:56 -05:00
yindo closed this issue 2026-02-21 20:14:56 -05:00
yindo commented 2026-02-21 20:14:56 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 27, 2026):

This is a known issue in Dify 1.11.4 Docker setups, usually caused by stricter backend checks and storage permission requirements introduced after 1.11.1. The most common causes are:

  • The storage directory (typically ./volumes/app/storage) is not writable by the Docker container user (UID 1001). Fix this by running:

    sudo chown -R 1001:1001 ./volumes/app/storage

    (or sudo chmod -R 777 ./volumes/app/storage on Mac/local dev), then restart your Docker containers. This resolves PermissionDenied (os error 13) errors that result in HTTP 500s during upload [details & fix].

  • Misconfigured environment variables: In your .env, set FILES_URL and (if present) INTERNAL_FILES_URL to http://api:5001 for Docker Compose. Also, make sure port 5001 is exposed in your docker-compose.yaml for the API service:

    ports:
  - "5001:5001"

    [config checklist]

  • File size or extension limits: Check UPLOAD_FILE_SIZE_LIMIT, NGINX_CLIENT_MAX_BODY_SIZE, and UPLOAD_FILE_EXTENSION_BLACKLIST in your .env. Make sure your file type and size are allowed [reference].

After making any changes, restart your Docker containers for the new settings to take effect.

If uploads still fail, check the API container logs for errors like PermissionDenied or storage-related exceptions. Sharing those log excerpts will help pinpoint the root cause. You can also try uploading a different file type or a smaller file to rule out extension or size-specific issues.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 27, 2026): <!-- Answer --> This is a known issue in Dify 1.11.4 Docker setups, usually caused by stricter backend checks and storage permission requirements introduced after 1.11.1. The most common causes are: - The storage directory (typically `./volumes/app/storage`) is not writable by the Docker container user (UID 1001). Fix this by running: ```sh sudo chown -R 1001:1001 ./volumes/app/storage ``` (or `sudo chmod -R 777 ./volumes/app/storage` on Mac/local dev), then restart your Docker containers. This resolves PermissionDenied (os error 13) errors that result in HTTP 500s during upload [[details & fix](https://github.com/langgenius/dify/issues/29352)]. - Misconfigured environment variables: In your `.env`, set `FILES_URL` and (if present) `INTERNAL_FILES_URL` to `http://api:5001` for Docker Compose. Also, make sure port 5001 is exposed in your `docker-compose.yaml` for the API service: ```yaml ports: - "5001:5001" ``` [[config checklist](https://github.com/langgenius/dify/issues/29071)] - File size or extension limits: Check `UPLOAD_FILE_SIZE_LIMIT`, `NGINX_CLIENT_MAX_BODY_SIZE`, and `UPLOAD_FILE_EXTENSION_BLACKLIST` in your `.env`. Make sure your file type and size are allowed [[reference](https://github.com/langgenius/dify/issues/19276)]. After making any changes, restart your Docker containers for the new settings to take effect. If uploads still fail, check the API container logs for errors like `PermissionDenied` or storage-related exceptions. Sharing those log excerpts will help pinpoint the root cause. You can also try uploading a different file type or a smaller file to rule out extension or size-specific issues. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/1b27dbf1-0e05-44e3-bd16-29693f8e570d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1b27dbf1-0e05-44e3-bd16-29693f8e570d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1b27dbf1-0e05-44e3-bd16-29693f8e570d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1b27dbf1-0e05-44e3-bd16-29693f8e570d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1b27dbf1-0e05-44e3-bd16-29693f8e570d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1b27dbf1-0e05-44e3-bd16-29693f8e570d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1b27dbf1-0e05-44e3-bd16-29693f8e570d?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20in%20Dify%201.11.4%20Docker%20setups%2C%20usually%20caused%20by%20stricter%20backend%20checks%20and%20storage%20permission%20requirements%20introduced%20after%201.11.1.%20The%20most%20common%20causes%20are%3A%0A%0A-%20The%20storage%20directory%20%28typically%20%60./volumes/app/storage%60%29%20is%20not%20writable%20by%20the%20Docker%20container%20user%20%28UID%201001%29.%20Fix%20this%20by%20running%3A%0A%20%20%60%60%60sh%0A%20%20sudo%20chown%20-R%201001%3A1001%20./volumes/app/storage%0A%20%20%60%60%60%0A%20%20%28or%20%60sudo%20chmod%20-R%20777%20./volumes/app/storage%60%20on%20Mac/local%20dev%29%2C%20then%20restart%20your%20Docker%20containers.%20This%20resolves%20PermissionDenied%20%28os%20error%2013%29%20errors%20that%20result%20in%20HTTP%20500s%20during%20upload%20%5B%5Bdetails%20%26%20fix%5D%28https%3A//github.com/langgenius/dify/issues/29352%29%5D.%0A%0A-%20Misconfigured%20environment%20variables%3A%20In%20your%20%60.env%60%2C%20set%20%60FILES_URL%60%20and%20%28if%20present%29%20%60INTERNAL_FILES_URL%60%20to%20%60http%3A//api%3A5001%60%20for%20Docker%20Compose.%20Also%2C%20make%20sure%20port%205001%20is%20exposed%20in%20your%20%60docker-compose.yaml%60%20for%20the%20API%20service%3A%0A%20%20%60%60%60yaml%0A%20%20ports%3A%0A%20%20%20%20-%20%225001%3A5001%22%0A%20%20%60%60%60%0A%20%20%5B%5Bconfig%20checklist%5D%28https%3A//github.com/langgenius/dify/issues/29071%29%5D%0A%0A-%20File%20size%20or%20extension%20limits%3A%20Check%20%60UPLOAD_FILE_SIZE_LIMIT%60%2C%20%60NGINX_CLIENT_MAX_BODY_SIZE%60%2C%20and%20%60UPLOAD_FILE_EXTENSION_BLACKLIST%60%20in%20your%20%60.env%60.%20Make%20sure%20your%20file%20type%20and%20size%20are%20allowed%20%5B%5Breference%5D%28https%3A//github.com/langgenius/dify/issues/19276%29%5D.%0A%0AAfter%20making%20any%20changes%2C%20restart%20your%20Docker%20containers%20for%20the%20new%20settings%20to%20take%20effect.%0A%0AIf%20uploads%20still%20fail%2C%20check%20the%20API%20container%20logs%20for%20errors%20like%20%60PermissionDenied%60%20or%20storage-related%20exceptions.%20Sharing%20those%20log%20excerpts%20will%20help%20pinpoint%20the%20root%20cause.%20You%20can%20also%20try%20uploading%20a%20different%20file%20type%20or%20a%20smaller%20file%20to%20rule%20out%20extension%20or%20size-specific%20issues.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31623)
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 🐞 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#21939
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?