langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

1 validation error for DifyPluginEnv REMOTE_INSTALL_URL #13843

New Issue
Closed
opened 2026-02-21 19:14:09 -05:00 by yindo · 6 comments
yindo commented 2026-02-21 19:14:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @tigflanker on GitHub (May 13, 2025).

Originally assigned to: @crazywoola on GitHub.

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

v1.3.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I encountered a looping installation failure error when installing the Ollama plugin offline using the latest Docker version (1.3.1):

plugin_daemon-1  | 2025/05/14 01:20:35 run.go:144: [INFO]plugin langgenius/ollama:0.0.6 started
plugin_daemon-1  | 2025/05/14 01:20:36 run.go:132: [ERROR]plugin langgenius/ollama:0.0.6 exited with error: exit status 1
plugin_daemon-1  | dcdf5589fdf5d01a995533f956853c69c54eddcf797006fa37/main.py", line 3, in <module>
plugin_daemon-1  | 
plugin_daemon-1  |     plugin = Plugin(DifyPluginEnv())
plugin_daemon-1  |                     ^^^^^^^^^^^^^^^
plugin_daemon-1  | 
plugin_daemon-1  |   File "/app/storage/cwd/langgenius/ollama-0.0.6@7d66a960a68cafdcdf5589fdf5d01a995533f956853c69c54eddcf797006fa37/.venv/lib/python3.12/site-packages/pydantic_settings/main.py", line 176, in __init__
plugin_daemon-1  | 
plugin_daemon-1  |     super().__init__(
plugin_daemon-1  |   File "/app/storage/cwd/langgenius/ollama-0.0.6@7d66a960a68cafdcdf5589fdf5d01a995533f956853c69c54eddcf797006fa37/.venv/lib/python3.12/site-packages/pydantic/main.py", line 253, in __init__
plugin_daemon-1  | 
plugin_daemon-1  |     validated_self = self.__pydantic_validator__.validate_python(data, self_instance=self)
plugin_daemon-1  | 
plugin_daemon-1  |                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
plugin_daemon-1  | 
plugin_daemon-1  | pydantic_core._pydantic_core.ValidationError: 1 validation error for DifyPluginEnv
plugin_daemon-1  | REMOTE_INSTALL_URL
plugin_daemon-1  |   Field required [type=missing, input_value={'INSTALL_METHOD': 'local'}, input_type=dict]
plugin_daemon-1  |     For further information visit https://errors.pydantic.dev/2.11/v/missing
plugin_daemon-1  | 
plugin_daemon-1  | 
plugin_daemon-1  | 
plugin_daemon-1  | 2025/05/14 01:20:36 run.go:182: [INFO]plugin langgenius/ollama:0.0.6 stopped

@dosu Could you please help me find similar cases and solutions?

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @tigflanker on GitHub (May 13, 2025). Originally assigned to: @crazywoola on GitHub. ### 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 v1.3.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I encountered a looping installation failure error when installing the Ollama plugin offline using the latest Docker version (1.3.1): ``` plugin_daemon-1 | 2025/05/14 01:20:35 run.go:144: [INFO]plugin langgenius/ollama:0.0.6 started plugin_daemon-1 | 2025/05/14 01:20:36 run.go:132: [ERROR]plugin langgenius/ollama:0.0.6 exited with error: exit status 1 plugin_daemon-1 | dcdf5589fdf5d01a995533f956853c69c54eddcf797006fa37/main.py", line 3, in <module> plugin_daemon-1 | plugin_daemon-1 | plugin = Plugin(DifyPluginEnv()) plugin_daemon-1 | ^^^^^^^^^^^^^^^ plugin_daemon-1 | plugin_daemon-1 | File "/app/storage/cwd/langgenius/ollama-0.0.6@7d66a960a68cafdcdf5589fdf5d01a995533f956853c69c54eddcf797006fa37/.venv/lib/python3.12/site-packages/pydantic_settings/main.py", line 176, in __init__ plugin_daemon-1 | plugin_daemon-1 | super().__init__( plugin_daemon-1 | File "/app/storage/cwd/langgenius/ollama-0.0.6@7d66a960a68cafdcdf5589fdf5d01a995533f956853c69c54eddcf797006fa37/.venv/lib/python3.12/site-packages/pydantic/main.py", line 253, in __init__ plugin_daemon-1 | plugin_daemon-1 | validated_self = self.__pydantic_validator__.validate_python(data, self_instance=self) plugin_daemon-1 | plugin_daemon-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ plugin_daemon-1 | plugin_daemon-1 | pydantic_core._pydantic_core.ValidationError: 1 validation error for DifyPluginEnv plugin_daemon-1 | REMOTE_INSTALL_URL plugin_daemon-1 | Field required [type=missing, input_value={'INSTALL_METHOD': 'local'}, input_type=dict] plugin_daemon-1 | For further information visit https://errors.pydantic.dev/2.11/v/missing plugin_daemon-1 | plugin_daemon-1 | plugin_daemon-1 | plugin_daemon-1 | 2025/05/14 01:20:36 run.go:182: [INFO]plugin langgenius/ollama:0.0.6 stopped ``` @dosu Could you please help me find similar cases and solutions? ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 19:14:09 -05:00
yindo closed this issue 2026-02-21 19:14:09 -05:00
yindo commented 2026-02-21 19:14:09 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 13, 2025):

