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

After upgrading from dify 1.6.0 to dify 1.7.1, there was an exception stating "Model deepseek ai/DeepSeek-V3 does not exist #15858

New Issue
Closed
opened 2026-02-21 19:23:41 -05:00 by yindo · 11 comments
yindo commented 2026-02-21 19:23:41 -05:00
Owner
Copy Link
Copy Source

Originally created by @JAVA-LW on GitHub (Aug 4, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.7.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After upgrading from dify 1.6.0 to dify 1.7.1,

✔️ Expected Behavior

normal use

❌ Actual Behavior

172.18.0.1 - - [04/Aug/2025:08:53:56 +0000] "POST /console/api/apps/2fcf21dd-121e-4530-a25d-617a7a5ed887/chat-messages HTTP/1.1" 400 96 "https://XXXX/app/2fcf21dd-121e-4530-a25d-617a7a5ed887/configuration" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36" "xxx.231.26.82"

https://XXXX/console/api/apps/2fcf21dd-121e-4530-a25d-617a7a5ed887/chat-messages

param:
{
"response_mode": "streaming",
"conversation_id": "",
"files": [],
"query": "你好",
"inputs": {},
"model_config": {
"pre_prompt": "",
"prompt_type": "simple",
"chat_prompt_config": {},
"completion_prompt_config": {},
"user_input_form": [],
"dataset_query_variable": "",
"opening_statement": "",
"more_like_this": {
"enabled": false
},
"suggested_questions": [],
"suggested_questions_after_answer": {
"enabled": false
},
"text_to_speech": {
"enabled": false,
"voice": "",
"language": ""
},
"speech_to_text": {
"enabled": false
},
"retriever_resource": {
"enabled": true
},
"sensitive_word_avoidance": {
"enabled": false,
"type": "",
"configs": []
},
"agent_mode": {
"max_iteration": 5,
"enabled": true,
"strategy": "react",
"tools": [
{
"provider_id": "junjiem/mcp_sse/mcp_sse",
"provider_type": "builtin",
"provider_name": "junjiem/mcp_sse/mcp_sse",
"tool_name": "mcp_sse_list_tools",
"tool_label": "获取 MCP 工具列表",
"tool_parameters": {},
"notAuthor": false,
"enabled": false,
"isDeleted": false
},
{
"provider_id": "junjiem/mcp_sse/mcp_sse",
"provider_type": "builtin",
"provider_name": "junjiem/mcp_sse/mcp_sse",
"tool_name": "mcp_sse_call_tool",
"tool_label": "调用 MCP 工具",
"tool_parameters": {
"tool_name": "",
"arguments": ""
},
"notAuthor": false,
"enabled": false,
"isDeleted": false
}
],
"prompt": null
},
"dataset_configs": {
"retrieval_model": "multiple",
"top_k": 4,
"reranking_enable": false,
"datasets": {
"datasets": []
}
},
"file_upload": {
"image": {
"detail": "high",
"enabled": false,
"number_limits": 3,
"transfer_methods": [
"remote_url",
"local_file"
]
},
"enabled": false,
"allowed_file_types": [],
"allowed_file_extensions": [
".JPG",
".JPEG",
".PNG",
".GIF",
".WEBP",
".SVG",
".MP4",
".MOV",
".MPEG",
".WEBM"
],
"allowed_file_upload_methods": [
"remote_url",
"local_file"
],
"number_limits": 3,
"fileUploadConfig": {
"file_size_limit": 15,
"batch_count_limit": 5,
"image_file_size_limit": 10,
"video_file_size_limit": 100,
"audio_file_size_limit": 50,
"workflow_file_upload_limit": 10
}
},
"annotation_reply": {
"enabled": false
},
"supportAnnotation": true,
"appId": "2fcf21dd-121e-4530-a25d-617a7a5ed887",
"supportCitationHitInfo": true,
"model": {
"provider": "langgenius/siliconflow/siliconflow",
"name": "deepseek-ai/DeepSeek-V3",
"mode": "chat",
"completion_params": {
"stop": []
}
}
},
"parent_message_id": null
}

return:

{
"code": "invalid_param",
"message": "Model deepseek-ai/DeepSeek-V3 not exist.",
"status": 400
}

It can be used normally at 1.6.0

Originally created by @JAVA-LW on GitHub (Aug 4, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.7.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After upgrading from dify 1.6.0 to dify 1.7.1, ### ✔️ Expected Behavior normal use ### ❌ Actual Behavior 172.18.0.1 - - [04/Aug/2025:08:53:56 +0000] "POST /console/api/apps/2fcf21dd-121e-4530-a25d-617a7a5ed887/chat-messages HTTP/1.1" 400 96 "https://XXXX/app/2fcf21dd-121e-4530-a25d-617a7a5ed887/configuration" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36" "xxx.231.26.82" https://XXXX/console/api/apps/2fcf21dd-121e-4530-a25d-617a7a5ed887/chat-messages param: { "response_mode": "streaming", "conversation_id": "", "files": [], "query": "你好", "inputs": {}, "model_config": { "pre_prompt": "", "prompt_type": "simple", "chat_prompt_config": {}, "completion_prompt_config": {}, "user_input_form": [], "dataset_query_variable": "", "opening_statement": "", "more_like_this": { "enabled": false }, "suggested_questions": [], "suggested_questions_after_answer": { "enabled": false }, "text_to_speech": { "enabled": false, "voice": "", "language": "" }, "speech_to_text": { "enabled": false }, "retriever_resource": { "enabled": true }, "sensitive_word_avoidance": { "enabled": false, "type": "", "configs": [] }, "agent_mode": { "max_iteration": 5, "enabled": true, "strategy": "react", "tools": [ { "provider_id": "junjiem/mcp_sse/mcp_sse", "provider_type": "builtin", "provider_name": "junjiem/mcp_sse/mcp_sse", "tool_name": "mcp_sse_list_tools", "tool_label": "获取 MCP 工具列表", "tool_parameters": {}, "notAuthor": false, "enabled": false, "isDeleted": false }, { "provider_id": "junjiem/mcp_sse/mcp_sse", "provider_type": "builtin", "provider_name": "junjiem/mcp_sse/mcp_sse", "tool_name": "mcp_sse_call_tool", "tool_label": "调用 MCP 工具", "tool_parameters": { "tool_name": "", "arguments": "" }, "notAuthor": false, "enabled": false, "isDeleted": false } ], "prompt": null }, "dataset_configs": { "retrieval_model": "multiple", "top_k": 4, "reranking_enable": false, "datasets": { "datasets": [] } }, "file_upload": { "image": { "detail": "high", "enabled": false, "number_limits": 3, "transfer_methods": [ "remote_url", "local_file" ] }, "enabled": false, "allowed_file_types": [], "allowed_file_extensions": [ ".JPG", ".JPEG", ".PNG", ".GIF", ".WEBP", ".SVG", ".MP4", ".MOV", ".MPEG", ".WEBM" ], "allowed_file_upload_methods": [ "remote_url", "local_file" ], "number_limits": 3, "fileUploadConfig": { "file_size_limit": 15, "batch_count_limit": 5, "image_file_size_limit": 10, "video_file_size_limit": 100, "audio_file_size_limit": 50, "workflow_file_upload_limit": 10 } }, "annotation_reply": { "enabled": false }, "supportAnnotation": true, "appId": "2fcf21dd-121e-4530-a25d-617a7a5ed887", "supportCitationHitInfo": true, "model": { "provider": "langgenius/siliconflow/siliconflow", "name": "deepseek-ai/DeepSeek-V3", "mode": "chat", "completion_params": { "stop": [] } } }, "parent_message_id": null } return: { "code": "invalid_param", "message": "Model deepseek-ai/DeepSeek-V3 not exist.", "status": 400 } It can be used normally at 1.6.0
yindo added the 🐞 bug label 2026-02-21 19:23:41 -05:00
yindo closed this issue 2026-02-21 19:23:41 -05:00
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 4, 2025):

The error happens because Dify 1.7.1 does not recognize the model identifier deepseek-ai/DeepSeek-V3. This is likely due to changes in how models are registered and referenced between versions. In 1.7.1, DeepSeek models must be explicitly registered in the provider configuration, and the identifier you used may no longer be valid or present in the registry. The most common supported identifiers are now deepseek-chat or deepseek-coder, not deepseek-ai/DeepSeek-V3 see details.

To resolve this, go to System Settings > Model Providers and ensure you have the DeepSeek provider configured with the correct model name (such as deepseek-chat), API endpoint, and credentials. If you use a plugin-based provider, make sure your Docker environment allows network access for the plugin daemon during its first initialization, and that environment variables like PLUGIN_DAEMON_URL and SANDBOX_ENABLE_NETWORK are set correctly. After making changes, restart the relevant containers. If you still see the error, check the plugin logs for initialization or dependency errors, and verify your DeepSeek account balance if using their API reference.

If you need to use the V3 model specifically and it is not listed, you may need to update your configuration to use the new supported model names, or manually add the model to the provider registry if possible. There is currently no documentation for restoring support for the old identifier, so using the supported model names is the recommended path.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 4, 2025): <!-- Answer --> The error happens because Dify 1.7.1 does not recognize the model identifier `deepseek-ai/DeepSeek-V3`. This is likely due to changes in how models are registered and referenced between versions. In 1.7.1, DeepSeek models must be explicitly registered in the provider configuration, and the identifier you used may no longer be valid or present in the registry. The most common supported identifiers are now `deepseek-chat` or `deepseek-coder`, not `deepseek-ai/DeepSeek-V3` [see details](https://github.com/langgenius/dify/issues/23236). To resolve this, go to System Settings > Model Providers and ensure you have the DeepSeek provider configured with the correct model name (such as `deepseek-chat`), API endpoint, and credentials. If you use a plugin-based provider, make sure your Docker environment allows network access for the plugin daemon during its first initialization, and that environment variables like `PLUGIN_DAEMON_URL` and `SANDBOX_ENABLE_NETWORK` are set correctly. After making changes, restart the relevant containers. If you still see the error, check the plugin logs for initialization or dependency errors, and verify your DeepSeek account balance if using their API [reference](https://github.com/langgenius/dify/issues/23236). If you need to use the V3 model specifically and it is not listed, you may need to update your configuration to use the new supported model names, or manually add the model to the provider registry if possible. There is currently no documentation for restoring support for the old identifier, so using the supported model names is the recommended path. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/019a7501-9e8b-4207-9fd4-360c3a684702?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/019a7501-9e8b-4207-9fd4-360c3a684702?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/019a7501-9e8b-4207-9fd4-360c3a684702?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/019a7501-9e8b-4207-9fd4-360c3a684702?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/019a7501-9e8b-4207-9fd4-360c3a684702?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/019a7501-9e8b-4207-9fd4-360c3a684702?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/019a7501-9e8b-4207-9fd4-360c3a684702?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/23361)
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@JAVA-LW commented on GitHub (Aug 4, 2025):

tdcktz@td-dify:~/git/dify/docker$ docker logs --tail=100 -f docker-plugin_daemon-1
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/recovery.go:102 (0xf964bb)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf95604)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/logger.go:249 (0xf955eb)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf949f1)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633 (0xf94460)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589 (0xf93f91)
/usr/local/go/src/net/http/server.go:3210 (0x7e26cd)
/usr/local/go/src/net/http/server.go:2092 (0x7c1bef)
/usr/local/go/src/runtime/asm_amd64.s:1700 (0x47d3a0)

