langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-25 13:36:01 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[Bug] Volcengine models not showing after being added #20072

New Issue
Closed
opened 2026-02-21 20:05:43 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:05:43 -05:00
Owner
Copy Link
Copy Source

Originally created by @pangpang20 on GitHub (Nov 1, 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

v1.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After adding two models in Volcengine, they do not appear in the model list, although they can be seen in the management panel.
Image

Image

✔️ Expected Behavior

Show models in Volcengine

❌ Actual Behavior

No models showed in Volcengine

Originally created by @pangpang20 on GitHub (Nov 1, 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 v1.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After adding two models in Volcengine, they do not appear in the model list, although they can be seen in the management panel. <img width="1252" height="595" alt="Image" src="https://github.com/user-attachments/assets/cf7b4480-6eee-4b93-b78d-3d3ffa139855" /> <img width="1553" height="431" alt="Image" src="https://github.com/user-attachments/assets/514fabe2-e8d6-4d7b-a8bc-baf02c3e9fe0" /> ### ✔️ Expected Behavior Show models in Volcengine ### ❌ Actual Behavior No models showed in Volcengine
yindo added the 🐞 bug label 2026-02-21 20:05:43 -05:00
yindo closed this issue 2026-02-21 20:05:43 -05:00
yindo commented 2026-02-21 20:05:43 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @pangpang20! I'm Dosu and I’m helping the dify team.

This is a known issue in Dify self-hosted Docker setups: models added via Volcengine (and some other plugins) can appear in the management panel but not in the main model list due to how model registration and filtering work in the backend and frontend. The most common causes are:

  • The models are not marked as enabled/active in the database, so they are filtered out of the user-facing list. This can happen if there was a silent failure during model addition, a missed migration step, or a network/configuration issue between the Dify containers and the plugin daemon [source].
  • If you recently upgraded, migrated, or restored your Docker environment, you need to run the following migration commands inside your Docker environment to ensure all plugins and models are properly registered: 
    uv run flask extract-plugins --workers=20
uv run flask install-plugins --workers=2
uv run flask migrate-data-for-plugin
    Skipping these can result in missing backend records, causing the UI to show zero models even after successful parameter entry [source].
  • Double-check that your Docker network configuration does not use localhost or 127.0.0.1 for service endpoints. Use your host's internal IP or host.docker.internal instead, and ensure PLUGIN_DAEMON_URL and SANDBOX_ENABLE_NETWORK=true are set correctly [source].
  • Check Docker and plugin daemon logs for errors like “model XXX not exists” or “PluginDaemonInternalServerError” during model registration [source].

If the models are visible in the management panel but not in the main list, it's likely they are not enabled or not marked as valid in the backend. You can inspect your database for ProviderModel records and ensure they are enabled and not deprecated, or try removing and re-adding the models after confirming network and migration steps are correct [source].

Let me know if you need more detailed steps for checking the logs or database.

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 (Nov 1, 2025): <!-- Greeting --> Hi @pangpang20! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This is a known issue in Dify self-hosted Docker setups: models added via Volcengine (and some other plugins) can appear in the management panel but not in the main model list due to how model registration and filtering work in the backend and frontend. The most common causes are: - The models are not marked as enabled/active in the database, so they are filtered out of the user-facing list. This can happen if there was a silent failure during model addition, a missed migration step, or a network/configuration issue between the Dify containers and the plugin daemon [[source]](https://github.com/langgenius/dify/issues/25996). - If you recently upgraded, migrated, or restored your Docker environment, you need to run the following migration commands inside your Docker environment to ensure all plugins and models are properly registered: ``` uv run flask extract-plugins --workers=20 uv run flask install-plugins --workers=2 uv run flask migrate-data-for-plugin ``` Skipping these can result in missing backend records, causing the UI to show zero models even after successful parameter entry [[source]](https://github.com/langgenius/dify/issues/25996). - Double-check that your Docker network configuration does not use `localhost` or `127.0.0.1` for service endpoints. Use your host's internal IP or `host.docker.internal` instead, and ensure `PLUGIN_DAEMON_URL` and `SANDBOX_ENABLE_NETWORK=true` are set correctly [[source]](https://github.com/langgenius/dify/issues/21363). - Check Docker and plugin daemon logs for errors like “model XXX not exists” or “PluginDaemonInternalServerError” during model registration [[source]](https://github.com/langgenius/dify/issues/25996). If the models are visible in the management panel but not in the main list, it's likely they are not enabled or not marked as valid in the backend. You can inspect your database for ProviderModel records and ensure they are enabled and not deprecated, or try removing and re-adding the models after confirming network and migration steps are correct [[source]](https://github.com/langgenius/dify/issues/25747). Let me know if you need more detailed steps for checking the logs or database. <!-- 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/1f42d691-0b26-46ad-86e6-16452926c9d3?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1f42d691-0b26-46ad-86e6-16452926c9d3?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1f42d691-0b26-46ad-86e6-16452926c9d3?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1f42d691-0b26-46ad-86e6-16452926c9d3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1f42d691-0b26-46ad-86e6-16452926c9d3?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1f42d691-0b26-46ad-86e6-16452926c9d3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1f42d691-0b26-46ad-86e6-16452926c9d3?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/27715)
yindo commented 2026-02-21 20:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@hanhaiszw commented on GitHub (Nov 1, 2025):

Same problem

@hanhaiszw commented on GitHub (Nov 1, 2025): Same problem
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#20072
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?