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

[Errno 13] Permission denied: '/home/dify' when uploading .pptx file in Document Extractor #21253

New Issue
Closed
opened 2026-02-21 20:11:37 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 20:11:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @yongzzz on GitHub (Dec 24, 2025).

Originally assigned to: @JohnJyong on GitHub.

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

Cloud or Self Hosted

Cloud

Steps to reproduce

  1. Open Document Extractor (https://cloud.dify.ai/app/43d98610-26c2-4c80-8eff-65aa54655063/workflow)
  2. Upload a .pptx file (6,256 KB)
  3. Wait for the extraction process

✔️ Expected Behavior

The .pptx file should be uploaded and processed normally without permission errors.

❌ Actual Behavior

The process fails with a permission denied error([Errno 13] Permission denied: '/home/dify') related to the /home/dify directory.

Image
Originally created by @yongzzz on GitHub (Dec 24, 2025). Originally assigned to: @JohnJyong on GitHub. ### 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.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce 1. Open Document Extractor (https://cloud.dify.ai/app/43d98610-26c2-4c80-8eff-65aa54655063/workflow) 2. Upload a .pptx file (6,256 KB) 3. Wait for the extraction process ### ✔️ Expected Behavior The .pptx file should be uploaded and processed normally without permission errors. ### ❌ Actual Behavior The process fails with a permission denied error([Errno 13] Permission denied: '/home/dify') related to the /home/dify directory. <img width="956" height="1746" alt="Image" src="https://github.com/user-attachments/assets/3e2c651d-2eb2-4554-8110-c26373776bd5" />
yindo added the 🐞 bugcloud labels 2026-02-21 20:11:37 -05:00
yindo closed this issue 2026-02-21 20:11:37 -05:00
yindo commented 2026-02-21 20:11:37 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 24, 2025):

Hi @yongzzz! I'm Dosu and I’m helping the dify team.

The error [Errno 13] Permission denied: '/home/dify' happens because the Dify application process doesn't have write access to the storage directory (often /home/dify in cloud deployments). This is due to the containers running as a non-root user (uid:1001) for security reasons, but the storage directory may not be owned by this user, causing permission errors during file uploads and extraction.

A recent update introduced an init container that automatically fixes storage permissions by running a chown command on the storage directory before the main application starts. This ensures the directory is owned by the correct user and prevents permission denied errors. If you are still seeing this error, your deployment may not include this fix yet. In that case, manually ensure the storage directory is owned by uid:1001, or check with your cloud provider to confirm the fix is applied in your environment. More details about this change can be found in the merged pull request #29297.

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 (Dec 24, 2025): <!-- Greeting --> Hi @yongzzz! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The error `[Errno 13] Permission denied: '/home/dify'` happens because the Dify application process doesn't have write access to the storage directory (often `/home/dify` in cloud deployments). This is due to the containers running as a non-root user (uid:1001) for security reasons, but the storage directory may not be owned by this user, causing permission errors during file uploads and extraction. A recent update introduced an init container that automatically fixes storage permissions by running a `chown` command on the storage directory before the main application starts. This ensures the directory is owned by the correct user and prevents permission denied errors. If you are still seeing this error, your deployment may not include this fix yet. In that case, manually ensure the storage directory is owned by uid:1001, or check with your cloud provider to confirm the fix is applied in your environment. More details about this change can be found in the [merged pull request #29297](https://github.com/langgenius/dify/pull/29297). <!-- 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/7062a4a5-7ba5-47a8-8374-97b6f8705802?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7062a4a5-7ba5-47a8-8374-97b6f8705802?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7062a4a5-7ba5-47a8-8374-97b6f8705802?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7062a4a5-7ba5-47a8-8374-97b6f8705802?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7062a4a5-7ba5-47a8-8374-97b6f8705802?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7062a4a5-7ba5-47a8-8374-97b6f8705802?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7062a4a5-7ba5-47a8-8374-97b6f8705802?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=The%20error%20%60%5BErrno%2013%5D%20Permission%20denied%3A%20%27/home/dify%27%60%20happens%20because%20the%20Dify%20application%20process%20doesn%27t%20have%20write%20access%20to%20the%20storage%20directory%20%28often%20%60/home/dify%60%20in%20cloud%20deployments%29.%20This%20is%20due%20to%20the%20containers%20running%20as%20a%20non-root%20user%20%28uid%3A1001%29%20for%20security%20reasons%2C%20but%20the%20storage%20directory%20may%20not%20be%20owned%20by%20this%20user%2C%20causing%20permission%20errors%20during%20file%20uploads%20and%20extraction.%0A%0AA%20recent%20update%20introduced%20an%20init%20container%20that%20automatically%20fixes%20storage%20permissions%20by%20running%20a%20%60chown%60%20command%20on%20the%20storage%20directory%20before%20the%20main%20application%20starts.%20This%20ensures%20the%20directory%20is%20owned%20by%20the%20correct%20user%20and%20prevents%20permission%20denied%20errors.%20If%20you%20are%20still%20seeing%20this%20error%2C%20your%20deployment%20may%20not%20include%20this%20fix%20yet.%20In%20that%20case%2C%20manually%20ensure%20the%20storage%20directory%20is%20owned%20by%20uid%3A1001%2C%20or%20check%20with%20your%20cloud%20provider%20to%20confirm%20the%20fix%20is%20applied%20in%20your%20environment.%20More%20details%20about%20this%20change%20can%20be%20found%20in%20the%20%5Bmerged%20pull%20request%20%2329297%5D%28https%3A//github.com/langgenius/dify/pull/29297%29.)&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/30092)
yindo commented 2026-02-21 20:11:38 -05:00
Author
Owner
Copy Link
Copy Source

