langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

the new version opena ai compatible plugin can not show any existed LLM #925

New Issue
Closed
opened 2026-02-16 10:21:01 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:21:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @simonjhy on GitHub (Jan 7, 2026).

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 Dify issues & Dify Official Plugins, 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.11.1

Plugin version

0.0.29

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

While I upgrade open ai compatible plugin to 0.0.30, the installed LLM instance will be dispear.

✔️ Error log

No response

Originally created by @simonjhy on GitHub (Jan 7, 2026). ### 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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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.11.1 ### Plugin version 0.0.29 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce While I upgrade open ai compatible plugin to 0.0.30, the installed LLM instance will be dispear. ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:21:01 -05:00
yindo closed this issue 2026-02-16 10:21:01 -05:00
yindo commented 2026-02-16 10:21:02 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 7, 2026):

This is a known issue that has affected multiple Dify versions: after upgrading certain model plugins (including the OpenAI-compatible plugin), all existing LLM configurations can disappear, especially in self-hosted Docker setups. The root cause is usually changes in the plugin's credential schema or registration logic, which can invalidate or hide previously saved entries. There is no built-in migration or recovery script for this scenario, and the official plugin documentation does not provide manual restoration steps.

To restore missing LLM instances, check that the plugin daemon is running and that the plugin is registered in the Dify UI or via API. If the LLMs are still missing, you will need to re-register or re-install the affected plugins and reconfigure your LLM instances. This is sometimes necessary because plugin identifiers or registration requirements may change between versions, and plugin files or dependencies can be lost during upgrades—especially with Docker volumes or persistent storage. Maintainers have also suggested removing and reinstalling plugins if dependency installation failed during the upgrade process. For future upgrades, it's recommended to follow the official migration guides and back up your data to minimize the risk of data loss during plugin or platform upgrades.

References:

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 7, 2026): <!-- Answer --> This is a known issue that has affected multiple Dify versions: after upgrading certain model plugins (including the OpenAI-compatible plugin), all existing LLM configurations can disappear, especially in self-hosted Docker setups. The root cause is usually changes in the plugin's credential schema or registration logic, which can invalidate or hide previously saved entries. There is no built-in migration or recovery script for this scenario, and the official plugin documentation does not provide manual restoration steps. To restore missing LLM instances, check that the plugin daemon is running and that the plugin is registered in the Dify UI or via API. If the LLMs are still missing, you will need to re-register or re-install the affected plugins and reconfigure your LLM instances. This is sometimes necessary because plugin identifiers or registration requirements may change between versions, and plugin files or dependencies can be lost during upgrades—especially with Docker volumes or persistent storage. Maintainers have also suggested removing and reinstalling plugins if dependency installation failed during the upgrade process. For future upgrades, it's recommended to follow the official migration guides and back up your data to minimize the risk of data loss during plugin or platform upgrades. References: - [Known issue: model configurations lost after plugin upgrade](https://github.com/langgenius/dify/issues/18171#issuecomment-2808747502) - [Plugin daemon and re-registration advice](https://github.com/langgenius/dify/issues/21865) - [No manual recovery steps in plugin docs](https://github.com/langgenius/dify-official-plugins/blob/b9aa7f0cda7432c554170618787721aa41b33fad/extensions/openai_compatible/README.md) <!-- 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/a868be54-f553-4b9c-a139-048bea5829d6?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a868be54-f553-4b9c-a139-048bea5829d6?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a868be54-f553-4b9c-a139-048bea5829d6?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a868be54-f553-4b9c-a139-048bea5829d6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a868be54-f553-4b9c-a139-048bea5829d6?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a868be54-f553-4b9c-a139-048bea5829d6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a868be54-f553-4b9c-a139-048bea5829d6?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20that%20has%20affected%20multiple%20Dify%20versions%3A%20after%20upgrading%20certain%20model%20plugins%20%28including%20the%20OpenAI-compatible%20plugin%29%2C%20all%20existing%20LLM%20configurations%20can%20disappear%2C%20especially%20in%20self-hosted%20Docker%20setups.%20The%20root%20cause%20is%20usually%20changes%20in%20the%20plugin%27s%20credential%20schema%20or%20registration%20logic%2C%20which%20can%20invalidate%20or%20hide%20previously%20saved%20entries.%20There%20is%20no%20built-in%20migration%20or%20recovery%20script%20for%20this%20scenario%2C%20and%20the%20official%20plugin%20documentation%20does%20not%20provide%20manual%20restoration%20steps.%0A%0ATo%20restore%20missing%20LLM%20instances%2C%20check%20that%20the%20plugin%20daemon%20is%20running%20and%20that%20the%20plugin%20is%20registered%20in%20the%20Dify%20UI%20or%20via%20API.%20If%20the%20LLMs%20are%20still%20missing%2C%20you%20will%20need%20to%20re-register%20or%20re-install%20the%20affected%20plugins%20and%20reconfigure%20your%20LLM%20instances.%20This%20is%20sometimes%20necessary%20because%20plugin%20identifiers%20or%20registration%20requirements%20may%20change%20between%20versions%2C%20and%20plugin%20files%20or%20dependencies%20can%20be%20lost%20during%20upgrades%E2%80%94especially%20with%20Docker%20volumes%20or%20persistent%20storage.%20Maintainers%20have%20also%20suggested%20removing%20and%20reinstalling%20plugins%20if%20dependency%20installation%20failed%20during%20the%20upgrade%20process.%20For%20future%20upgrades%2C%20it%27s%20recommended%20to%20follow%20the%20official%20migration%20guides%20and%20back%20up%20your%20data%20to%20minimize%20the%20risk%20of%20data%20loss%20during%20plugin%20or%20platform%20upgrades.%0A%0AReferences%3A%20%20%0A-%20%5BKnown%20issue%3A%20model%20configurations%20lost%20after%20plugin%20upgrade%5D%28https%3A//github.com/langgenius/dify/issues/18171%23issuecomment-2808747502%29%20%20%0A-%20%5BPlugin%20daemon%20and%20re-registration%20advice%5D%28https%3A//github.com/langgenius/dify/issues/21865%29%20%20%0A-%20%5BNo%20manual%20recovery%20steps%20in%20plugin%20docs%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/b9aa7f0cda7432c554170618787721aa41b33fad/extensions/openai_compatible/README.md%29)&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-official-plugins/issues/2383)
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 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-official-plugins#925
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?