mirror of
https://github.com/langgenius/dify-plugin-daemon.git
synced 2026-07-21 17:25:23 -04:00
Path issue in Docker deployment of dify-plugin-daemon causes plugins to malfunction #40
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 @yjc980121 on GitHub (Mar 13, 2025).
Description:
In the Docker deployment version, the endpoint path of dify-plugin-daemon does not start with /, while in Dify Cloud, the endpoint path does start with /. This causes requests to the root path / in HTML to be handled incorrectly, resulting in plugins (such as yeuoly/waifu) not working properly.
Steps to Reproduce:
Deploy dify-plugin-daemon in a Docker environment.
Deploy the yeuoly/waifu plugin.
Start the service and access the relevant page.
Observe whether the plugin functions work properly.
Expected Behavior:
The plugin should work properly in the Docker deployment version, just as it does in Dify Cloud.
Actual Behavior:
In the Docker deployment version, the plugin does not work properly, and requests to the root path / in HTML are not handled correctly.
Possible Solution:
Modify the configuration of dify-plugin-daemon to ensure that the endpoint path in the Docker deployment version starts with /.
Dynamically handle paths in the HTML code to adapt to path differences in different environments.
Additional Information:
Specific configuration files and environment settings for the Docker deployment version.
Relevant documentation and code for the Dify Plugin Daemon project.
We hope the team can pay attention to and resolve this issue as soon as possible.
@Yeuoly commented on GitHub (Mar 17, 2025):
Thanks for your report, already got the problem, but it can only be handled in the plugin side, I will fix the plugin ASAP