[GIN] 2025/08/04 - 09:11:30 | 200 | 51.496175ms | 172.18.0.7 | GET "/plugin/b9838708-6956-4d95-a393-8ea4ac5471db/management/models?page=1&page_size=256"
[GIN] 2025/08/04 - 09:11:30 | 500 | 38.135501ms | 172.18.0.7 | POST "/plugin/b9838708-6956-4d95-a393-8ea4ac5471db/dispatch/model/schema"

2025/08/04 09:11:30 [Recovery] 2025/08/04 - 09:11:30 panic recovered:
runtime error: invalid memory address or nil pointer dereference
/usr/local/go/src/runtime/panic.go:262 (0x4771b8)
/usr/local/go/src/runtime/signal_unix.go:917 (0x477188)
/app/internal/core/plugin_manager/local_runtime/stdio.go:85 (0xdbf0b2)
/app/internal/core/plugin_manager/local_runtime/io.go:16 (0xdbca1a)
/app/internal/core/plugin_daemon/generic.go:27 (0xfda4d6)
/app/internal/core/plugin_daemon/model.gen.go:161 (0x1008dab)
/app/internal/service/model.gen.go:210 (0x1008d92)
/app/internal/service/base_sse.go:116 (0x1013cfa)
/app/internal/service/base_sse.go:44 (0x1013f5e)
/app/internal/service/base_sse.go:114 (0x1013c44)
/app/internal/service/model.gen.go:208 (0x1008d51)
/app/internal/server/controllers/model.gen.go:163 (0x1ec7fa8)
/app/internal/server/controllers/base.go:53 (0x103de1b)
/app/internal/server/controllers/base.go:31 (0x103e281)
/app/internal/server/controllers/base.go:37 (0x103dd35)
/app/internal/server/controllers/model.gen.go:160 (0x1ec7ef3)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/middleware.go:170 (0x1ecaa33)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/middleware.go:97 (0x1ecaad3)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/middleware.go:66 (0x1ecedb1)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/controllers/health_check.go:28 (0x1eceaa4)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/middleware.go:24 (0x1eca1b4)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/controllers/health_check.go:20 (0x1ecea44)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf964ce)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/recovery.go:102 (0xf964bb)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf95604)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/logger.go:249 (0xf955eb)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf949f1)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633 (0xf94460)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589 (0xf93f91)
/usr/local/go/src/net/http/server.go:3210 (0x7e26cd)
/usr/local/go/src/net/http/server.go:2092 (0x7c1bef)
/usr/local/go/src/runtime/asm_amd64.s:1700 (0x47d3a0)

