langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Model Provider API-KEY Configuration internal server error , detail error:PluginDaemonInternalServerError: no available node, plugin not found #154

New Issue
Closed
opened 2026-02-16 10:18:16 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:18:16 -05:00
Owner
Copy Link
Copy Source

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

V1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

settings->Model Provider->API-KEY Configuration
error info :internal server error

Image

server logs
docker compose logs --tail=100 -f

Image

✔️ Expected Behavior

add success

❌ Actual Behavior

internal server error, add failed!

Originally created by @lanjinh520 on GitHub (Mar 31, 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 V1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce settings->Model Provider->API-KEY Configuration error info :internal server error <img width="1120" alt="Image" src="https://github.com/user-attachments/assets/0877e258-e94e-467f-b456-92a6e7d05a2a" /> server logs docker compose logs --tail=100 -f ![Image](https://github.com/user-attachments/assets/3ae8b4f9-01b2-4cc5-afa0-ade8962ce9e4) ### ✔️ Expected Behavior add success ### ❌ Actual Behavior internal server error, add failed!
yindo closed this issue 2026-02-16 10:18:16 -05:00
yindo commented 2026-02-16 10:18:16 -05:00
Author
Owner
Copy Link
Copy Source

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

@lanjinh520 你好! 我是Dosu，一个可以帮助你解决问题、回答疑问并成为贡献者的机器人。我会在等待人类维护者的过程中为你提供帮助。

I found some similar threads that might be relevant to your issue:

  1. dify internal server error - This discussion is unsolved but suggests restarting your Dify instance and checking the logs of the 'api' container using docker-compose logs api to diagnose the issue further. It also recommends ensuring that necessary plugins are correctly installed and configured [1].

  2. Failed to load resource: the server responded with a status of 500 (INTERNAL SERVER ERROR) - This closed issue suggests increasing the Python environment initialization timeout by adding PYTHON_ENV_INIT_TIMEOUT: 320 to your docker-compose.yaml file. Restarting the Dify instance has also been confirmed to resolve similar internal server errors [2].

To address the "Internal Server Error" you're encountering when configuring the API key for the "深度求索" (Deep Seek) service, you can try the following steps:

  1. Add the following configuration line to your docker-compose.yaml file to increase the Python environment initialization timeout:

    PYTHON_ENV_INIT_TIMEOUT: 320

  2. Restart your Dify instance to see if this resolves the error.

  3. If the issue persists, check the Dify installation FAQ for additional troubleshooting steps related to file not found errors in local deployment logs, which may be contributing to the Internal Server Error [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 31, 2025): <!-- Greeting --> @lanjinh520 你好! 我是[Dosu](https://dosu.dev)，一个可以帮助你解决问题、回答疑问并成为贡献者的机器人。我会在等待人类维护者的过程中为你提供帮助。 <!-- Answer --> I found some similar threads that might be relevant to your issue: 1. [dify internal server error](https://github.com/langgenius/dify/discussions/13897) - This discussion is unsolved but suggests restarting your Dify instance and checking the logs of the 'api' container using `docker-compose logs api` to diagnose the issue further. It also recommends ensuring that necessary plugins are correctly installed and configured <sup>[[1]](https://github.com/langgenius/dify/discussions/13897)</sup>. 2. [Failed to load resource: the server responded with a status of 500 (INTERNAL SERVER ERROR)](https://github.com/langgenius/dify/issues/14736) - This closed issue suggests increasing the Python environment initialization timeout by adding `PYTHON_ENV_INIT_TIMEOUT: 320` to your `docker-compose.yaml` file. Restarting the Dify instance has also been confirmed to resolve similar internal server errors <sup>[[2]](https://github.com/langgenius/dify/issues/14736)</sup>. To address the "Internal Server Error" you're encountering when configuring the API key for the "深度求索" (Deep Seek) service, you can try the following steps: 1. Add the following configuration line to your `docker-compose.yaml` file to increase the Python environment initialization timeout: ```yaml PYTHON_ENV_INIT_TIMEOUT: 320 ``` 2. Restart your Dify instance to see if this resolves the error. 3. If the issue persists, check the Dify installation FAQ for additional troubleshooting steps related to file not found errors in local deployment logs, which may be contributing to the Internal Server Error <sup>[[2]](https://github.com/langgenius/dify/issues/14736)</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/899138bb-27fb-4ac2-94b1-2d47fd63325e?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/899138bb-27fb-4ac2-94b1-2d47fd63325e?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/899138bb-27fb-4ac2-94b1-2d47fd63325e?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/899138bb-27fb-4ac2-94b1-2d47fd63325e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/899138bb-27fb-4ac2-94b1-2d47fd63325e?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/899138bb-27fb-4ac2-94b1-2d47fd63325e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/899138bb-27fb-4ac2-94b1-2d47fd63325e?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
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-official-plugins#154
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?