mirror of
https://github.com/langgenius/dify-plugin-daemon.git
synced 2026-07-21 17:25:23 -04:00
no available node, plugin runtime not found #231
Reference in New Issue
Block a user
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?
Originally created by @gaoding-hailang on GitHub (Jan 22, 2026).
Self Checks
To make sure we get to you in time, please check the following :)
Versions
Describe the bug
When I implement a plugin myself and debug it locally, I always fail to locate the plugin. However, the plugin version can be displayed in the Dify interface and the node can also be found, but an error occurs during runtime，but if use dify-plugin-daemon version 0.4.2 is ok:
2026/01/22 15:20:20 factory.go:28: [31m[ERROR]PluginDaemonInternalServerError: no available node, plugin runtime not found
goroutine 1102 [running]:
runtime/debug.Stack()
/usr/local/go/src/runtime/debug/stack.go:26 +0x5e
github.com/langgenius/dify-plugin-daemon/internal/types/exception.InternalServerError({0x2b50f60, 0xc003451d10})
/app/internal/types/exception/factory.go:27 +0x27
github.com/langgenius/dify-plugin-daemon/internal/server.(*App).redirectPluginInvokeByPluginIdentifier(0xc0006caac0, 0xc0006be100, {0xc001e21180?, 0xcd2c94?}, {0x2b50f60, 0x407da40})
/app/internal/server/middleware.go:132 +0x105
github.com/langgenius/dify-plugin-daemon/internal/server.(*App).pluginDispatchGroup.(*App).RedirectPluginInvoke.func3(0xc0006be100)
/app/internal/server/middleware.go:106 +0x8a
github.com/gin-gonic/gin.(*Context).Next(0xc0006be100)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 +0x2b
github.com/langgenius/dify-plugin-daemon/internal/server.(*App).pluginDispatchGroup.(*App).FetchPluginInstallation.func2(0xc0006be100)
/app/internal/server/middleware.go:78 +0x235
github.com/gin-gonic/gin.(*Context).Next(0xc0006be100)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 +0x2b
github.com/langgenius/dify-plugin-daemon/internal/server.(*App).pluginDispatchGroup.CollectActiveDispatchRequests.func1(0x27d2bbc?)
/app/internal/server/controllers/health_check.go:28 +0x25
github.com/gin-gonic/gin.(*Context).Next(0xc0006be100)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 +0x2b
github.com/langgenius/dify-plugin-daemon/internal/server.(*App).pluginGroup.CheckingKey.func1(0xc0006be100)
/app/internal/server/middleware.go:26 +0x95
github.com/gin-gonic/gin.(*Context).Next(0xc0006be100)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 +0x2b
github.com/langgenius/dify-plugin-daemon/internal/server.(*App).server.CollectActiveRequests.func3(0xc0052a7a10?)
/app/internal/server/controllers/health_check.go:20 +0x25
github.com/gin-gonic/gin.(*Context).Next(...)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185
github.com/gin-gonic/gin.CustomRecoveryWithWriter.func1(0xc0006be100)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/recovery.go:102 +0x6f
github.com/gin-gonic/gin.(*Context).Next(...)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185
github.com/gin-gonic/gin.LoggerWithConfig.func1(0xc0006be100)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/logger.go:249 +0xe5
github.com/gin-gonic/gin.(*Context).Next(...)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest(0xc0000f44e0, 0xc0006be100)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633 +0x872
github.com/gin-gonic/gin.(*Engine).ServeHTTP(0xc0000f44e0, {0x2b813f0, 0xc000ea96c0}, 0xc001d64c80)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589 +0x1aa
net/http.serverHandler.ServeHTTP({0x2b731c8?}, {0x2b813f0?, 0xc000ea96c0?}, 0x6?)
/usr/local/go/src/net/http/server.go:3301 +0x8e
net/http.(*conn).serve(0xc000e74e10, {0x2b85958, 0xc00078b860})
/usr/local/go/src/net/http/server.go:2102 +0x625
created by net/http.(*Server).Serve in goroutine 76
/usr/local/go/src/net/http/server.go:3454 +0x485
[0m
@dosubot[bot] commented on GitHub (Jan 22, 2026):
Hi @gaoding-hailang! I'm Dosu and I’m helping the dify-plugin-daemon team.
This error means the plugin runtime was never registered or was removed before invocation. Even if the plugin version and node show up in the UI, the runtime only becomes available after successful environment initialization and startup. Common causes include: manifest.yaml missing required fields or having encoding issues, misaligned Docker volume mounts or environment variables (so the daemon can't read the plugin files), persistent storage misconfiguration (plugin data lost after restarts), or rapid plugin restarts during debugging (the runtime can't reconnect due to a sleep delay) [source] [source] [source].
Troubleshooting checklist:
If you share your manifest.yaml and environment setup, I can help spot specific issues.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@fatelei commented on GitHub (Jan 22, 2026):
you serve one server, so error is no nodes
@gaoding-hailang commented on GitHub (Jan 22, 2026):
In version 0.5.2, this configuration (see in image) needs to be consistent with the version number; however, this requirement does not apply to version 0.4.2. I solved this problem by modifying the value to match the version number.