@JAVA-LW commented on GitHub (Aug 4, 2025): tdcktz@td-dify:~/git/dify/docker$ docker logs --tail=100 -f docker-plugin_daemon-1 /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/recovery.go:102 (0xf964bb) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf95604) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/logger.go:249 (0xf955eb) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf949f1) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633 (0xf94460) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589 (0xf93f91) /usr/local/go/src/net/http/server.go:3210 (0x7e26cd) /usr/local/go/src/net/http/server.go:2092 (0x7c1bef) /usr/local/go/src/runtime/asm_amd64.s:1700 (0x47d3a0) [GIN] 2025/08/04 - 09:11:30 | 200 | 51.496175ms | 172.18.0.7 | GET "/plugin/b9838708-6956-4d95-a393-8ea4ac5471db/management/models?page=1&page_size=256" [GIN] 2025/08/04 - 09:11:30 | 500 | 38.135501ms | 172.18.0.7 | POST "/plugin/b9838708-6956-4d95-a393-8ea4ac5471db/dispatch/model/schema" 2025/08/04 09:11:30 [Recovery] 2025/08/04 - 09:11:30 panic recovered: runtime error: invalid memory address or nil pointer dereference /usr/local/go/src/runtime/panic.go:262 (0x4771b8) /usr/local/go/src/runtime/signal_unix.go:917 (0x477188) /app/internal/core/plugin_manager/local_runtime/stdio.go:85 (0xdbf0b2) /app/internal/core/plugin_manager/local_runtime/io.go:16 (0xdbca1a) /app/internal/core/plugin_daemon/generic.go:27 (0xfda4d6) /app/internal/core/plugin_daemon/model.gen.go:161 (0x1008dab) /app/internal/service/model.gen.go:210 (0x1008d92) /app/internal/service/base_sse.go:116 (0x1013cfa) /app/internal/service/base_sse.go:44 (0x1013f5e) /app/internal/service/base_sse.go:114 (0x1013c44) /app/internal/service/model.gen.go:208 (0x1008d51) /app/internal/server/controllers/model.gen.go:163 (0x1ec7fa8) /app/internal/server/controllers/base.go:53 (0x103de1b) /app/internal/server/controllers/base.go:31 (0x103e281) /app/internal/server/controllers/base.go:37 (0x103dd35) /app/internal/server/controllers/model.gen.go:160 (0x1ec7ef3) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/middleware.go:170 (0x1ecaa33) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/middleware.go:97 (0x1ecaad3) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/middleware.go:66 (0x1ecedb1) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/controllers/health_check.go:28 (0x1eceaa4) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/middleware.go:24 (0x1eca1b4) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/controllers/health_check.go:20 (0x1ecea44) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf964ce) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/recovery.go:102 (0xf964bb) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf95604) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/logger.go:249 (0xf955eb) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf949f1) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633 (0xf94460) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589 (0xf93f91) /usr/local/go/src/net/http/server.go:3210 (0x7e26cd) /usr/local/go/src/net/http/server.go:2092 (0x7c1bef) /usr/local/go/src/runtime/asm_amd64.s:1700 (0x47d3a0)
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 4, 2025):

