langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

There is a problem deploying Dify in a 64 bit Windows 10 environment without Docker. Please help, everyone. #12450

New Issue
Closed
opened 2026-02-21 19:07:28 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:07:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @mzymcm on GitHub (Apr 1, 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.1.3

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

There is a problem deploying Dify in a 64 bit Windows 10 environment without Docker. Please help, everyone.
Version 1.1.3
The first step is to pull, install, and deploy the following:
https://github.com/langgenius/dify.git
https://github.com/langgenius/dify-plugin-daemon.git
Deploy dify.git:
copy .env.example .env
etcd --data-dir=C:\Dify_all\etcd\data
cd C:\Dify_all\weaviate
.\weaviate.exe --scheme=http --host=0.0.0.0 --port=8080
psql -U postgres
CREATE DATABASE dify;
\q
flask db upgrade
poetry run flask run --host 0.0.0.0 --port=5001 --debug
Enter C: \ Dify.all \ dify \ API to execute
poetry run celery -A app.celery worker -P solo --without-gossip --without-mingle -Q dataset,generation,mail,ops_trace --loglevel
Enter the C: \ Dify.all \ dify \ web directory
copy .env.example .env.local
pnpm install
pnpm build
Modify packagejson
Move the 11 lines
"start": "cp -r .next/static .next/standalone/.next/static && cp -r public .next/standalone/public && cross-env PORT=$npm_config_port HOSTNAME=$npm_config_host node .next/standalone/server.js",
Change to:
"start": "cross-env PORT=$npm_config_port HOSTNAME=$npm_config_host node .next/standalone/server.js",
save
cd C:\Dify_all\dify\web
C:\Windows\System32\robocopy.exe ".next\static" ".next\standalone.next\static" /E /MT:8
C:\Windows\System32\robocopy.exe "public" ".next/standalone/public" /E /MT:8
C:\Users\Administrator\AppData\Roaming\npm\pnpm start
Deploy dify-plugin daemon. git:
copy .env.example .env
go build -o plugin-daemon.exe ./cmd/server
cd C:\dify-plugin-daemon
plugin-daemon.exe
The second step is to use it on the client side, and the following error occurs.
The client has no problem from creating a super manager to entering the management page, but there are always errors when adding model suppliers.
After adding the submission, the following error is reported:
{
"code": "invalid_param",
"message": "PluginDaemonBadRequestError: file not found: icon_s_en.svg\nfailed to remap model icon small en_US\nfailed to remap assets\nfailed to save package",

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @mzymcm on GitHub (Apr 1, 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.1.3 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce There is a problem deploying Dify in a 64 bit Windows 10 environment without Docker. Please help, everyone. Version 1.1.3 The first step is to pull, install, and deploy the following: https://github.com/langgenius/dify.git https://github.com/langgenius/dify-plugin-daemon.git Deploy dify.git: copy .env.example .env etcd --data-dir=C:\Dify_all\etcd\data cd C:\Dify_all\weaviate .\weaviate.exe --scheme=http --host=0.0.0.0 --port=8080 psql -U postgres CREATE DATABASE dify; \q flask db upgrade poetry run flask run --host 0.0.0.0 --port=5001 --debug Enter C: \ Dify.all \ dify \ API to execute poetry run celery -A app.celery worker -P solo --without-gossip --without-mingle -Q dataset,generation,mail,ops_trace --loglevel Enter the C: \ Dify.all \ dify \ web directory copy .env.example .env.local pnpm install pnpm build Modify packagejson Move the 11 lines "start": "cp -r .next/static .next/standalone/.next/static && cp -r public .next/standalone/public && cross-env PORT=$npm_config_port HOSTNAME=$npm_config_host node .next/standalone/server.js", Change to: "start": "cross-env PORT=$npm_config_port HOSTNAME=$npm_config_host node .next/standalone/server.js", save cd C:\Dify_all\dify\web C:\Windows\System32\robocopy.exe ".next\static" ".next\standalone.next\static" /E /MT:8 C:\Windows\System32\robocopy.exe "public" ".next/standalone/public" /E /MT:8 C:\Users\Administrator\AppData\Roaming\npm\pnpm start Deploy dify-plugin daemon. git: copy .env.example .env go build -o plugin-daemon.exe ./cmd/server cd C:\dify-plugin-daemon plugin-daemon.exe The second step is to use it on the client side, and the following error occurs. The client has no problem from creating a super manager to entering the management page, but there are always errors when adding model suppliers. After adding the submission, the following error is reported: { "code": "invalid_param", "message": "PluginDaemonBadRequestError: file not found: icon_s_en.svg\nfailed to remap model icon small en_US\nfailed to remap assets\nfailed to save package", ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:07:28 -05:00
yindo closed this issue 2026-02-21 19:07:28 -05:00
yindo commented 2026-02-21 19:07:28 -05:00
Author
Owner
Copy Link
Copy Source

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

I found a similar unsolved discussion titled "There is a problem deploying Dify in a 64 bit Windows 10 environment without Docker. Please help, everyone" [1]. This discussion might provide some insights or additional context related to your issue.

Regarding the error you're encountering, it seems to be related to missing files, specifically icon_s_en.svg, which is causing a PluginDaemonBadRequestError. This type of error can occur if the necessary files are not correctly located in their expected directories. A common solution is to ensure that all required files are present and correctly mapped in the deployment environment.

Additionally, make sure that the environment variables and paths are correctly set up, as these can affect file remapping and access. If the issue persists, you might want to check the configuration and ensure that all dependencies are correctly installed and configured.

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 1, 2025): <!-- Answer --> I found a similar unsolved discussion titled "There is a problem deploying Dify in a 64 bit Windows 10 environment without Docker. Please help, everyone" <sup>[[1]](https://github.com/langgenius/dify/discussions/17299)</sup>. This discussion might provide some insights or additional context related to your issue. Regarding the error you're encountering, it seems to be related to missing files, specifically `icon_s_en.svg`, which is causing a `PluginDaemonBadRequestError`. This type of error can occur if the necessary files are not correctly located in their expected directories. A common solution is to ensure that all required files are present and correctly mapped in the deployment environment. Additionally, make sure that the environment variables and paths are correctly set up, as these can affect file remapping and access. If the issue persists, you might want to check the configuration and ensure that all dependencies are correctly installed and configured. <!-- 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/51605b61-e962-4fd2-b8dc-dde0aca8d862?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/51605b61-e962-4fd2-b8dc-dde0aca8d862?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/51605b61-e962-4fd2-b8dc-dde0aca8d862?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/51605b61-e962-4fd2-b8dc-dde0aca8d862?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/51605b61-e962-4fd2-b8dc-dde0aca8d862?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/51605b61-e962-4fd2-b8dc-dde0aca8d862?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/51605b61-e962-4fd2-b8dc-dde0aca8d862?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 🐞 bug
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#12450
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?