langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -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. #12446

New Issue
Closed
opened 2026-02-21 19:07:27 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:07:27 -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

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 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🤔 cant-reproduce labels 2026-02-21 19:07:27 -05:00
yindo closed this issue 2026-02-21 19:07:27 -05:00
yindo commented 2026-02-21 19:07:27 -05:00
Author
Owner
Copy Link
Copy Source

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

I found a similar discussion regarding deploying Dify in a 64-bit Windows 10 environment without Docker, which might be helpful for your issue. The discussion is titled "There is a problem deploying Dify in a 64 bit Windows 10 environment without Docker. Please help, everyone" and is currently unsolved [1].

Regarding the error you're encountering, "PluginDaemonBadRequestError: file not found: icon_s_en.svg," it seems related to how Dify handles file paths for assets like icons during deployment. A 'file not found' error can occur if the CONSOLE_API_URL is empty, leading to incorrect path handling and resulting in 404 errors for icon URLs. This issue was resolved in a previous pull request by changing the paths to absolute, allowing browsers to correctly interpret and display the icons [2].

Additionally, ensure that your environment variables and configurations are correctly set, especially those related to the Plugin Daemon, as incorrect settings can lead to such errors [3].

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 discussion regarding deploying Dify in a 64-bit Windows 10 environment without Docker, which might be helpful for your issue. The discussion is titled "There is a problem deploying Dify in a 64 bit Windows 10 environment without Docker. Please help, everyone" and is currently unsolved <sup>[[1]](https://github.com/langgenius/dify/discussions/17299)</sup>. Regarding the error you're encountering, "PluginDaemonBadRequestError: file not found: icon_s_en.svg," it seems related to how Dify handles file paths for assets like icons during deployment. A 'file not found' error can occur if the `CONSOLE_API_URL` is empty, leading to incorrect path handling and resulting in 404 errors for icon URLs. This issue was resolved in a previous pull request by changing the paths to absolute, allowing browsers to correctly interpret and display the icons <sup>[[2]](https://github.com/langgenius/dify/issues/15472)</sup>. Additionally, ensure that your environment variables and configurations are correctly set, especially those related to the Plugin Daemon, as incorrect settings can lead to such errors <sup>[[3]](https://github.com/langgenius/dify/issues/14850)</sup>. <!-- 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/47a30366-3021-4809-95f4-df341483bd2d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/47a30366-3021-4809-95f4-df341483bd2d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/47a30366-3021-4809-95f4-df341483bd2d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/47a30366-3021-4809-95f4-df341483bd2d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/47a30366-3021-4809-95f4-df341483bd2d?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/47a30366-3021-4809-95f4-df341483bd2d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/47a30366-3021-4809-95f4-df341483bd2d?feedback_type=other)</sup>
yindo commented 2026-02-21 19:07:27 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 1, 2025):

We do not provide technical support for starting from the source. Thank you for your understanding. We assume you have the necessary expertise to set it up independently. If you require technical support, please obtain our business license by contacting us at business@dify.ai.

@crazywoola commented on GitHub (Apr 1, 2025): We do not provide technical support for starting from the source. Thank you for your understanding. We assume you have the necessary expertise to set it up independently. If you require technical support, please obtain our business license by contacting us at business@dify.ai.
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 🤔 cant-reproduce
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#12446
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?