Your plugin_daemon panic and "Model deepseek-ai/DeepSeek-V3 not exist" error after upgrading to Dify 1.7.1 are both caused by the model not being registered or initialized correctly in the new version. This usually happens if the plugin daemon couldn't access the network to install dependencies during its first run, or if the model identifier changed and is no longer valid in 1.7.1. The panic occurs because the daemon tries to access a missing or nil model object, which is a known issue when models are not properly registered or initialized after an upgrade (source, source).

To fix this:

  1. Make sure your Docker environment allows network access for the plugin daemon during initialization.
  2. Double-check that environment variables like PLUGIN_DAEMON_URL (should be http://host.docker.internal:5002), SANDBOX_ENABLE_NETWORK (should be true), and PLUGIN_STORAGE_TYPE are set correctly.
  3. Remove and reinstall the DeepSeek provider in System Settings > Model Providers, and use the supported model names for 1.7.1 (such as deepseek-chat or deepseek-coder).
  4. Restart the plugin daemon and related containers after making changes.
  5. If you migrated your Docker environment from another machine or network, reinitialize all plugins after ensuring network access.

If you still see the error, check the plugin daemon logs for dependency installation failures or missing model registrations. Setting a reachable PIP_MIRROR_URL and increasing PLUGIN_PYTHON_ENV_INIT_TIMEOUT can help if you have network/firewall restrictions (source, source).

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 4, 2025): <!-- Answer --> Your plugin_daemon panic and "Model deepseek-ai/DeepSeek-V3 not exist" error after upgrading to Dify 1.7.1 are both caused by the model not being registered or initialized correctly in the new version. This usually happens if the plugin daemon couldn't access the network to install dependencies during its first run, or if the model identifier changed and is no longer valid in 1.7.1. The panic occurs because the daemon tries to access a missing or nil model object, which is a known issue when models are not properly registered or initialized after an upgrade ([source](https://github.com/langgenius/dify/issues/19797), [source](https://github.com/langgenius/dify/issues/23236)). To fix this: 1. Make sure your Docker environment allows network access for the plugin daemon during initialization. 2. Double-check that environment variables like `PLUGIN_DAEMON_URL` (should be `http://host.docker.internal:5002`), `SANDBOX_ENABLE_NETWORK` (should be `true`), and `PLUGIN_STORAGE_TYPE` are set correctly. 3. Remove and reinstall the DeepSeek provider in System Settings > Model Providers, and use the supported model names for 1.7.1 (such as `deepseek-chat` or `deepseek-coder`). 4. Restart the plugin daemon and related containers after making changes. 5. If you migrated your Docker environment from another machine or network, reinitialize all plugins after ensuring network access. If you still see the error, check the plugin daemon logs for dependency installation failures or missing model registrations. Setting a reachable `PIP_MIRROR_URL` and increasing `PLUGIN_PYTHON_ENV_INIT_TIMEOUT` can help if you have network/firewall restrictions ([source](https://github.com/langgenius/dify/issues/19797), [source](https://github.com/langgenius/dify/issues/20325)). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/ee9f5d6b-7417-42f9-8294-eefac4e0c2bf?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ee9f5d6b-7417-42f9-8294-eefac4e0c2bf?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ee9f5d6b-7417-42f9-8294-eefac4e0c2bf?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ee9f5d6b-7417-42f9-8294-eefac4e0c2bf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ee9f5d6b-7417-42f9-8294-eefac4e0c2bf?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ee9f5d6b-7417-42f9-8294-eefac4e0c2bf?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ee9f5d6b-7417-42f9-8294-eefac4e0c2bf?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/23361)
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@JAVA-LW commented on GitHub (Aug 4, 2025):

