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 authorization settings for custom plugins cannot be saved. #12534

New Issue
Closed
opened 2026-02-21 19:07:51 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:07:51 -05:00
Owner
Copy Link
Copy Source

Originally created by @WwKk-Cc on GitHub (Apr 3, 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.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I customized a Dify plugin. During the testing phase, I could pre-authorize the plugin and complete the entire process smoothly. However, after packaging the plugin and installing it on my Dify in a local installation format, I was unable to pre-authorize the plugin. The specific situation is as follows: after clicking the "Save" button, there was a long wait, and then it failed to save.

Image

Image

✔️ Expected Behavior

The pre-authorization value can be saved normally as it was during the test.

❌ Actual Behavior

The pre-authorization value cannot be saved.

Originally created by @WwKk-Cc on GitHub (Apr 3, 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.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I customized a Dify plugin. During the testing phase, I could pre-authorize the plugin and complete the entire process smoothly. However, after packaging the plugin and installing it on my Dify in a local installation format, I was unable to pre-authorize the plugin. The specific situation is as follows: after clicking the "Save" button, there was a long wait, and then it failed to save. ![Image](https://github.com/user-attachments/assets/70ca4590-d1a3-48a1-b82f-a94ef0c8d0b3) ![Image](https://github.com/user-attachments/assets/c8cf7d56-9d5d-4fab-8aec-6955bdf64502) ### ✔️ Expected Behavior The pre-authorization value can be saved normally as it was during the test. ### ❌ Actual Behavior The pre-authorization value cannot be saved.
yindo added the 🐞 bugstale labels 2026-02-21 19:07:51 -05:00
yindo closed this issue 2026-02-21 19:07:51 -05:00
yindo commented 2026-02-21 19:07:51 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 3, 2025):

@WwKk-Cc Hello there! I'm here to help you with bug reports, questions, and becoming a contributor. I'm looking forward to assisting you with the issue you've encountered.

The issue you're experiencing with saving authorization settings for custom plugins in a self-hosted Docker environment might be related to the POST request to the "update" endpoint, which is showing a status of "NS_BINDING..." and a response size of 0 bytes. This status typically indicates that the request is stuck in the binding phase, possibly due to network issues or server configuration problems.

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

  1. Check Network Configuration: Ensure that your network settings are correctly configured and that there are no firewall rules or network policies blocking the request.

  2. Verify Server Logs: Check the server logs for any error messages or warnings that might provide more insight into why the request is not completing.

  3. Inspect Docker Setup: Make sure that your Docker setup is correctly configured, especially the network settings. Verify that the containers can communicate with each other as expected.

  4. Database Configuration: Double-check your database configuration to ensure that all settings are correct and that the database is accessible from the application.

  5. Endpoint Functionality: Review the update_endpoint function in the codebase to ensure it is functioning as expected. This function is responsible for handling the update requests [1].

If these steps do not resolve the issue, consider reviewing any recent changes to your environment or setup that might have affected the plugin's ability to save authorization settings.

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 (Apr 3, 2025): <!-- Greeting --> @WwKk-Cc Hello there! I'm here to help you with bug reports, questions, and becoming a contributor. I'm looking forward to assisting you with the issue you've encountered. <!-- Answer --> The issue you're experiencing with saving authorization settings for custom plugins in a self-hosted Docker environment might be related to the POST request to the "update" endpoint, which is showing a status of "NS_BINDING..." and a response size of 0 bytes. This status typically indicates that the request is stuck in the binding phase, possibly due to network issues or server configuration problems. Here are a few steps you can take to troubleshoot and potentially resolve the issue: 1. **Check Network Configuration**: Ensure that your network settings are correctly configured and that there are no firewall rules or network policies blocking the request. 2. **Verify Server Logs**: Check the server logs for any error messages or warnings that might provide more insight into why the request is not completing. 3. **Inspect Docker Setup**: Make sure that your Docker setup is correctly configured, especially the network settings. Verify that the containers can communicate with each other as expected. 4. **Database Configuration**: Double-check your database configuration to ensure that all settings are correct and that the database is accessible from the application. 5. **Endpoint Functionality**: Review the `update_endpoint` function in the codebase to ensure it is functioning as expected. This function is responsible for handling the update requests <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/plugin/manager/endpoint.py)</sup>. If these steps do not resolve the issue, consider reviewing any recent changes to your environment or setup that might have affected the plugin's ability to save authorization settings. <!-- 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/cf51d3f8-3d0f-4cbb-bb03-996e66534092?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/cf51d3f8-3d0f-4cbb-bb03-996e66534092?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/cf51d3f8-3d0f-4cbb-bb03-996e66534092?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/cf51d3f8-3d0f-4cbb-bb03-996e66534092?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/cf51d3f8-3d0f-4cbb-bb03-996e66534092?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/cf51d3f8-3d0f-4cbb-bb03-996e66534092?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/cf51d3f8-3d0f-4cbb-bb03-996e66534092?feedback_type=other)</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#12534
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?