保存ollama模型时,没有反应,查看NetWork的models已经超时 #12514

Closed
opened 2026-02-21 19:07:45 -05:00 by yindo · 2 comments
Owner

Originally created by @DaweiTom on GitHub (Apr 3, 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

main

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @DaweiTom on GitHub (Apr 3, 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 main ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/c53869b4-820b-45fb-9284-36edb932ab4d) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🤔 cant-reproduce label 2026-02-21 19:07:45 -05:00
yindo closed this issue 2026-02-21 19:07:45 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Apr 3, 2025):

Hello, @DaweiTom! I'm here to help you with any bugs, questions, or contributions you might have. Let's tackle this issue together!

I found some similar discussions that might be relevant to your issue:

  1. What is the reason for the request timed out when saving the model? - This discussion is still open and might provide insights into the timeout issue you're experiencing [1].

  2. Run failed: [models] Connection Error, HTTPConnectionPool(host='172.26.27.223', port=11434): Read timed out. (read timeout=300) - This is another open discussion that deals with connection errors and timeouts, which could be related to your problem [2].

To address the issue of no response when saving the Ollama model and network requests timing out, you can try the following steps:

  • Configure the environment variables in your .env file as follows:

    PROVIDER_OLLAMA_API_BASE_URL=http://host.docker.internal:11434/
    PLUGIN_WORKING_PATH=/app/cwd
    
  • If you are deploying Dify in an offline environment, consider downgrading to Dify version 0.15.3, which has been confirmed to work successfully with Ollama model configuration in offline environments [3].

  • Modify the docker-compose.yaml file for the plugin_daemon service by adding or updating the following environment variable to increase the timeout limit:

    plugin_daemon:
      environment:
        PLUGIN_MAX_EXECUTION_TIMEOUT: 2400
    

After making these changes, restart your Docker containers. This should help resolve the timeout issues with the Ollama model [3].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 3, 2025): <!-- Greeting --> Hello, @DaweiTom! I'm here to help you with any bugs, questions, or contributions you might have. Let's tackle this issue together! <!-- Answer --> I found some similar discussions that might be relevant to your issue: 1. [What is the reason for the request timed out when saving the model?](https://github.com/langgenius/dify/discussions/14017) - This discussion is still open and might provide insights into the timeout issue you're experiencing <sup>[[1]](https://github.com/langgenius/dify/discussions/14017)</sup>. 2. [Run failed: [models] Connection Error, HTTPConnectionPool(host='172.26.27.223', port=11434): Read timed out. (read timeout=300)](https://github.com/langgenius/dify/discussions/16116) - This is another open discussion that deals with connection errors and timeouts, which could be related to your problem <sup>[[2]](https://github.com/langgenius/dify/discussions/16116)</sup>. To address the issue of no response when saving the Ollama model and network requests timing out, you can try the following steps: - Configure the environment variables in your `.env` file as follows: ```plaintext PROVIDER_OLLAMA_API_BASE_URL=http://host.docker.internal:11434/ PLUGIN_WORKING_PATH=/app/cwd ``` - If you are deploying Dify in an offline environment, consider downgrading to Dify version 0.15.3, which has been confirmed to work successfully with Ollama model configuration in offline environments <sup>[[3]](https://github.com/langgenius/dify/issues/15538)</sup>. - Modify the `docker-compose.yaml` file for the `plugin_daemon` service by adding or updating the following environment variable to increase the timeout limit: ```yaml plugin_daemon: environment: PLUGIN_MAX_EXECUTION_TIMEOUT: 2400 ``` After making these changes, restart your Docker containers. This should help resolve the timeout issues with the Ollama model <sup>[[3]](https://github.com/langgenius/dify/issues/15538)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/1eb7ffa1-f7b0-4189-beb4-61bedd4c0b37?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/1eb7ffa1-f7b0-4189-beb4-61bedd4c0b37?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/1eb7ffa1-f7b0-4189-beb4-61bedd4c0b37?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/1eb7ffa1-f7b0-4189-beb4-61bedd4c0b37?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1eb7ffa1-f7b0-4189-beb4-61bedd4c0b37?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/1eb7ffa1-f7b0-4189-beb4-61bedd4c0b37?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1eb7ffa1-f7b0-4189-beb4-61bedd4c0b37?feedback_type=other)</sup>
Author
Owner

@q785383749 commented on GitHub (Apr 25, 2025):

I installed dify1.2.0 and the latest version of ollama 0.6.5 in an offline environment, and also installed the model. I confirmed that ollama has been started and can be launched in a dialogue from the command line, and then downloaded the offline ollama plugin from dify. When adding a model after successful installation, sometimes it prompts "{" message ":" Internal Server Error "," code ":" unknown "}", and the console log shows an error: "Plugin Daemon Internal Server Error: no available node, plugin not found". Sometimes clicking to add a model does not respond, but I did not encounter this issue in the 0.15.x dify version

@q785383749 commented on GitHub (Apr 25, 2025): I installed dify1.2.0 and the latest version of ollama 0.6.5 in an offline environment, and also installed the model. I confirmed that ollama has been started and can be launched in a dialogue from the command line, and then downloaded the offline ollama plugin from dify. When adding a model after successful installation, sometimes it prompts "{" message ":" Internal Server Error "," code ":" unknown "}", and the console log shows an error: "Plugin Daemon Internal Server Error: no available node, plugin not found". Sometimes clicking to add a model does not respond, but I did not encounter this issue in the 0.15.x dify version
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#12514