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

docker-plugin_daemon It's been rebooting #13268

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

Originally created by @mbpz on GitHub (Apr 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.2.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

docker-plugin_daemon It's been rebooting.
langgenius/dify-plugin-daemon:0.0.7-local the status is restaring.

requests.exceptions.ConnectionError: HTTPConnectionPool(host='plugin_daemon', port=5002): Max retries exceeded with url: /plugin/f6c08d9a-f50f-4152-ac4e-194545d508c7/management/install/tasks?page=1&page_size=100 (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff8326bfe0>: Failed to resolve 'plugin_daemon' ([Errno -2] Name or service not known)"))

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @mbpz on GitHub (Apr 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.2.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce docker-plugin_daemon It's been rebooting. langgenius/dify-plugin-daemon:0.0.7-local the status is restaring. requests.exceptions.ConnectionError: HTTPConnectionPool(host='plugin_daemon', port=5002): Max retries exceeded with url: /plugin/f6c08d9a-f50f-4152-ac4e-194545d508c7/management/install/tasks?page=1&page_size=100 (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff8326bfe0>: Failed to resolve 'plugin_daemon' ([Errno -2] Name or service not known)")) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 19:11:21 -05:00
yindo commented 2026-02-21 19:11:21 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 23, 2025):

docker-plugin_daemon It's been rebooting.
langgenius/dify-plugin-daemon:0.0.7-local the status is restaring.

requests.exceptions.ConnectionError: HTTPConnectionPool(host='plugin_daemon', port=5002): Max retries exceeded with url: /plugin/f6c08d9a-f50f-4152-ac4e-194545d508c7/management/install/tasks?page=1&page_size=100 (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff8326bfe0>: Failed to resolve 'plugin_daemon' ([Errno -2] Name or service not known)"))

This seems to be a general network issue to me, please turn off you proxy or switch it to tunnel mode.

Please do search existing issues for more help.

@crazywoola commented on GitHub (Apr 23, 2025): ``` docker-plugin_daemon It's been rebooting. langgenius/dify-plugin-daemon:0.0.7-local the status is restaring. requests.exceptions.ConnectionError: HTTPConnectionPool(host='plugin_daemon', port=5002): Max retries exceeded with url: /plugin/f6c08d9a-f50f-4152-ac4e-194545d508c7/management/install/tasks?page=1&page_size=100 (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0xffff8326bfe0>: Failed to resolve 'plugin_daemon' ([Errno -2] Name or service not known)")) ``` This seems to be a general network issue to me, please turn off you proxy or switch it to tunnel mode. Please do search existing issues for more help.
yindo commented 2026-02-21 19:11:21 -05:00
Author
Owner
Copy Link
Copy Source

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

I found a similar issue that was reported and closed: Failed to start the docker-plugin_daemon-1 repeatedly. This issue was resolved by a pull request that fixed the Docker Compose plugin S3 configuration default value [1].

To address the problem of the docker-plugin_daemon repeatedly rebooting and showing a "restarting" status with a connection error in version 1.2.0 of the self-hosted Dify environment, you can follow these steps:

  1. Add these settings to your .env file:

    PLUGIN_S3_USE_AWS_MANAGED_IAM=false
PLUGIN_S3_USE_PATH_STYLE=false

  2. Update your docker-compose.yaml file with default values:

    plugin_daemon:
  environment:
    S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false}
    S3_USE_PATH_STYLE: ${PLUGIN_S3_USE_PATH_STYLE:-false}

  3. Restart the application with these commands:

    docker compose down
docker rmi $(docker images -q 'dify-*')
docker compose up -d

These steps should help resolve the issue by addressing the environment variable parsing problem related to the S3_USE_AWS_MANAGED_IAM variable [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 (Apr 23, 2025): <!-- Answer --> I found a similar issue that was reported and closed: [Failed to start the docker-plugin_daemon-1 repeatedly](https://github.com/langgenius/dify/issues/17703). This issue was resolved by a pull request that fixed the Docker Compose plugin S3 configuration default value <sup>[[1]](https://github.com/langgenius/dify/issues/17703)</sup>. To address the problem of the `docker-plugin_daemon` repeatedly rebooting and showing a "restarting" status with a connection error in version 1.2.0 of the self-hosted Dify environment, you can follow these steps: 1. Add these settings to your `.env` file: ```plaintext PLUGIN_S3_USE_AWS_MANAGED_IAM=false PLUGIN_S3_USE_PATH_STYLE=false ``` 2. Update your `docker-compose.yaml` file with default values: ```yaml plugin_daemon: environment: S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false} S3_USE_PATH_STYLE: ${PLUGIN_S3_USE_PATH_STYLE:-false} ``` 3. Restart the application with these commands: ```bash docker compose down docker rmi $(docker images -q 'dify-*') docker compose up -d ``` These steps should help resolve the issue by addressing the environment variable parsing problem related to the `S3_USE_AWS_MANAGED_IAM` variable <sup>[[2]](https://github.com/langgenius/dify/issues/18415)</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/3fe1f895-5af3-4ca4-858f-d1dc9dec47c4?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/3fe1f895-5af3-4ca4-858f-d1dc9dec47c4?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/3fe1f895-5af3-4ca4-858f-d1dc9dec47c4?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/3fe1f895-5af3-4ca4-858f-d1dc9dec47c4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/3fe1f895-5af3-4ca4-858f-d1dc9dec47c4?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/3fe1f895-5af3-4ca4-858f-d1dc9dec47c4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/3fe1f895-5af3-4ca4-858f-d1dc9dec47c4?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
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#13268
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?