langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Failed to delete app: Failed to fetch #12002

New Issue
Closed
opened 2026-02-21 19:05:13 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 19:05:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @asdfghj2270 on GitHub (Mar 23, 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

1.1.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

Image

Failed to delete app: Failed to fetch

✔️ Expected Behavior

When I tried to delete the application and the knowledge base, the system prompted, "Failed to delete app: Failed to fetch".

❌ Actual Behavior

I want to delete the application and the knowledge base.

Originally created by @asdfghj2270 on GitHub (Mar 23, 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 1.1.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/dddd48f0-5324-4238-a5fa-bc5a19494bfa) ![Image](https://github.com/user-attachments/assets/73532921-89b2-47cd-9a82-e3e2ab9a4a2c) ![Image](https://github.com/user-attachments/assets/0930a652-52da-4986-867b-d7d53ae63df1) Failed to delete app: Failed to fetch ### ✔️ Expected Behavior When I tried to delete the application and the knowledge base, the system prompted, "Failed to delete app: Failed to fetch". ### ❌ Actual Behavior I want to delete the application and the knowledge base.
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 19:05:13 -05:00
yindo closed this issue 2026-02-21 19:05:13 -05:00
yindo commented 2026-02-21 19:05:13 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 23, 2025):

Hey @asdfghj2270! I'm here to help you with any bugs, questions, or contributions. Let's get to the bottom of this together!

I found a similar unsolved discussion titled Failed to delete app on self-hosted environment which might be relevant to your issue [1]. Additionally, there was a closed issue where re-deploying Dify on another server resolved the problem [2].

The 'Failed to fetch' error when attempting to delete an app in Dify can be caused by network or server conditions where DELETE requests do not reach the backend server, resulting in 'ERR_CONNECTION_RESET' errors. This might be due to server misconfiguration, network firewall settings, or other network-related problems. Misconfigured proxy settings in the squid.conf file could also lead to such errors. Ensuring that the proxy settings allow the necessary network traffic and checking for any misconfigurations in the Nginx setup can help resolve these issues [2].

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Mar 23, 2025): <!-- Greeting --> Hey @asdfghj2270! I'm here to help you with any bugs, questions, or contributions. Let's get to the bottom of this together! <!-- Answer --> I found a similar unsolved discussion titled [Failed to delete app on self-hosted environment](https://github.com/langgenius/dify/discussions/14407) which might be relevant to your issue <sup>[[1]](https://github.com/langgenius/dify/discussions/14407)</sup>. Additionally, there was a closed issue where re-deploying Dify on another server resolved the problem <sup>[[2]](https://github.com/langgenius/dify/issues/13507)</sup>. The 'Failed to fetch' error when attempting to delete an app in Dify can be caused by network or server conditions where DELETE requests do not reach the backend server, resulting in 'ERR_CONNECTION_RESET' errors. This might be due to server misconfiguration, network firewall settings, or other network-related problems. Misconfigured proxy settings in the `squid.conf` file could also lead to such errors. Ensuring that the proxy settings allow the necessary network traffic and checking for any misconfigurations in the Nginx setup can help resolve these issues <sup>[[2]](https://github.com/langgenius/dify/issues/13507)</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/de0ad61a-432e-4ade-9e68-b0322319f6b9?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/de0ad61a-432e-4ade-9e68-b0322319f6b9?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/de0ad61a-432e-4ade-9e68-b0322319f6b9?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/de0ad61a-432e-4ade-9e68-b0322319f6b9?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/de0ad61a-432e-4ade-9e68-b0322319f6b9?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/de0ad61a-432e-4ade-9e68-b0322319f6b9?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/de0ad61a-432e-4ade-9e68-b0322319f6b9?feedback_type=other)</sup>
yindo commented 2026-02-21 19:05:13 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 24, 2025):

Please provide the logs of the api and worker container.