To resolve the looping installation failure error with the Ollama plugin in Dify version 1.3.1, specifically addressing the "REMOTE_INSTALL_URL Field required" validation error, follow these steps:

  1. Stop the Docker containers:

    docker compose down

  2. Add the following environment variable to the worker, api, and plugin_daemon services in your docker-compose.yml:

    REMOTE_INSTALL_URL: http://${EXPOSE_PLUGIN_DEBUGGING_HOST:-localhost}:${EXPOSE_PLUGIN_DEBUGGING_PORT:-5003}

  3. Add the following line to the dify/docker/.env file:

    REMOTE_INSTALL_URL=http://${EXPOSE_PLUGIN_DEBUGGING_HOST:-localhost}:${EXPOSE_PLUGIN_DEBUGGING_PORT:-5003}

  4. Restart the Docker containers:

    docker compose up -d

Alternatively, you can use version 0.0.10 of the openai_api_compatible plugin instead of version 0.0.16 to avoid this issue [1][2].

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 (May 13, 2025): <!-- Answer --> To resolve the looping installation failure error with the Ollama plugin in Dify version 1.3.1, specifically addressing the "REMOTE_INSTALL_URL Field required" validation error, follow these steps: 1. Stop the Docker containers: ```bash docker compose down ``` 2. Add the following environment variable to the `worker`, `api`, and `plugin_daemon` services in your `docker-compose.yml`: ```yaml REMOTE_INSTALL_URL: http://${EXPOSE_PLUGIN_DEBUGGING_HOST:-localhost}:${EXPOSE_PLUGIN_DEBUGGING_PORT:-5003} ``` 3. Add the following line to the `dify/docker/.env` file: ``` REMOTE_INSTALL_URL=http://${EXPOSE_PLUGIN_DEBUGGING_HOST:-localhost}:${EXPOSE_PLUGIN_DEBUGGING_PORT:-5003} ``` 4. Restart the Docker containers: ```bash docker compose up -d ``` Alternatively, you can use version 0.0.10 of the openai_api_compatible plugin instead of version 0.0.16 to avoid this issue <sup>[[1]](https://github.com/langgenius/dify/issues/19635)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/19612)</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/3982fef1-dbc9-4ba8-9ba1-2589cf652093?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/3982fef1-dbc9-4ba8-9ba1-2589cf652093?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/3982fef1-dbc9-4ba8-9ba1-2589cf652093?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/3982fef1-dbc9-4ba8-9ba1-2589cf652093?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/3982fef1-dbc9-4ba8-9ba1-2589cf652093?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/3982fef1-dbc9-4ba8-9ba1-2589cf652093?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/3982fef1-dbc9-4ba8-9ba1-2589cf652093?feedback_type=other)</sup>
yindo commented 2026-02-21 19:14:09 -05:00
Author
Owner
Copy Link
Copy Source

@tigflanker commented on GitHub (May 13, 2025):

@dosu This time, I have used entirely local installation methods: specifically, I first download the plugin to my local machine and then install it from the local source. Additionally, I'm not sure whether the issue is caused by the Ollama plugin itself or due to the fact that I previously terminated the installation forcefully.

@tigflanker commented on GitHub (May 13, 2025): @dosu This time, I have used entirely local installation methods: specifically, I first download the plugin to my local machine and then install it from the local source. Additionally, I'm not sure whether the issue is caused by the Ollama plugin itself or due to the fact that I previously terminated the installation forcefully.
yindo commented 2026-02-21 19:14:09 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 13, 2025):

