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

After installing the model provider, it is impossible to configure the local model api or the key of the external model. #20463

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

Originally created by @xuanjianpengpeng on GitHub (Nov 20, 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.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After installing the Ollama and DeepSeek plugins, it should be possible to configure the model invocation settings. However, the button for this configuration is not displayed, making it impossible to set up the model information.

I conducted some tests and encountered two issues:

Errors occurred frequently during the plugin installation process. However, I managed to successfully install the plugins by first downloading the installation package and then installing them locally.

Previously, I deployed the Dify service using Docker on server A. After the above attempts, I installed the plugins and configured the model invocation settings, including the local Ollama and DeepSeek official keys, both of which worked correctly.

Subsequently, I deployed Dify on server B (a virtual machine with the same version as server A) using Docker as well, and it worked normally.

The issue arose when I deleted the "volumes" data directory of Dify on server A, intending to reset and reuse Dify. However, even after successfully reinstalling the plugins, I was still unable to configure the model invocation settings. What could be the problem here?

To troubleshoot further, I created a new directory named "dify2" at the same level as the original Dify directory on server A, pulled the code again, and redeployed it. Yet, I still couldn't install and use the plugins properly.

Is there something wrong with my operations? How should I troubleshoot this issue? What should be my next steps?

✔️ Expected Behavior

Normally, the configuration button is displayed, allowing for configuration.

Image

❌ Actual Behavior

The configuration button is not displayed.

Image Image
Originally created by @xuanjianpengpeng on GitHub (Nov 20, 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.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After installing the Ollama and DeepSeek plugins, it should be possible to configure the model invocation settings. However, the button for this configuration is not displayed, making it impossible to set up the model information. I conducted some tests and encountered two issues: Errors occurred frequently during the plugin installation process. However, I managed to successfully install the plugins by first downloading the installation package and then installing them locally. Previously, I deployed the Dify service using Docker on server A. After the above attempts, I installed the plugins and configured the model invocation settings, including the local Ollama and DeepSeek official keys, both of which worked correctly. Subsequently, I deployed Dify on server B (a virtual machine with the same version as server A) using Docker as well, and it worked normally. The issue arose when I deleted the "volumes" data directory of Dify on server A, intending to reset and reuse Dify. However, even after successfully reinstalling the plugins, I was still unable to configure the model invocation settings. What could be the problem here? To troubleshoot further, I created a new directory named "dify2" at the same level as the original Dify directory on server A, pulled the code again, and redeployed it. Yet, I still couldn't install and use the plugins properly. Is there something wrong with my operations? How should I troubleshoot this issue? What should be my next steps? ### ✔️ Expected Behavior Normally, the configuration button is displayed, allowing for configuration. <img width="3840" height="1919" alt="Image" src="https://github.com/user-attachments/assets/23350186-3785-4d4e-ba3e-392bc451d974" /> ### ❌ Actual Behavior The configuration button is not displayed. <img width="3840" height="1919" alt="Image" src="https://github.com/user-attachments/assets/c3dcc9ca-a9f1-4716-8034-4938364c2fb9" /> <img width="3840" height="1919" alt="Image" src="https://github.com/user-attachments/assets/a15e8d8c-c5dc-44c3-972d-653cde2dff7b" />
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 20:07:33 -05:00
yindo closed this issue 2026-02-21 20:07:33 -05:00
yindo commented 2026-02-21 20:07:33 -05:00
Author
Owner
Copy Link
Copy Source

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

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

The missing configuration button is almost always caused by incomplete or missing backend state for the model provider after a volume reset or plugin installation error. The UI only shows the configuration button if the backend reports the provider as properly registered and ready for configuration. If the provider's status is not "active" (for example, if plugin registration failed or the backend can't find the provider's credential schema), the button won't appear and you'll see warnings about incomplete configuration.

To fix this, check these points:

  • Make sure you are not using localhost or 127.0.0.1 for any service endpoints in your Docker setup. Use host.docker.internal or your host's LAN IP so containers can communicate.
  • Double-check your environment variables: PLUGIN_DAEMON_URL should point to the correct host and port, and SANDBOX_ENABLE_NETWORK should be set to true.
  • After resetting volumes or copying environments, you must run these migration commands inside Docker to extract, install, and migrate plugin and model data: 
    uv run flask extract-plugins --workers=20
uv run flask install-plugins --workers=2
uv run flask migrate-data-for-plugin
    Skipping these steps can cause models and configuration buttons not to appear, even if the UI says the plugin was installed successfully.
  • Make sure the plugin daemon and Dify containers are on the same Docker network.
  • Check both the Dify API and plugin daemon logs for errors during plugin installation or model provider registration—look for credential validation failures, schema mismatches, or plugin daemon response errors.
  • The plugin may need outbound internet access the first time it runs to install dependencies. If your network blocks this, plugin setup can silently fail and models won't appear.

If you see a red error box about "Reached maximum retries" for a plugin download, that's a sign of network or authentication issues blocking plugin registration, which will also prevent the configuration button from appearing.

Following these steps should restore the configuration UI and let you set up your model providers again. For more details and troubleshooting context, see this discussion and this checklist.

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 20, 2025): <!-- Greeting --> Hi @xuanjianpengpeng! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The missing configuration button is almost always caused by incomplete or missing backend state for the model provider after a volume reset or plugin installation error. The UI only shows the configuration button if the backend reports the provider as properly registered and ready for configuration. If the provider's status is not "active" (for example, if plugin registration failed or the backend can't find the provider's credential schema), the button won't appear and you'll see warnings about incomplete configuration. To fix this, check these points: - Make sure you are not using `localhost` or `127.0.0.1` for any service endpoints in your Docker setup. Use `host.docker.internal` or your host's LAN IP so containers can communicate. - Double-check your environment variables: `PLUGIN_DAEMON_URL` should point to the correct host and port, and `SANDBOX_ENABLE_NETWORK` should be set to `true`. - After resetting volumes or copying environments, you must run these migration commands inside Docker to extract, install, and migrate plugin and model data: ``` uv run flask extract-plugins --workers=20 uv run flask install-plugins --workers=2 uv run flask migrate-data-for-plugin ``` Skipping these steps can cause models and configuration buttons not to appear, even if the UI says the plugin was installed successfully. - Make sure the plugin daemon and Dify containers are on the same Docker network. - Check both the Dify API and plugin daemon logs for errors during plugin installation or model provider registration—look for credential validation failures, schema mismatches, or plugin daemon response errors. - The plugin may need outbound internet access the first time it runs to install dependencies. If your network blocks this, plugin setup can silently fail and models won't appear. If you see a red error box about "Reached maximum retries" for a plugin download, that's a sign of network or authentication issues blocking plugin registration, which will also prevent the configuration button from appearing. Following these steps should restore the configuration UI and let you set up your model providers again. For more details and troubleshooting context, see [this discussion](https://github.com/langgenius/dify-official-plugins/issues/1518) and [this checklist](https://github.com/langgenius/dify-official-plugins/issues/1542). <!-- 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/281c39ad-5ee9-429d-9323-7c94733c9a0d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/281c39ad-5ee9-429d-9323-7c94733c9a0d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/281c39ad-5ee9-429d-9323-7c94733c9a0d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/281c39ad-5ee9-429d-9323-7c94733c9a0d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/281c39ad-5ee9-429d-9323-7c94733c9a0d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/281c39ad-5ee9-429d-9323-7c94733c9a0d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/281c39ad-5ee9-429d-9323-7c94733c9a0d?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/28485)
yindo commented 2026-02-21 20:07:33 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 20, 2025):

Image

can not reproduce this in the latest branch.

@crazywoola commented on GitHub (Nov 20, 2025): <img width="2100" height="1386" alt="Image" src="https://github.com/user-attachments/assets/1ffe1141-7e8c-43fa-a957-246c8d933a61" /> can not reproduce this in the latest branch.
yindo commented 2026-02-21 20:07:33 -05:00
Author
Owner
Copy Link
Copy Source

@xuanjianpengpeng commented on GitHub (Nov 21, 2025):

The latest test shows that after deleting the "volumes" directory and restarting the service, the local model call information configured for the Ollama plugin appears like this: it does not display the newly added model list, only the model credential information is visible. However, this setup is not functional. Could it be an issue with the network communication configuration? How can this be troubleshooted?

Image
@xuanjianpengpeng commented on GitHub (Nov 21, 2025): The latest test shows that after deleting the "volumes" directory and restarting the service, the local model call information configured for the Ollama plugin appears like this: it does not display the newly added model list, only the model credential information is visible. However, this setup is not functional. Could it be an issue with the network communication configuration? How can this be troubleshooted? <img width="3840" height="1919" alt="Image" src="https://github.com/user-attachments/assets/151fd6bc-f3fa-4cce-9521-a073a30641d6" />
yindo commented 2026-02-21 20:07:33 -05:00
Author
Owner
Copy Link
Copy Source

@yeshenlougu commented on GitHub (Nov 27, 2025):

I pull the latest,in a new dictory and set the .env. It works correctly.

@yeshenlougu commented on GitHub (Nov 27, 2025): I pull the latest,in a new dictory and set the .env. It works correctly.
yindo commented 2026-02-21 20:07:34 -05:00
Author
Owner
Copy Link
Copy Source

@zzc9psxvw2-oss commented on GitHub (Dec 11, 2025):

I pull the latest,in a new dictory and set the .env. It works correctly.

How exactly do you operate?

@zzc9psxvw2-oss commented on GitHub (Dec 11, 2025): > I pull the latest,in a new dictory and set the .env. It works correctly. How exactly do you operate?
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#20463
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?