EXPOSE_PLUGIN_DAEMON_PORT=5002
PLUGIN_DAEMON_PORT=5002
PLUGIN_DAEMON_KEY=lYkiYYT6owG+71oLerGzA7GXCgOT++6ovaezWAjpCjf+Sjc3ZtU+qUEi
PLUGIN_DAEMON_URL=http://plugin_daemon:5002
PLUGIN_MAX_PACKAGE_SIZE=52428800
PLUGIN_PPROF_ENABLED=false

Enable network for the sandbox service

SANDBOX_ENABLE_NETWORK=true

PLUGIN_STORAGE_TYPE=local
@dosu

@JAVA-LW commented on GitHub (Aug 4, 2025): EXPOSE_PLUGIN_DAEMON_PORT=5002 PLUGIN_DAEMON_PORT=5002 PLUGIN_DAEMON_KEY=lYkiYYT6owG+71oLerGzA7GXCgOT++6ovaezWAjpCjf+Sjc3ZtU+qUEi PLUGIN_DAEMON_URL=http://plugin_daemon:5002 PLUGIN_MAX_PACKAGE_SIZE=52428800 PLUGIN_PPROF_ENABLED=false # Enable network for the sandbox service SANDBOX_ENABLE_NETWORK=true PLUGIN_STORAGE_TYPE=local [@dosu](https://go.dosu.dev/dosubot)
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 4, 2025):