@crazywoola commented on GitHub (Mar 24, 2025): Please provide the logs of the api and worker container.
yindo commented 2026-02-21 19:05:13 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 24, 2025):

https://github.com/langgenius/dify/blob/41dff175b3f9a98c5bf795315b5937de074a41ed/CONTRIBUTING.md#L23-L33

@crazywoola commented on GitHub (Mar 24, 2025): https://github.com/langgenius/dify/blob/41dff175b3f9a98c5bf795315b5937de074a41ed/CONTRIBUTING.md#L23-L33
yindo commented 2026-02-21 19:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@ServiceTail commented on GitHub (Mar 28, 2025):

I also encountered this issue. Moreover, I didn't see the request reaching Nginx. After deploying the service on the server, I can create files and apps when accessing it from my local machine, but I cannot delete them.

@ServiceTail commented on GitHub (Mar 28, 2025): I also encountered this issue. Moreover, I didn't see the request reaching Nginx. After deploying the service on the server, I can create files and apps when accessing it from my local machine, but I cannot delete them.
yindo commented 2026-02-21 19:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@jlau-ice commented on GitHub (Jul 1, 2025):

This should be a firewall policy issue, where the firewall is blocking DELETE and PUT requests.
https://bbs.sangfor.com.cn/forum.php?mod=viewthread&tid=275637

After Sangfor AF Standard Version 7.2, when method filtering is enabled, methods such as PUT, DELETE, TRACE, TRACK, DEBUG, COPY, MOVE, etc., are blocked by default. That is, checking the policy box indicates rejection. Before Sangfor AF Standard Version 7.2, when method filtering was enabled, GET, POST, HEAD, OPTIONS, etc., were allowed by default, meaning checking the policy box indicated allowance.

① Operation path example for Standard Version AF 7.0 and earlier: Can be viewed and modified under [Server Protection] - [WEB Application Protection] in the corresponding policy's [HTTP Anomaly Detection] - [Method Filtering].
② Operation path example for Standard Version AF 7.3: After checking [HTTP Anomaly Detection] in the corresponding policy under [Server Protection] - [WEB Application Protection], view and modify it under [Advanced Configuration] - [HTTP Anomaly Detection] - [Method Filtering].
③ Operation path example for Standard Version AF 7.4: After checking [HTTP Anomaly Detection] in the corresponding template under [Object] - [Security Policy Template] - [WEB Application Protection], view and modify it under [Advanced Configuration] - [HTTP Anomaly Detection] - [Method Filtering].

@jlau-ice commented on GitHub (Jul 1, 2025): This should be a firewall policy issue, where the firewall is blocking DELETE and PUT requests. https://bbs.sangfor.com.cn/forum.php?mod=viewthread&tid=275637 After Sangfor AF Standard Version 7.2, when method filtering is enabled, methods such as PUT, DELETE, TRACE, TRACK, DEBUG, COPY, MOVE, etc., are blocked by default. That is, checking the policy box indicates rejection. Before Sangfor AF Standard Version 7.2, when method filtering was enabled, GET, POST, HEAD, OPTIONS, etc., were allowed by default, meaning checking the policy box indicated allowance. ① Operation path example for Standard Version AF 7.0 and earlier: Can be viewed and modified under [Server Protection] - [WEB Application Protection] in the corresponding policy's [HTTP Anomaly Detection] - [Method Filtering]. ② Operation path example for Standard Version AF 7.3: After checking [HTTP Anomaly Detection] in the corresponding policy under [Server Protection] - [WEB Application Protection], view and modify it under [Advanced Configuration] - [HTTP Anomaly Detection] - [Method Filtering]. ③ Operation path example for Standard Version AF 7.4: After checking [HTTP Anomaly Detection] in the corresponding template under [Object] - [Security Policy Template] - [WEB Application Protection], view and modify it under [Advanced Configuration] - [HTTP Anomaly Detection] - [Method Filtering].
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 🤔 cant-reproduce
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#12002
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?