To address the issue with the Ollama plugin installation, especially if you previously terminated the installation forcefully, follow these steps:

  1. Clear Plugin Data: Execute the following SQL commands in the dify_plugin database to remove any residual plugin data:

    delete from plugin_installations where plugin_unique_identifier is not null;
delete from plugin_declarations where plugin_unique_identifier is not null;
delete from ai_model_installations where plugin_unique_identifier is not null;
delete from plugins where plugin_unique_identifier is not null;

  2. Clear Plugin Directories: Remove the contents of the following directories to ensure a clean state:

    • /app/storage/cwd/plugins/plugin
    • /app/storage/cwd/plugins/plugin-working
    • /app/storage/cwd/plugins/persistence
    • /app/storage/cwd/plugins/plugin-root

  3. Restart Plugin Daemon: Restart the plugin daemon service to apply the changes.

  4. Reinstall the Plugin: Proceed with reinstalling the plugin from your local source.

These steps should help resolve any issues related to forcefully terminating the plugin installation and ensure a clean setup for the Ollama plugin [1].

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 (May 13, 2025): <!-- Answer --> To address the issue with the Ollama plugin installation, especially if you previously terminated the installation forcefully, follow these steps: 1. **Clear Plugin Data**: Execute the following SQL commands in the `dify_plugin` database to remove any residual plugin data: ```sql delete from plugin_installations where plugin_unique_identifier is not null; delete from plugin_declarations where plugin_unique_identifier is not null; delete from ai_model_installations where plugin_unique_identifier is not null; delete from plugins where plugin_unique_identifier is not null; ``` 2. **Clear Plugin Directories**: Remove the contents of the following directories to ensure a clean state: - `/app/storage/cwd/plugins/plugin` - `/app/storage/cwd/plugins/plugin-working` - `/app/storage/cwd/plugins/persistence` - `/app/storage/cwd/plugins/plugin-root` 3. **Restart Plugin Daemon**: Restart the plugin daemon service to apply the changes. 4. **Reinstall the Plugin**: Proceed with reinstalling the plugin from your local source. These steps should help resolve any issues related to forcefully terminating the plugin installation and ensure a clean setup for the Ollama plugin <sup>[[1]](https://github.com/langgenius/dify/issues/14718)</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/ac788874-5f5d-4575-8bd9-b55998508a58?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ac788874-5f5d-4575-8bd9-b55998508a58?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ac788874-5f5d-4575-8bd9-b55998508a58?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ac788874-5f5d-4575-8bd9-b55998508a58?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ac788874-5f5d-4575-8bd9-b55998508a58?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/ac788874-5f5d-4575-8bd9-b55998508a58?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ac788874-5f5d-4575-8bd9-b55998508a58?feedback_type=other)</sup>
yindo commented 2026-02-21 19:14:09 -05:00
Author
Owner
Copy Link
Copy Source

@IthacaDream commented on GitHub (May 13, 2025):

Here's a quick fix for this issue:
a. locking dify_plugin version < 0.2.3
OR
b . adding a new env REMOTE_INSTALL_URL for plugin_daemon serivce

@IthacaDream commented on GitHub (May 13, 2025): Here's a quick fix for this issue: a. locking dify_plugin version < 0.2.3 `OR ` b . adding a new env `REMOTE_INSTALL_URL` for `plugin_daemon` serivce
yindo commented 2026-02-21 19:14:09 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 13, 2025):

Similar issues:

PR:

@crazywoola commented on GitHub (May 13, 2025): Similar issues: - https://github.com/langgenius/dify/issues/19632 - https://github.com/langgenius/dify/issues/19612 - https://github.com/langgenius/dify/issues/19635 - https://github.com/langgenius/dify/issues/19624 PR: - https://github.com/langgenius/dify-plugin-sdks/pull/141
yindo commented 2026-02-21 19:14:09 -05:00
Author
Owner
Copy Link
Copy Source

@Yeuoly commented on GitHub (May 14, 2025):

Fixed, a new version has been released here: https://github.com/langgenius/dify-plugin-sdks/releases/tag/0.2.4
just feel free to reinstall the plugin and everything will be fine

@Yeuoly commented on GitHub (May 14, 2025): Fixed, a new version has been released here: https://github.com/langgenius/dify-plugin-sdks/releases/tag/0.2.4 just feel free to reinstall the plugin and everything will be fine
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#13843
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?