langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

xxx models not exists #393

New Issue
Closed
opened 2026-02-16 10:19:16 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 10:19:16 -05:00
Owner
Copy Link
Copy Source

Originally created by @ywf on GitHub (Jun 23, 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.4.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Adding a large model via the Volcano Ark plugin shows a success prompt, but the model is not displayed.

✔️ Expected Behavior

Volcano's large model can be properly added.

❌ Actual Behavior

Not showing the model

Image

Image

Originally created by @ywf on GitHub (Jun 23, 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.4.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Adding a large model via the Volcano Ark plugin shows a success prompt, but the model is not displayed. ### ✔️ Expected Behavior Volcano's large model can be properly added. ### ❌ Actual Behavior Not showing the model ![Image](https://github.com/user-attachments/assets/454f902b-308b-4467-8cec-c0fc358a000d) ![Image](https://github.com/user-attachments/assets/f65ef85b-27ae-441b-b787-ffdf54fc0312)
yindo closed this issue 2026-02-16 10:19:16 -05:00
yindo commented 2026-02-16 10:19:17 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 23, 2025):

This issue is common in self-hosted Docker setups when adding models via plugins like Volcano Ark. The most likely causes are network or configuration problems between your Dify containers and the plugin daemon. Here’s a focused checklist to help you troubleshoot:

  • Make sure you are not using localhost or 127.0.0.1 for any service endpoints in your Docker environment. Use host.docker.internal or your host’s internal IP instead, so containers can communicate properly [source].
  • Double-check your environment variables: PLUGIN_DAEMON_URL should point to the correct host and port (e.g., http://host.docker.internal:5002), and SANDBOX_ENABLE_NETWORK should be set to true [source].
  • If you migrated or copied your Docker environment, remove and reinstall the plugin after confirming network access is available. Sometimes plugins need to be re-initialized to register models correctly [source].
  • The plugin may need outbound internet access the first time it runs to install dependencies. If your network blocks this, the plugin can’t finish setup and models won’t appear [source].
  • Check that the plugin daemon and Dify containers are on the same Docker network.
  • In the Dify admin interface, confirm the plugin is installed and the models are listed. If not, there may be a registration or network issue.
  • If you see errors like “model XXX not exists” in logs, it usually means the model wasn’t registered or enabled on the backend. Check your Docker logs for errors from the plugin daemon or Dify API containers for more details [source].

If you’ve checked all of the above and the model still doesn’t appear, please share any relevant error logs from your Docker containers for deeper diagnosis.

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Jun 23, 2025): <!-- Answer --> This issue is common in self-hosted Docker setups when adding models via plugins like Volcano Ark. The most likely causes are network or configuration problems between your Dify containers and the plugin daemon. Here’s a focused checklist to help you troubleshoot: - Make sure you are not using `localhost` or `127.0.0.1` for any service endpoints in your Docker environment. Use `host.docker.internal` or your host’s internal IP instead, so containers can communicate properly [[source]](https://github.com/langgenius/dify/issues/20325). - Double-check your environment variables: `PLUGIN_DAEMON_URL` should point to the correct host and port (e.g., `http://host.docker.internal:5002`), and `SANDBOX_ENABLE_NETWORK` should be set to `true` [[source]](https://github.com/langgenius/dify/issues/20325). - If you migrated or copied your Docker environment, remove and reinstall the plugin after confirming network access is available. Sometimes plugins need to be re-initialized to register models correctly [[source]](https://github.com/langgenius/dify/issues/19481). - The plugin may need outbound internet access the first time it runs to install dependencies. If your network blocks this, the plugin can’t finish setup and models won’t appear [[source]](https://github.com/langgenius/dify/issues/20325). - Check that the plugin daemon and Dify containers are on the same Docker network. - In the Dify admin interface, confirm the plugin is installed and the models are listed. If not, there may be a registration or network issue. - If you see errors like “model XXX not exists” in logs, it usually means the model wasn’t registered or enabled on the backend. Check your Docker logs for errors from the plugin daemon or Dify API containers for more details [[source]](https://github.com/langgenius/dify/pull/20843). If you’ve checked all of the above and the model still doesn’t appear, please share any relevant error logs from your Docker containers for deeper diagnosis. <!-- 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/b57e68db-fe40-4b1c-93ca-0d9a77071933?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b57e68db-fe40-4b1c-93ca-0d9a77071933?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b57e68db-fe40-4b1c-93ca-0d9a77071933?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b57e68db-fe40-4b1c-93ca-0d9a77071933?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b57e68db-fe40-4b1c-93ca-0d9a77071933?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b57e68db-fe40-4b1c-93ca-0d9a77071933?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b57e68db-fe40-4b1c-93ca-0d9a77071933?feedback_type=other)</sup>&nbsp;&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/21363)
yindo commented 2026-02-16 10:19:17 -05:00
Author
Owner
Copy Link
Copy Source

@ywf commented on GitHub (Jun 23, 2025):

Thank you. I upgraded from version 1.4.0 to 1.4.3 by reusing the volumes directory and .env file from the 1.4.0 installation. Here's the detailed process:

Ran docker compose down

Deleted the original volumes directory, then replaced it along with the .env file from the 1.4.0 version

Executed docker compose up -d

After logging in, the version shows as 1.4.3, and the workflows and plugins from 1.4.0 are visible on the interface. However, when attempting to add a large model using the Volcano Ark plugin, the operation failed.

Was this upgrade procedure incorrect?

@ywf commented on GitHub (Jun 23, 2025): Thank you. I upgraded from version 1.4.0 to 1.4.3 by reusing the volumes directory and .env file from the 1.4.0 installation. Here's the detailed process: Ran docker compose down Deleted the original volumes directory, then replaced it along with the .env file from the 1.4.0 version Executed docker compose up -d After logging in, the version shows as 1.4.3, and the workflows and plugins from 1.4.0 are visible on the interface. However, when attempting to add a large model using the Volcano Ark plugin, the operation failed. Was this upgrade procedure incorrect?
yindo commented 2026-02-16 10:19:17 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 23, 2025):

Your upgrade procedure missed a key step: after replacing or deleting Docker volumes, you need to run specific migration commands to restore plugin and model data. Simply copying the volumes and .env file is not enough—this will result in missing models and plugins, even if the UI appears normal and workflows/plugins are listed.

The official upgrade process requires you to:

  1. Stop Docker services and back up your data.
  2. Update your .env file to match the latest .env.example (to ensure compatibility).
  3. Run these migration commands inside your Docker environment: 
    uv run flask extract-plugins --workers=20
uv run flask install-plugins --workers=2
uv run flask migrate-data-for-plugin

These commands extract, reinstall, and migrate all plugin and model data. Skipping them means your environment will not have the necessary backend records for plugins and models, which is why adding a model via the Volcano Ark plugin fails to register or display in the UI—even if you see a success prompt.

You can find more details and step-by-step instructions in the official migration guide.

If you still have your old data, restore it and follow the migration steps above. If not, you may need to reinstall plugins and re-add models manually.

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Jun 23, 2025): <!-- Answer --> Your upgrade procedure missed a key step: after replacing or deleting Docker volumes, you need to run specific migration commands to restore plugin and model data. Simply copying the volumes and .env file is not enough—this will result in missing models and plugins, even if the UI appears normal and workflows/plugins are listed. The official upgrade process requires you to: 1. Stop Docker services and back up your data. 2. Update your .env file to match the latest .env.example (to ensure compatibility). 3. Run these migration commands inside your Docker environment: ``` uv run flask extract-plugins --workers=20 uv run flask install-plugins --workers=2 uv run flask migrate-data-for-plugin ``` These commands extract, reinstall, and migrate all plugin and model data. Skipping them means your environment will not have the necessary backend records for plugins and models, which is why adding a model via the Volcano Ark plugin fails to register or display in the UI—even if you see a success prompt. You can find more details and step-by-step instructions in the [official migration guide](https://github.com/crazywoola/dify-docs-mintlify/blob/766ba4baea07dd783e72dcc745d2a4cffd03d2e8/en/development/migration/migrate-to-v1.mdx). If you still have your old data, restore it and follow the migration steps above. If not, you may need to reinstall plugins and re-add models manually. <!-- 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/ca7db134-6be7-4a9d-80c7-de53692cbd4a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ca7db134-6be7-4a9d-80c7-de53692cbd4a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ca7db134-6be7-4a9d-80c7-de53692cbd4a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ca7db134-6be7-4a9d-80c7-de53692cbd4a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ca7db134-6be7-4a9d-80c7-de53692cbd4a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ca7db134-6be7-4a9d-80c7-de53692cbd4a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ca7db134-6be7-4a9d-80c7-de53692cbd4a?feedback_type=other)</sup>&nbsp;&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/21363)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
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-official-plugins#393
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?