docker compose ps
to check you plugin daemon’s image is it running
Still getting errors. After installing Dify with Docker, when entering the interface, it keeps reporting the following two errors:
Failed to request plugin daemon, url: plugin/5a017356-6fa9-4536-8863-a1ff7d4ee2ba/management/install/tasks
Failed to request plugin daemon, url:plugin/5a017356-6fa9-4536-8863-a1ff7d4ee2ba/management/models
localhost:docker qingfeng$ docker logs ceb1b1183b5f
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
2026/01/27 12:20:48 pool.go:32: [INFO]init routine pool, size: 10000
2026/01/27 12:20:49 init.go:103: [INFO]dify plugin db initialized
2026/01/27 12:20:49 manager.go:114: [INFO]start plugin manager daemon…
2026/01/27 12:20:49 watcher.go:17: [INFO]start to handle new plugins in path: plugin
2026/01/27 12:20:49 watcher.go:18: [INFO]Launching plugins with max concurrency: 2
2026/01/27 12:20:49 init.go:20: [INFO]Persistence initialized
[gnet] 2026-01-27T12:20:49.875181162Z INFO logging/logger.go:256 Launching gnet with 8 event-loops, listening on: tcp://0.0.0.0:5003
2026/01/27 12:21:49 cluster_lifetime.go:113: [INFO]current node has become the master of the cluster
2026/01/27 12:22:19 node.go:213: [INFO]node 930caa3c-8d81-4d10-b8d1-faa519677117 has been removed from the cluster due to being disconnected
2026/01/27 13:14:27 node.go:213: [INFO]node 65c32b9c-43c1-49bf-884f-ecb867e6fb83 has been removed from the cluster due to being disconnected
2026/01/27 13:48:16 node.go:213: [INFO]node 65c32b9c-43c1-49bf-884f-ecb867e6fb83 has been removed from the cluster due to being disconnected
2026/01/27 14:04:31 node.go:213: [INFO]node 65c32b9c-43c1-49bf-884f-ecb867e6fb83 has been removed from the cluster due to being disconnected
2026/01/27 14:08:18 node.go:213: [INFO]node 65c32b9c-43c1-49bf-884f-ecb867e6fb83 has been removed from the cluster due to being disconnected
I see your logs
but “has been removed from the cluster due to being disconnected“ is not real clear
you shoud check the other plug-in (for example, middleware such as Redis and network components)
or check your service’s configuration is it meets the needs
Excuse me, I’d like to ask: Regarding [Redis and other middleware and network components], I don’t need to install Redis middleware separately, right? After I started Dify with Docker, it immediately reported an error. I tried two versions: Dify 1.11.4 and Dify 1.8.0. After starting and logging in, it immediately reported an error. No plugins were installed, the plugin page kept loading, and error messages kept appearing. I’d close the error message, and it would pop up again shortly. The main errors are as follows:
Failed to request plugin daemon, url: plugin/5a017356-6fa9-4536-8863-a1ff7d4ee2ba/management/list
Failed to request plugin daemon, url:plugin/5a017356-6fa9-4536-8863-a1ff7d4ee2ba/management/models
Failed to request plugin daemon, url: plugin/5a017356-6fa9-4536-8863-a1ff7d4ee2ba/management/install/tasks
First, if you use docker compose to start Dify
You must have redis mirrors and docker networks
Then check whether redis has error logs
Check whether the network segment and port configured in docker-compose.yml conflict with the host environment or other applications
Finally check the server configuration
Thank you for your patient reply! It’s still not working. The issue is that after logging in, the top right corner continuously reports errors:
Failed to request plugin daemon, url: plugin/5a017356-6fa9-4536-8863-a1ff7d4ee2ba/management/list
Failed to request plugin daemon, url:plugin/5a017356-6fa9-4536-8863-a1ff7d4ee2ba/management/models
Failed to request plugin daemon, url: plugin/5a017356-6fa9-4536-8863-a1ff7d4ee2ba/management/install/tasks
Currently, it’s the dify-1.8.0 version. I haven’t modified the docker-compose.yml configuration file, and the Docker network configuration is as follows.
I’ve tried several versions (e.g., 1.11.3, 1.8.0, 1.2.0), and the page always reports the same error.
Redis starts normally. I see ‘success’ in the logs.
For docker-plugin_daemon-1, the error logs vary across different versions:
Version 1.8 of docker-plugin_daemon-1 reports this error:
2026/01/28 08:30:05 watcher.go:18: [INFO]Launching plugins with max concurrency: 2
2026/01/28 08:30:05 init.go:20: [INFO]Persistence initialized
[gnet] 2026-01-28T08:30:05.516768271Z INFO logging/logger.go:256 Launching gnet with 8 event-loops, listening on: tcp://0.0.0.0:5003
2026/01/28 08:31:05 cluster_lifetime.go:113: [INFO]current node has become the master of the cluster
2026/01/28 08:31:05 node.go:213: [INFO]node f07bf1ad-49eb-4fd0-8705-8459a7cb1145 has been removed from the cluster due to being disconnected
2026/01/28 08:31:05 node.go:213: [INFO]node 6e81c5ba-9e88-4875-b60f-e72a384e53bf has been removed from the cluster due to being disconnected
Version 1.2 of docker-plugin_daemon-1 keeps restarting and cannot start. The logs show the following error:
[PANIC]Error processing environment variables: envconfig.Process: assigning S3_USE_AWS_MANAGED_IAM to S3UseAwsManagedIam: converting ‘’ to type bool. details: strconv.ParseBool: parsing "": invalid syntax
panic: [PANIC]Error processing environment variables: envconfig.Process: assigning S3_USE_AWS_MANAGED_IAM to S3UseAwsManagedIam: converting ‘’ to type bool. details: strconv.ParseBool: parsing "": invalid syntax
I think you can enter the node first
Check the communication between nodes is normal
If communication fails, you need to consider modifying the network configuration in yml
Also, a possibility that the resources you allocate are not enough to start all nodes
New Ticket Created