timeout exceptions in dify-plugin-deamon(v0.0.3) #75

Open
opened 2026-02-16 00:19:37 -05:00 by yindo · 3 comments
Owner

Originally created by @ziyuzhan on GitHub (Apr 2, 2025).

Introducing storage volumes when deploying plugin-deamon separately using k8s resulted in timeout exceptions (unable to configure plugin information after installing the plugin), . Is it due to NFS's inability to keep up with read and write speeds or some other reason

Originally created by @ziyuzhan on GitHub (Apr 2, 2025). Introducing storage volumes when deploying plugin-deamon separately using k8s resulted in timeout exceptions (unable to configure plugin information after installing the plugin), . Is it due to NFS's inability to keep up with read and write speeds or some other reason
yindo added the plugin-daemon label 2026-02-16 00:19:37 -05:00
Author
Owner

@jasonkylelol commented on GitHub (Apr 27, 2025):

@ziyuzhan same problems, any resolution?

@jasonkylelol commented on GitHub (Apr 27, 2025): @ziyuzhan same problems, any resolution?
Author
Owner

@41tair commented on GitHub (May 23, 2025):

Could you provide more information?

Versions

  1. dify-plugin-daemon Version
  2. dify-api Version

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@41tair commented on GitHub (May 23, 2025): Could you provide more information? **Versions** 1. dify-plugin-daemon Version 2. dify-api Version **Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.
Author
Owner

@jinyulovelee commented on GitHub (Jun 18, 2025):

http://127.0.0.1:5004 connection refuse,so 5004port how to start?

@jinyulovelee commented on GitHub (Jun 18, 2025): http://127.0.0.1:5004 connection refuse,so 5004port how to start?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#75