Your environment variables look correct, but the error and plugin_daemon panic are caused by the model identifier deepseek-ai/DeepSeek-V3 no longer being valid in Dify 1.7.1. Supported DeepSeek model names are now deepseek-chat or deepseek-coder.

To fix this, open System Settings > Model Providers in the Dify UI and check which DeepSeek models are available. Remove and re-add the DeepSeek provider using a supported model name if needed. Make sure your plugin daemon container has outbound internet access during initialization (not just SANDBOX_ENABLE_NETWORK=true, but actual Docker network connectivity). After making changes, restart the plugin daemon and related containers. If the error persists, check the plugin daemon logs for dependency or registration errors and share any relevant log details for further troubleshooting reference.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 4, 2025): <!-- Answer --> Your environment variables look correct, but the error and plugin_daemon panic are caused by the model identifier `deepseek-ai/DeepSeek-V3` no longer being valid in Dify 1.7.1. Supported DeepSeek model names are now `deepseek-chat` or `deepseek-coder`. To fix this, open System Settings > Model Providers in the Dify UI and check which DeepSeek models are available. Remove and re-add the DeepSeek provider using a supported model name if needed. Make sure your plugin daemon container has outbound internet access during initialization (not just `SANDBOX_ENABLE_NETWORK=true`, but actual Docker network connectivity). After making changes, restart the plugin daemon and related containers. If the error persists, check the plugin daemon logs for dependency or registration errors and share any relevant log details for further troubleshooting [reference](https://github.com/langgenius/dify/issues/23236). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/a0ee3b3f-6cae-4b9a-acee-c5db0f57ac46?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a0ee3b3f-6cae-4b9a-acee-c5db0f57ac46?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a0ee3b3f-6cae-4b9a-acee-c5db0f57ac46?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a0ee3b3f-6cae-4b9a-acee-c5db0f57ac46?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a0ee3b3f-6cae-4b9a-acee-c5db0f57ac46?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a0ee3b3f-6cae-4b9a-acee-c5db0f57ac46?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a0ee3b3f-6cae-4b9a-acee-c5db0f57ac46?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/23361)
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 4, 2025):

Please remove the provider and install it again. Please try to install the latest version as well.

@crazywoola commented on GitHub (Aug 4, 2025): Please remove the provider and install it again. Please try to install the latest version as well.
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@JAVA-LW commented on GitHub (Aug 4, 2025):

Please remove the provider and install it again. Please try to install the latest version as well.

This is the latest Docker version 1.7.1. I have deleted and reinstalled the plugin multiple times. Even when I directly pull down a new project, the issue persists

log：
[GIN] 2025/08/04 - 13:41:00 | 200 | 438.642µs | 172.18.0.8 | GET "/plugin/4c7b6371-efe1-4461-9bcb-6b9e9a875ee1/management/models?page=1&page_size=256"