@yongzzz commented on GitHub (Dec 24, 2025):

@dosu

I want to clarify that I am not using a self-hosted or private deployment.
This issue occurs while using Dify’s official cloud (SaaS) platform directly via the website.

@yongzzz commented on GitHub (Dec 24, 2025): @dosu I want to clarify that I am not using a self-hosted or private deployment. This issue occurs while using Dify’s official cloud (SaaS) platform directly via the website.
yindo commented 2026-02-21 20:11:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 24, 2025):

Thanks for clarifying—this kind of permission error shouldn’t happen on the official Dify Cloud platform, since users don’t have access to or control over the backend filesystem. All documented permission errors are specific to self-hosted deployments; there are no recent reports or incidents affecting SaaS users like you.

This indicates a backend issue that only the Dify Cloud operations team can resolve. Please report this directly to Dify Cloud support (with your error details and screenshot) so they can investigate and fix the infrastructure problem on their end. If you need help summarizing the technical details for support, let me know!

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 (Dec 24, 2025): <!-- Answer --> Thanks for clarifying—this kind of permission error shouldn’t happen on the official Dify Cloud platform, since users don’t have access to or control over the backend filesystem. All documented permission errors are specific to self-hosted deployments; there are no recent reports or incidents affecting SaaS users like you. This indicates a backend issue that only the Dify Cloud operations team can resolve. Please report this directly to Dify Cloud support (with your error details and screenshot) so they can investigate and fix the infrastructure problem on their end. If you need help summarizing the technical details for support, let me know! <!-- 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/ad0b89c6-e301-4747-8a92-3c5df88a28a4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ad0b89c6-e301-4747-8a92-3c5df88a28a4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ad0b89c6-e301-4747-8a92-3c5df88a28a4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ad0b89c6-e301-4747-8a92-3c5df88a28a4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ad0b89c6-e301-4747-8a92-3c5df88a28a4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ad0b89c6-e301-4747-8a92-3c5df88a28a4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ad0b89c6-e301-4747-8a92-3c5df88a28a4?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=Thanks%20for%20clarifying%E2%80%94this%20kind%20of%20permission%20error%20shouldn%E2%80%99t%20happen%20on%20the%20official%20Dify%20Cloud%20platform%2C%20since%20users%20don%E2%80%99t%20have%20access%20to%20or%20control%20over%20the%20backend%20filesystem.%20All%20documented%20permission%20errors%20are%20specific%20to%20self-hosted%20deployments%3B%20there%20are%20no%20recent%20reports%20or%20incidents%20affecting%20SaaS%20users%20like%20you.%0A%0AThis%20indicates%20a%20backend%20issue%20that%20only%20the%20Dify%20Cloud%20operations%20team%20can%20resolve.%20Please%20report%20this%20directly%20to%20Dify%20Cloud%20support%20%28with%20your%20error%20details%20and%20screenshot%29%20so%20they%20can%20investigate%20and%20fix%20the%20infrastructure%20problem%20on%20their%20end.%20If%20you%20need%20help%20summarizing%20the%20technical%20details%20for%20support%2C%20let%20me%20know%21)&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/30092)
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 cloud 🐞 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#21253
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?