2025/08/04 13:41:00 [Recovery] 2025/08/04 - 13:41:00 panic recovered:
runtime error: invalid memory address or nil pointer dereference
[GIN] 2025/08/04 - 13:41:00 | 500 | 1.051312ms | 172.18.0.8 | POST "/plugin/4c7b6371-efe1-4461-9bcb-6b9e9a875ee1/dispatch/model/schema"
/usr/local/go/src/runtime/panic.go:262 (0x4771b8)
/usr/local/go/src/runtime/signal_unix.go:917 (0x477188)
/app/internal/core/plugin_manager/local_runtime/stdio.go:85 (0xdbf0b2)
/app/internal/core/plugin_manager/local_runtime/io.go:16 (0xdbca1a)
/app/internal/core/plugin_daemon/generic.go:27 (0xfda4d6)
/app/internal/core/plugin_daemon/model.gen.go:161 (0x1008dab)
/app/internal/service/model.gen.go:210 (0x1008d92)
/app/internal/service/base_sse.go:116 (0x1013cfa)
/app/internal/service/base_sse.go:44 (0x1013f5e)
/app/internal/service/base_sse.go:114 (0x1013c44)
/app/internal/service/model.gen.go:208 (0x1008d51)
/app/internal/server/controllers/model.gen.go:163 (0x1ec7fa8)
/app/internal/server/controllers/base.go:53 (0x103de1b)
/app/internal/server/controllers/base.go:31 (0x103e281)
/app/internal/server/controllers/base.go:37 (0x103dd35)
/app/internal/server/controllers/model.gen.go:160 (0x1ec7ef3)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/middleware.go:170 (0x1ecaa33)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/middleware.go:97 (0x1ecaad3)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/middleware.go:66 (0x1ecedb1)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/controllers/health_check.go:28 (0x1eceaa4)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/middleware.go:24 (0x1eca1b4)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a)
/app/internal/server/controllers/health_check.go:20 (0x1ecea44)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf964ce)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/recovery.go:102 (0xf964bb)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf95604)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/logger.go:249 (0xf955eb)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf949f1)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633 (0xf94460)
/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589 (0xf93f91)
/usr/local/go/src/net/http/server.go:3210 (0x7e26cd)
/usr/local/go/src/net/http/server.go:2092 (0x7c1bef)
/usr/local/go/src/runtime/asm_amd64.s:1700 (0x47d3a0)

2025/08/04 13:42:23 full_duplex.go:65: [ERROR]init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds, retrying
2025/08/04 13:42:23 full_duplex.go:59: [INFO]init environment for plugin langgenius/deepseek:0.0.6
2025/08/04 13:44:23 full_duplex.go:65: [ERROR]init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds, retrying
2025/08/04 13:44:23 full_duplex.go:59: [INFO]init environment for plugin langgenius/deepseek:0.0.6

@JAVA-LW commented on GitHub (Aug 4, 2025): > Please remove the provider and install it again. Please try to install the latest version as well. This is the latest Docker version 1.7.1. I have deleted and reinstalled the plugin multiple times. Even when I directly pull down a new project, the issue persists log： [GIN] 2025/08/04 - 13:41:00 | 200 | 438.642µs | 172.18.0.8 | GET "/plugin/4c7b6371-efe1-4461-9bcb-6b9e9a875ee1/management/models?page=1&page_size=256" 2025/08/04 13:41:00 [Recovery] 2025/08/04 - 13:41:00 panic recovered: runtime error: invalid memory address or nil pointer dereference [GIN] 2025/08/04 - 13:41:00 | 500 | 1.051312ms | 172.18.0.8 | POST "/plugin/4c7b6371-efe1-4461-9bcb-6b9e9a875ee1/dispatch/model/schema" /usr/local/go/src/runtime/panic.go:262 (0x4771b8) /usr/local/go/src/runtime/signal_unix.go:917 (0x477188) /app/internal/core/plugin_manager/local_runtime/stdio.go:85 (0xdbf0b2) /app/internal/core/plugin_manager/local_runtime/io.go:16 (0xdbca1a) /app/internal/core/plugin_daemon/generic.go:27 (0xfda4d6) /app/internal/core/plugin_daemon/model.gen.go:161 (0x1008dab) /app/internal/service/model.gen.go:210 (0x1008d92) /app/internal/service/base_sse.go:116 (0x1013cfa) /app/internal/service/base_sse.go:44 (0x1013f5e) /app/internal/service/base_sse.go:114 (0x1013c44) /app/internal/service/model.gen.go:208 (0x1008d51) /app/internal/server/controllers/model.gen.go:163 (0x1ec7fa8) /app/internal/server/controllers/base.go:53 (0x103de1b) /app/internal/server/controllers/base.go:31 (0x103e281) /app/internal/server/controllers/base.go:37 (0x103dd35) /app/internal/server/controllers/model.gen.go:160 (0x1ec7ef3) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/middleware.go:170 (0x1ecaa33) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/middleware.go:97 (0x1ecaad3) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/middleware.go:66 (0x1ecedb1) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/controllers/health_check.go:28 (0x1eceaa4) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/middleware.go:24 (0x1eca1b4) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf8896a) /app/internal/server/controllers/health_check.go:20 (0x1ecea44) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf964ce) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/recovery.go:102 (0xf964bb) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf95604) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/logger.go:249 (0xf955eb) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185 (0xf949f1) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633 (0xf94460) /go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589 (0xf93f91) /usr/local/go/src/net/http/server.go:3210 (0x7e26cd) /usr/local/go/src/net/http/server.go:2092 (0x7c1bef) /usr/local/go/src/runtime/asm_amd64.s:1700 (0x47d3a0) 2025/08/04 13:42:23 full_duplex.go:65: [ERROR]init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds, retrying 2025/08/04 13:42:23 full_duplex.go:59: [INFO]init environment for plugin langgenius/deepseek:0.0.6 2025/08/04 13:44:23 full_duplex.go:65: [ERROR]init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds, retrying 2025/08/04 13:44:23 full_duplex.go:59: [INFO]init environment for plugin langgenius/deepseek:0.0.6
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 5, 2025):

It seems to be a general network issue, you can change the pypi mirror according to your needs.

@crazywoola commented on GitHub (Aug 5, 2025): It seems to be a general network issue, you can change the pypi mirror according to your needs.
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@JAVA-LW commented on GitHub (Aug 5, 2025):

It seems to be a general network issue, you can change the pypi mirror according to your needs.

yes，I set PIP_MIRROR_URL=PIP_MIRROR_URL=https://pypi.tuna.tsinghua.edu.cn/simple

but I solved it by migrating the database

@JAVA-LW commented on GitHub (Aug 5, 2025): > It seems to be a general network issue, you can change the pypi mirror according to your needs. yes，I set PIP_MIRROR_URL=PIP_MIRROR_URL=https://pypi.tuna.tsinghua.edu.cn/simple but I solved it by migrating the database
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@geeklx commented on GitHub (Aug 6, 2025):

这似乎是一个普遍的网络问题，您可以根据需要更改 pypi 镜像。

是的，我设置了 PIP_MIRROR_URL=PIP_MIRROR_URL= https://pypi.tuna.tsinghua.edu.cn/simple

但我通过迁移数据库解决了这个问题

how to solve it？

@geeklx commented on GitHub (Aug 6, 2025): > > 这似乎是一个普遍的网络问题，您可以根据需要更改 pypi 镜像。 > > 是的，我设置了 PIP_MIRROR_URL=PIP_MIRROR_URL= https://pypi.tuna.tsinghua.edu.cn/simple > > 但我通过迁移数据库解决了这个问题 how to solve it？
yindo commented 2026-02-21 19:23:42 -05:00
Author
Owner
Copy Link
Copy Source

@JAVA-LW commented on GitHub (Aug 7, 2025):

这似乎是一个普遍的网络问题，您可以根据需要更改 pypi 镜像。

是的，我设置了 PIP_MIRROR_URL=PIP_MIRROR_URL= https://pypi.tuna.tsinghua.edu.cn/simple
但我通过迁移数据库解决了这个问题

how to solve it？

You can try modifying the configuration file first. My situation is somewhat special, so I directly migrated the user and plugin configurations to the new deployment environment later

@JAVA-LW commented on GitHub (Aug 7, 2025): > > > 这似乎是一个普遍的网络问题，您可以根据需要更改 pypi 镜像。 > > > > > > 是的，我设置了 PIP_MIRROR_URL=PIP_MIRROR_URL= https://pypi.tuna.tsinghua.edu.cn/simple > > 但我通过迁移数据库解决了这个问题 > > how to solve it？ You can try modifying the configuration file first. My situation is somewhat special, so I directly migrated the user and plugin configurations to the new deployment environment later
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#15858
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?