Knowledge Base Q&A Image Output Conflicts with Mineru Plugin Configuration #21191

New Issue

2026-02-21T20:11:20-05:00

yindo commented

2026-02-21 20:11:20 -05:00

Originally created by @comaaxl on GitHub (Dec 21, 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

v1.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I have locally deployed Dify v1.11.1 on a MacBook M4 via Docker, where Docker runs on Docker Desktop installed on the Mac. Initially, I set FILES_URL=http://local:5001 in the .env file—this is the only way to display images parsed from documents in the Knowledge Base Q&A output. For example, images extracted from Word documents appear as . This configuration is based on the solution provided in your GitHub issue: https://github.com/langgenius/dify/issues/29090

However, when FILES_URL is set to http://local:5001, the Mineru plugin (version: v0.5.1) fails to work properly and throws the following error:
"An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: ConnectError, error details: [Errno 111] Connection refused"

The Mineru plugin only functions correctly if FILES_URL is set to http://api:5001.
Therefore, I am confused—aren't the configurations for these two features conflicting? Could you please provide a solution to make both the Knowledge Base Q&A image display and the Mineru plugin work properly simultaneously? thanks!

env.txt

docker-compose.yaml

✔️ Expected Behavior

none

❌ Actual Behavior

none

Originally created by @comaaxl on GitHub (Dec 21, 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 v1.11.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I have locally deployed Dify v1.11.1 on a MacBook M4 via Docker, where Docker runs on Docker Desktop installed on the Mac. Initially, I set FILES_URL=http://local:5001 in the .env file—this is the only way to display images parsed from documents in the Knowledge Base Q&A output. For example, images extracted from Word documents appear as ![image](http://api:5001/files/079c5597-11fa-4710-8337-77943c37de37/file-preview). This configuration is based on the solution provided in your GitHub issue: https://github.com/langgenius/dify/issues/29090 However, when FILES_URL is set to http://local:5001, the Mineru plugin (version: v0.5.1) fails to work properly and throws the following error: "An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: ConnectError, error details: [Errno 111] Connection refused" The Mineru plugin only functions correctly if FILES_URL is set to http://api:5001. Therefore, I am confused—aren't the configurations for these two features conflicting? Could you please provide a solution to make both the Knowledge Base Q&A image display and the Mineru plugin work properly simultaneously? thanks! [env.txt](https://github.com/user-attachments/files/24278810/env.txt) [docker-compose.yaml](https://github.com/user-attachments/files/24278811/docker-compose.yaml) ### ✔️ Expected Behavior none ### ❌ Actual Behavior none

yindo added the 🐞 bug label 2026-02-21 20:11:20 -05:00

yindo closed this issue

2026-02-21 20:11:20 -05:00

yindo commented

2026-02-21 20:11:21 -05:00

@dosubot[bot] commented on GitHub (Dec 21, 2025):

This conflict happens because FILES_URL is used for external file access (like image display in your browser), while plugins such as Mineru need to access files via the internal Docker network address. Dify supports a separate INTERNAL_FILES_URL environment variable for this purpose.

To resolve both issues, set your environment variables as follows:

FILES_URL to the externally-accessible address (e.g., http://local:5001) so images display correctly in the Knowledge Base Q&A.
INTERNAL_FILES_URL to the internal Docker network address (e.g., http://api:5001) so Mineru can connect without errors.

Both variables should be set in your .env and referenced in your docker-compose.yaml. After updating, restart all relevant containers to apply the changes.

This setup works because Dify's codebase prioritizes INTERNAL_FILES_URL for internal plugin/service communication and FILES_URL for browser access, allowing both features to function simultaneously (feature config, file helpers, docker-compose.yaml).

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 21, 2025):  This conflict happens because FILES_URL is used for external file access (like image display in your browser), while plugins such as Mineru need to access files via the internal Docker network address. Dify supports a separate INTERNAL_FILES_URL environment variable for this purpose. To resolve both issues, set your environment variables as follows: - FILES_URL to the externally-accessible address (e.g., `http://local:5001`) so images display correctly in the Knowledge Base Q&A. - INTERNAL_FILES_URL to the internal Docker network address (e.g., `http://api:5001`) so Mineru can connect without errors. Both variables should be set in your `.env` and referenced in your `docker-compose.yaml`. After updating, restart all relevant containers to apply the changes. This setup works because Dify's codebase prioritizes INTERNAL_FILES_URL for internal plugin/service communication and FILES_URL for browser access, allowing both features to function simultaneously ([feature config](https://github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/api/configs/feature/__init__.py#L301-L315), [file helpers](https://github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/api/core/file/helpers.py#L11-L38), [docker-compose.yaml](https://github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/docker/docker-compose.yaml#L7-L993)).  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/b39fef0b-1774-41bf-9114-50f884eb6f67?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b39fef0b-1774-41bf-9114-50f884eb6f67?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b39fef0b-1774-41bf-9114-50f884eb6f67?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b39fef0b-1774-41bf-9114-50f884eb6f67?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b39fef0b-1774-41bf-9114-50f884eb6f67?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b39fef0b-1774-41bf-9114-50f884eb6f67?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b39fef0b-1774-41bf-9114-50f884eb6f67?feedback_type=other) [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20conflict%20happens%20because%20FILES_URL%20is%20used%20for%20external%20file%20access%20%28like%20image%20display%20in%20your%20browser%29%2C%20while%20plugins%20such%20as%20Mineru%20need%20to%20access%20files%20via%20the%20internal%20Docker%20network%20address.%20Dify%20supports%20a%20separate%20INTERNAL_FILES_URL%20environment%20variable%20for%20this%20purpose.%0A%0ATo%20resolve%20both%20issues%2C%20set%20your%20environment%20variables%20as%20follows%3A%0A%0A-%20FILES_URL%20to%20the%20externally-accessible%20address%20%28e.g.%2C%20%60http%3A//local%3A5001%60%29%20so%20images%20display%20correctly%20in%20the%20Knowledge%20Base%20Q%26A.%0A-%20INTERNAL_FILES_URL%20to%20the%20internal%20Docker%20network%20address%20%28e.g.%2C%20%60http%3A//api%3A5001%60%29%20so%20Mineru%20can%20connect%20without%20errors.%0A%0ABoth%20variables%20should%20be%20set%20in%20your%20%60.env%60%20and%20referenced%20in%20your%20%60docker-compose.yaml%60.%20After%20updating%2C%20restart%20all%20relevant%20containers%20to%20apply%20the%20changes.%0A%0AThis%20setup%20works%20because%20Dify%27s%20codebase%20prioritizes%20INTERNAL_FILES_URL%20for%20internal%20plugin/service%20communication%20and%20FILES_URL%20for%20browser%20access%2C%20allowing%20both%20features%20to%20function%20simultaneously%20%28%5Bfeature%20config%5D%28https%3A//github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/api/configs/feature/__init__.py%23L301-L315%29%2C%20%5Bfile%20helpers%5D%28https%3A//github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/api/core/file/helpers.py%23L11-L38%29%2C%20%5Bdocker-compose.yaml%5D%28https%3A//github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/docker/docker-compose.yaml%23L7-L993%29%29.) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/29965)

yindo commented

2026-02-21 20:11:21 -05:00

@comaaxl commented on GitHub (Dec 21, 2025):

@dosu
@dosu

But strangely enough, I currently have the following settings in my .env file:
FILES_URL=http://localhost:5001
INTERNAL_FILES_URL=http://api:5001

Additionally, the following variables are defined at the very top of my docker_compose.yaml file:

FILES_URL: ${FILES_URL:-}
INTERNAL_FILES_URL: ${INTERNAL_FILES_URL:-}

However, in practice, while the images in the Knowledge Base Q&A can be displayed normally, the Mineru plugin still throws an error：

The Mineru plugin only works properly if I set FILES_URL=http://api:5001. But in this case, when conducting Q&A, the images flash briefly (i.e., the original Markdown format of the images appears for a split second and then disappears immediately) and fail to be displayed persistently.

It seems that the configuration you suggested does not resolve the issue as expected. Additionally, regarding your recommendation to reference FILES_URL and INTERNAL_FILES_URL in docker_compose.yaml, do I need to add these references specifically within the api service configuration?
I have provided my two configuration files below. Could you please help analyze and resolve this problem? Thank you!

env.txt

docker-compose.yaml

@comaaxl commented on GitHub (Dec 21, 2025): @dosu [@dosu](https://go.dosu.dev/dosubot) But strangely enough, I currently have the following settings in my .env file: FILES_URL=http://localhost:5001 INTERNAL_FILES_URL=http://api:5001 Additionally, the following variables are defined at the very top of my docker_compose.yaml file: FILES_URL: ${FILES_URL:-} INTERNAL_FILES_URL: ${INTERNAL_FILES_URL:-} However, in practice, while the images in the Knowledge Base Q&A can be displayed normally, the Mineru plugin still throws an error： <img width="989" height="500" alt="Image" src="https://github.com/user-attachments/assets/1ecace0d-95f3-48a0-8b37-1c3547531372" /> The Mineru plugin only works properly if I set FILES_URL=http://api:5001. But in this case, when conducting Q&A, the images flash briefly (i.e., the original Markdown format of the images appears for a split second and then disappears immediately) and fail to be displayed persistently. It seems that the configuration you suggested does not resolve the issue as expected. Additionally, regarding your recommendation to reference FILES_URL and INTERNAL_FILES_URL in docker_compose.yaml, do I need to add these references specifically within the api service configuration? I have provided my two configuration files below. Could you please help analyze and resolve this problem? Thank you! [env.txt](https://github.com/user-attachments/files/24279027/env.txt) [docker-compose.yaml](https://github.com/user-attachments/files/24279001/docker-compose.yaml)

yindo commented

2026-02-21 20:11:21 -05:00

@comaaxl commented on GitHub (Dec 21, 2025):

@dosu
api log:

2025-12-21 14:11:16.321 INFO [Dummy-9] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/triggers?page=1&page_size=256⁠ "HTTP/1.1 200 OK"

2025-12-21 14:11:16.323 INFO [Dummy-5] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256⁠ "HTTP/1.1 200 OK"

2025-12-21 14:11:16.330 INFO [Dummy-8] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256⁠ "HTTP/1.1 200 OK"

2025-12-21 14:11:19.698 INFO [Dummy-46] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠ "HTTP/1.1 200 OK"

2025-12-21 14:11:19.818 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠ "HTTP/1.1 200 OK"

2025-12-21 14:11:20.058 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/dispatch/tool/invoke⁠ "HTTP/1.1 200 OK"

2025-12-21 14:11:20.060 ERROR [GraphWorker-0] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\"args\":{},\"error_type\":\"ConnectError\",\"message\":\"[Errno 111] Connection refused\"}","error_type":"PluginInvokeError","args":null}', 'data': None}

2025-12-21 14:11:20.060 ERROR [GraphDispatcher] [error_handler.py:101] - Node 1766320785291 failed with ABORT strategy: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: ConnectError, error details: [Errno 111] Connection refused

2025-12-21 14:11:20.162 ERROR [Thread-17 (_generate_worker)] [workflow_entry.py:111] - Unknown Error when workflow entry running

Traceback (most recent call last):

File "/app/api/core/workflow/workflow_entry.py", line 107, in run

yield from generator

File "/app/api/core/workflow/graph_engine/graph_engine.py", line 270, in run

raise self._graph_execution.error

RuntimeError: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: ConnectError, error details: [Errno 111] Connection refused

2025-12-21 14:11:21.270 INFO [Dummy-15] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠ "HTTP/1.1 200 OK"

plugin_daemon log:

[GIN] 2025/12/21 - 14:11:16 | 200 | 890.625µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/triggers?page=1&page_size=256"

[GIN] 2025/12/21 - 14:11:16 | 200 | 2.990541ms | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256"

[GIN] 2025/12/21 - 14:11:16 | 200 | 12.223625ms | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256"

[GIN] 2025/12/21 - 14:11:19 | 200 | 699.542µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru"

[GIN] 2025/12/21 - 14:11:19 | 200 | 588.083µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru"

[GIN] 2025/12/21 - 14:11:20 | 200 | 216.448166ms | 172.20.0.11 | POST "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/dispatch/tool/invoke"

[GIN] 2025/12/21 - 14:11:21 | 200 | 522.5µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru"

[GIN] 2025/12/21 - 14:11:40 | 200 | 772.375µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru"

@comaaxl commented on GitHub (Dec 21, 2025): [@dosu](https://go.dosu.dev/dosubot) api log: 2025-12-21 14:11:16.321 INFO [Dummy-9] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/triggers?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/triggers?page=1&page_size=256) "HTTP/1.1 200 OK" 2025-12-21 14:11:16.323 INFO [Dummy-5] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256) "HTTP/1.1 200 OK" 2025-12-21 14:11:16.330 INFO [Dummy-8] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256) "HTTP/1.1 200 OK" 2025-12-21 14:11:19.698 INFO [Dummy-46] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru) "HTTP/1.1 200 OK" 2025-12-21 14:11:19.818 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru) "HTTP/1.1 200 OK" 2025-12-21 14:11:20.058 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/dispatch/tool/invoke⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/dispatch/tool/invoke) "HTTP/1.1 200 OK" 2025-12-21 14:11:20.060 ERROR [GraphWorker-0] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{},\\"error_type\\":\\"ConnectError\\",\\"message\\":\\"[Errno 111] Connection refused\\"}","error_type":"PluginInvokeError","args":null}', 'data': None} 2025-12-21 14:11:20.060 ERROR [GraphDispatcher] [error_handler.py:101] - Node 1766320785291 failed with ABORT strategy: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: ConnectError, error details: [Errno 111] Connection refused 2025-12-21 14:11:20.162 ERROR [Thread-17 (_generate_worker)] [workflow_entry.py:111] - Unknown Error when workflow entry running Traceback (most recent call last): File "/app/api/core/workflow/workflow_entry.py", line 107, in run yield from generator File "/app/api/core/workflow/graph_engine/graph_engine.py", line 270, in run raise self._graph_execution.error RuntimeError: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: ConnectError, error details: [Errno 111] Connection refused 2025-12-21 14:11:21.270 INFO [Dummy-15] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru) "HTTP/1.1 200 OK" plugin_daemon log: [GIN] 2025/12/21 - 14:11:16 | 200 | 890.625µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/triggers?page=1&page_size=256" [GIN] 2025/12/21 - 14:11:16 | 200 | 2.990541ms | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256" [GIN] 2025/12/21 - 14:11:16 | 200 | 12.223625ms | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/models?page=1&page_size=256" [GIN] 2025/12/21 - 14:11:19 | 200 | 699.542µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru" [GIN] 2025/12/21 - 14:11:19 | 200 | 588.083µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru" [GIN] 2025/12/21 - 14:11:20 | 200 | 216.448166ms | 172.20.0.11 | POST "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/dispatch/tool/invoke" [GIN] 2025/12/21 - 14:11:21 | 200 | 522.5µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru" [GIN] 2025/12/21 - 14:11:40 | 200 | 772.375µs | 172.20.0.11 | GET "/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru"

yindo commented

2026-02-21 20:11:21 -05:00

@dosubot[bot] commented on GitHub (Dec 21, 2025):

Your current setup is running into this issue because Docker containers can't access your host's localhost, and INTERNAL_FILES_URL takes priority for plugin access. Here’s how to resolve it:

In your .env file, set FILES_URL to your host's LAN IP (for example, http://192.168.x.x:5001), not localhost or api. Leave INTERNAL_FILES_URL blank.
In your docker-compose.yaml, under the api service, add a ports mapping:
```
ports:
  - "5001:5001"
```
This exposes the file server to your host/LAN.
Restart all containers with docker-compose down && docker-compose up -d to apply changes.
Verify the environment variables inside both the api and plugin_daemon containers using docker exec <container> env to ensure the correct values are loaded.
Test file server accessibility from your browser (using the LAN IP and port 5001) and from within the plugin_daemon container (using curl or wget to the FILES_URL address).

This setup ensures that images display in the Knowledge Base Q&A and the Mineru plugin can connect without errors. If you still see issues, double-check your Docker port mapping and that the correct .env file is being used. More details and examples are available in the docs and related issues (source, source).

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 21, 2025):  Your current setup is running into this issue because Docker containers can't access your host's localhost, and INTERNAL_FILES_URL takes priority for plugin access. Here’s how to resolve it: 1. In your .env file, set FILES_URL to your host's LAN IP (for example, `http://192.168.x.x:5001`), not `localhost` or `api`. Leave INTERNAL_FILES_URL blank. 2. In your docker-compose.yaml, under the api service, add a ports mapping: ```yaml ports: - "5001:5001" ``` This exposes the file server to your host/LAN. 3. Restart all containers with `docker-compose down && docker-compose up -d` to apply changes. 4. Verify the environment variables inside both the api and plugin_daemon containers using `docker exec <container> env` to ensure the correct values are loaded. 5. Test file server accessibility from your browser (using the LAN IP and port 5001) and from within the plugin_daemon container (using curl or wget to the FILES_URL address). This setup ensures that images display in the Knowledge Base Q&A and the Mineru plugin can connect without errors. If you still see issues, double-check your Docker port mapping and that the correct .env file is being used. More details and examples are available in the docs and related issues ([source](https://github.com/langgenius/dify-docs/issues/471#issuecomment-3343703487), [source](https://github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/docker/.env.example#L44-L58)).  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/0096bed4-627c-4f2d-b16d-6519fa939845?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0096bed4-627c-4f2d-b16d-6519fa939845?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0096bed4-627c-4f2d-b16d-6519fa939845?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0096bed4-627c-4f2d-b16d-6519fa939845?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0096bed4-627c-4f2d-b16d-6519fa939845?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0096bed4-627c-4f2d-b16d-6519fa939845?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0096bed4-627c-4f2d-b16d-6519fa939845?feedback_type=other) [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Your%20current%20setup%20is%20running%20into%20this%20issue%20because%20Docker%20containers%20can%27t%20access%20your%20host%27s%20localhost%2C%20and%20INTERNAL_FILES_URL%20takes%20priority%20for%20plugin%20access.%20Here%E2%80%99s%20how%20to%20resolve%20it%3A%0A%0A1.%20In%20your%20.env%20file%2C%20set%20FILES_URL%20to%20your%20host%27s%20LAN%20IP%20%28for%20example%2C%20%60http%3A//192.168.x.x%3A5001%60%29%2C%20not%20%60localhost%60%20or%20%60api%60.%20Leave%20INTERNAL_FILES_URL%20blank.%0A2.%20In%20your%20docker-compose.yaml%2C%20under%20the%20api%20service%2C%20add%20a%20ports%20mapping%3A%20%20%0A%20%20%20%60%60%60yaml%0A%20%20%20ports%3A%0A%20%20%20%20%20-%20%225001%3A5001%22%0A%20%20%20%60%60%60%0A%20%20%20This%20exposes%20the%20file%20server%20to%20your%20host/LAN.%0A3.%20Restart%20all%20containers%20with%20%60docker-compose%20down%20%26%26%20docker-compose%20up%20-d%60%20to%20apply%20changes.%0A4.%20Verify%20the%20environment%20variables%20inside%20both%20the%20api%20and%20plugin_daemon%20containers%20using%20%60docker%20exec%20%3Ccontainer%3E%20env%60%20to%20ensure%20the%20correct%20values%20are%20loaded.%0A5.%20Test%20file%20server%20accessibility%20from%20your%20browser%20%28using%20the%20LAN%20IP%20and%20port%205001%29%20and%20from%20within%20the%20plugin_daemon%20container%20%28using%20curl%20or%20wget%20to%20the%20FILES_URL%20address%29.%0A%0AThis%20setup%20ensures%20that%20images%20display%20in%20the%20Knowledge%20Base%20Q%26A%20and%20the%20Mineru%20plugin%20can%20connect%20without%20errors.%20If%20you%20still%20see%20issues%2C%20double-check%20your%20Docker%20port%20mapping%20and%20that%20the%20correct%20.env%20file%20is%20being%20used.%20More%20details%20and%20examples%20are%20available%20in%20the%20docs%20and%20related%20issues%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify-docs/issues/471%23issuecomment-3343703487%29%2C%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/docker/.env.example%23L44-L58%29%29.) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/29965)

yindo commented

2026-02-21 20:11:21 -05:00

@comaaxl commented on GitHub (Dec 21, 2025):

@dosu
@dosu
FILES_URL=http://192.168.0.110:5001
INTERNAL_FILES_URL=

the environment variables inside both the api and plugin_daemon containers using docker exec env to ensure the correct values are loaded.

now the Mineru plugin throws an error：

api log

RuntimeError: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: Exception, error details: Failed to create parsing task: HTTPSConnectionPool(host='mineru.net', port=443): Max retries exceeded with url: /api/v4/file-urls/batch (Caused by NameResolutionError("HTTPSConnection(host='mineru.net', port=443): Failed to resolve 'mineru.net' ([Errno -3] Temporary failure in name resolution)"))

2025-12-21 14:39:41.088 INFO [Dummy-6] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠ "HTTP/1.1 200 OK"

2025-12-21 14:39:50.417 INFO [Dummy-5] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/triggers?page=1&page_size=256⁠ "HTTP/1.1 200 OK"

2025-12-21 14:39:53.870 INFO [Dummy-4] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠ "HTTP/1.1 200 OK"

2025-12-21 14:39:53.995 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠ "HTTP/1.1 200 OK"

2025-12-21 14:40:02.034 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/dispatch/tool/invoke⁠ "HTTP/1.1 200 OK"

2025-12-21 14:40:02.036 ERROR [GraphWorker-0] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\"args\":{},\"error_type\":\"Exception\",\"message\":\"Failed to create parsing task: HTTPSConnectionPool(host='mineru.net', port=443): Max retries exceeded with url: /api/v4/file-urls/batch (Caused by NameResolutionError(\\\"HTTPSConnection(host='mineru.net', port=443): Failed to resolve 'mineru.net' ([Errno -3] Temporary failure in name resolution)\\\"))\"}","error_type":"PluginInvokeError","args":null}', 'data': None}

2025-12-21 14:40:02.125 ERROR [GraphDispatcher] [error_handler.py:101] - Node 1766320785291 failed with ABORT strategy: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: Exception, error details: Failed to create parsing task: HTTPSConnectionPool(host='mineru.net', port=443): Max retries exceeded with url: /api/v4/file-urls/batch (Caused by NameResolutionError("HTTPSConnection(host='mineru.net', port=443): Failed to resolve 'mineru.net' ([Errno -3] Temporary failure in name resolution)"))

2025-12-21 14:40:02.240 ERROR [Thread-7 (_generate_worker)] [workflow_entry.py:111] - Unknown Error when workflow entry running

Traceback (most recent call last):

File "/app/api/core/workflow/workflow_entry.py", line 107, in run

yield from generator

File "/app/api/core/workflow/graph_engine/graph_engine.py", line 270, in run

raise self._graph_execution.error

RuntimeError: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: Exception, error details: Failed to create parsing task: HTTPSConnectionPool(host='mineru.net', port=443): Max retries exceeded with url: /api/v4/file-urls/batch (Caused by NameResolutionError("HTTPSConnection(host='mineru.net', port=443): Failed to resolve 'mineru.net' ([Errno -3] Temporary failure in name resolution)"))

2025-12-21 14:40:05.033 INFO [Dummy-7] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠ "HTTP/1.1 200 OK"

@comaaxl commented on GitHub (Dec 21, 2025): @dosu [@dosu](https://go.dosu.dev/dosubot) FILES_URL=http://192.168.0.110:5001 INTERNAL_FILES_URL= the environment variables inside both the api and plugin_daemon containers using docker exec <container> env to ensure the correct values are loaded. <img width="363" height="122" alt="Image" src="https://github.com/user-attachments/assets/19004152-f808-4a53-9953-0df4b26c04af" /> now the Mineru plugin throws an error： <img width="1051" height="538" alt="Image" src="https://github.com/user-attachments/assets/b2c08c47-d786-4521-985a-6291e23b28c3" /> api log RuntimeError: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: Exception, error details: Failed to create parsing task: HTTPSConnectionPool(host='mineru.net', port=443): Max retries exceeded with url: /api/v4/file-urls/batch (Caused by NameResolutionError("HTTPSConnection(host='mineru.net', port=443): Failed to resolve 'mineru.net' ([Errno -3] Temporary failure in name resolution)")) 2025-12-21 14:39:41.088 INFO [Dummy-6] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru) "HTTP/1.1 200 OK" 2025-12-21 14:39:50.417 INFO [Dummy-5] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/triggers?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/triggers?page=1&page_size=256) "HTTP/1.1 200 OK" 2025-12-21 14:39:53.870 INFO [Dummy-4] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru) "HTTP/1.1 200 OK" 2025-12-21 14:39:53.995 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru) "HTTP/1.1 200 OK" 2025-12-21 14:40:02.034 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/dispatch/tool/invoke⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/dispatch/tool/invoke) "HTTP/1.1 200 OK" 2025-12-21 14:40:02.036 ERROR [GraphWorker-0] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{},\\"error_type\\":\\"Exception\\",\\"message\\":\\"Failed to create parsing task: HTTPSConnectionPool(host=\'mineru.net\', port=443): Max retries exceeded with url: /api/v4/file-urls/batch (Caused by NameResolutionError(\\\\\\"HTTPSConnection(host=\'mineru.net\', port=443): Failed to resolve \'mineru.net\' ([Errno -3] Temporary failure in name resolution)\\\\\\"))\\"}","error_type":"PluginInvokeError","args":null}', 'data': None} 2025-12-21 14:40:02.125 ERROR [GraphDispatcher] [error_handler.py:101] - Node 1766320785291 failed with ABORT strategy: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: Exception, error details: Failed to create parsing task: HTTPSConnectionPool(host='mineru.net', port=443): Max retries exceeded with url: /api/v4/file-urls/batch (Caused by NameResolutionError("HTTPSConnection(host='mineru.net', port=443): Failed to resolve 'mineru.net' ([Errno -3] Temporary failure in name resolution)")) 2025-12-21 14:40:02.240 ERROR [Thread-7 (_generate_worker)] [workflow_entry.py:111] - Unknown Error when workflow entry running Traceback (most recent call last): File "/app/api/core/workflow/workflow_entry.py", line 107, in run yield from generator File "/app/api/core/workflow/graph_engine/graph_engine.py", line 270, in run raise self._graph_execution.error RuntimeError: An error occurred in the langgenius/mineru/mineru, please contact the author of langgenius/mineru/mineru for help, error type: Exception, error details: Failed to create parsing task: HTTPSConnectionPool(host='mineru.net', port=443): Max retries exceeded with url: /api/v4/file-urls/batch (Caused by NameResolutionError("HTTPSConnection(host='mineru.net', port=443): Failed to resolve 'mineru.net' ([Errno -3] Temporary failure in name resolution)")) 2025-12-21 14:40:05.033 INFO [Dummy-7] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru⁠](http://plugin_daemon:5002/plugin/e0bceaf9-2ab5-45db-85da-e9da7d368333/management/tool?provider=mineru&plugin_id=langgenius%2Fmineru) "HTTP/1.1 200 OK"

yindo commented

2026-02-21 20:11:21 -05:00

@dosubot[bot] commented on GitHub (Dec 21, 2025):

The DNS error for mineru.net is caused by the SSRF proxy (ssrf_proxy service) in your Docker setup, which only allows outbound connections to domains listed in its ACL. By default, only .marketplace.dify.ai is allowed, so mineru.net is blocked.

To fix this, edit docker/ssrf_proxy/squid.conf.template and add mineru.net to the allowed_domains ACL, like this:

acl allowed_domains dstdomain .marketplace.dify.ai mineru.net
http_access allow allowed_domains
http_access deny all

Then, rebuild and restart the ssrf_proxy and plugin_daemon containers (docker-compose down && docker-compose up -d) to apply the change. This will allow the Mineru plugin to connect to mineru.net while keeping your current FILES_URL setup for image display in the Knowledge Base Q&A.
Reference

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 21, 2025):  The DNS error for mineru.net is caused by the SSRF proxy (ssrf_proxy service) in your Docker setup, which only allows outbound connections to domains listed in its ACL. By default, only .marketplace.dify.ai is allowed, so mineru.net is blocked. To fix this, edit docker/ssrf_proxy/squid.conf.template and add mineru.net to the allowed_domains ACL, like this: ``` acl allowed_domains dstdomain .marketplace.dify.ai mineru.net http_access allow allowed_domains http_access deny all ``` Then, rebuild and restart the ssrf_proxy and plugin_daemon containers (docker-compose down && docker-compose up -d) to apply the change. This will allow the Mineru plugin to connect to mineru.net while keeping your current FILES_URL setup for image display in the Knowledge Base Q&A. [Reference](https://github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/docker/ssrf_proxy/squid.conf.template#L22-L30)  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/7f0d88a0-d030-4d60-99b5-b0ae8ccb40fa?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7f0d88a0-d030-4d60-99b5-b0ae8ccb40fa?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7f0d88a0-d030-4d60-99b5-b0ae8ccb40fa?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7f0d88a0-d030-4d60-99b5-b0ae8ccb40fa?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7f0d88a0-d030-4d60-99b5-b0ae8ccb40fa?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7f0d88a0-d030-4d60-99b5-b0ae8ccb40fa?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7f0d88a0-d030-4d60-99b5-b0ae8ccb40fa?feedback_type=other) [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20DNS%20error%20for%20mineru.net%20is%20caused%20by%20the%20SSRF%20proxy%20%28ssrf_proxy%20service%29%20in%20your%20Docker%20setup%2C%20which%20only%20allows%20outbound%20connections%20to%20domains%20listed%20in%20its%20ACL.%20By%20default%2C%20only%20.marketplace.dify.ai%20is%20allowed%2C%20so%20mineru.net%20is%20blocked.%0A%0ATo%20fix%20this%2C%20edit%20docker/ssrf_proxy/squid.conf.template%20and%20add%20mineru.net%20to%20the%20allowed_domains%20ACL%2C%20like%20this%3A%0A%0A%60%60%60%0Aacl%20allowed_domains%20dstdomain%20.marketplace.dify.ai%20mineru.net%0Ahttp_access%20allow%20allowed_domains%0Ahttp_access%20deny%20all%0A%60%60%60%0A%0AThen%2C%20rebuild%20and%20restart%20the%20ssrf_proxy%20and%20plugin_daemon%20containers%20%28docker-compose%20down%20%26%26%20docker-compose%20up%20-d%29%20to%20apply%20the%20change.%20This%20will%20allow%20the%20Mineru%20plugin%20to%20connect%20to%20mineru.net%20while%20keeping%20your%20current%20FILES_URL%20setup%20for%20image%20display%20in%20the%20Knowledge%20Base%20Q%26A.%20%20%0A%5BReference%5D%28https%3A//github.com/langgenius/dify/blob/6cf71366ba44c1ff538acb760e3fc5853ee31ac8/docker/ssrf_proxy/squid.conf.template%23L22-L30%29) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/29965)

yindo commented

2026-02-21 20:11:21 -05:00

@comaaxl commented on GitHub (Dec 21, 2025):

@dosu
@dosu

I haven't modified the configuration file "docker/ssrf_proxy/squid.conf.template".

After connecting to the "company's Wi-Fi"(10.21.176.242), I used the command "ipconfig getifaddr en0" to obtain the IP address, then set it in FILES_URL as http://[company's Wi-Fi IP]:5001, and left INTERNAL_FILES_URL empty. In this case, Dify can both use the Mineru plugin normally and display images in Knowledge Base Q&A.

However, after connecting to a "mobile hotspot"(172.20.10.2), I used the same command "ipconfig getifaddr en0" to get the IP address, then set it in FILES_URL as http://[mobile hotspot IP]:5001. After that, Mineru throws the following error:

now I have two questions to consult:
1.Why does Mineru fail to work properly when the IP address in FILES_URL is replaced with the one from the mobile hotspot?
2.If I use the company Wi-Fi's IP address in FILES_URL, I have to manually modify the IP in the .env file when the IP changes. This is quite cumbersome—are there any better solutions?

Additionally, I'd like to add that a colleague of mine deployed Dify in the same way on a "Tencent Cloud server". He only needs to set FILES_URL=http://api:5001, and both the Mineru plugin and the image display function work normally. Could this bug of mine be caused by deploying locally on a Mac instead of on a cloud server?

@comaaxl commented on GitHub (Dec 21, 2025): @dosu [@dosu](https://go.dosu.dev/dosubot) I haven't modified the configuration file "docker/ssrf_proxy/squid.conf.template". After connecting to the "company's Wi-Fi"(10.21.176.242), I used the command "ipconfig getifaddr en0" to obtain the IP address, then set it in FILES_URL as http://[company's Wi-Fi IP]:5001, and left INTERNAL_FILES_URL empty. In this case, Dify can both use the Mineru plugin normally and display images in Knowledge Base Q&A. However, after connecting to a "mobile hotspot"(172.20.10.2), I used the same command "ipconfig getifaddr en0" to get the IP address, then set it in FILES_URL as http://[mobile hotspot IP]:5001. After that, Mineru throws the following error: <img width="996" height="498" alt="Image" src="https://github.com/user-attachments/assets/e915c0c5-6d92-4d3e-b74d-6ad35ffc9c12" /> now I have two questions to consult: 1.Why does Mineru fail to work properly when the IP address in FILES_URL is replaced with the one from the mobile hotspot? 2.If I use the company Wi-Fi's IP address in FILES_URL, I have to manually modify the IP in the .env file when the IP changes. This is quite cumbersome—are there any better solutions? Additionally, I'd like to add that a colleague of mine deployed Dify in the same way on a "Tencent Cloud server". He only needs to set FILES_URL=http://api:5001, and both the Mineru plugin and the image display function work normally. Could this bug of mine be caused by deploying locally on a Mac instead of on a cloud server?

yindo commented

2026-02-21 20:11:22 -05:00

@dosubot[bot] commented on GitHub (Dec 21, 2025):

When you switch to a mobile hotspot and set FILES_URL to your new IP, Docker containers on Mac often can't reach the host at that IP due to how Docker Desktop for Mac handles networking. This results in the "No route to host" error for Mineru—your containers can't access the host's file server via the hotspot IP, even though it works on your company Wi-Fi. This is a known limitation of Docker networking on Mac, especially with changing network interfaces and IPs.
You don't need to manually update FILES_URL every time your IP changes. On Mac (and Windows), Docker provides a special DNS name: host.docker.internal. Set both FILES_URL and INTERNAL_FILES_URL to http://host.docker.internal:5001 in your .env file. This alias always points to your host machine from inside containers, regardless of your current network or IP. Make sure port 5001 is published in your docker-compose.yaml under the api service:
```
ports:
  - "5001:5001"
```
Then restart your containers (docker-compose down && docker-compose up -d). This setup works for both browser image display and plugin access, and you won't need to update your IP again when switching networks.
Reference | Reference

Cloud servers (like Tencent Cloud) work with http://api:5001 because all services run inside Docker on a VM with a static internal network, so api:5001 is always reachable from both plugins and the frontend. On your Mac, the host's IP can change and isn't always reachable from containers, so host.docker.internal is the best solution.

If you need Mineru to access external domains (like mineru.net) and run into DNS errors, make sure to whitelist those domains in your SSRF proxy config as discussed earlier, but that's separate from the host IP issue.

Let me know if you need a concrete example .env or docker-compose.yaml snippet!

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 21, 2025):  1. When you switch to a mobile hotspot and set FILES_URL to your new IP, Docker containers on Mac often can't reach the host at that IP due to how Docker Desktop for Mac handles networking. This results in the "No route to host" error for Mineru—your containers can't access the host's file server via the hotspot IP, even though it works on your company Wi-Fi. This is a known limitation of Docker networking on Mac, especially with changing network interfaces and IPs. 2. You don't need to manually update FILES_URL every time your IP changes. On Mac (and Windows), Docker provides a special DNS name: `host.docker.internal`. Set both FILES_URL and INTERNAL_FILES_URL to `http://host.docker.internal:5001` in your `.env` file. This alias always points to your host machine from inside containers, regardless of your current network or IP. Make sure port 5001 is published in your `docker-compose.yaml` under the `api` service: ```yaml ports: - "5001:5001" ``` Then restart your containers (`docker-compose down && docker-compose up -d`). This setup works for both browser image display and plugin access, and you won't need to update your IP again when switching networks. [Reference](https://github.com/langgenius/dify/issues/26860) | [Reference](https://github.com/langgenius/dify/blob/ba73964dfd8f99459a14a73a2297a92ab9c6f156/docker/docker-compose.yaml#L14-L185) Cloud servers (like Tencent Cloud) work with `http://api:5001` because all services run inside Docker on a VM with a static internal network, so `api:5001` is always reachable from both plugins and the frontend. On your Mac, the host's IP can change and isn't always reachable from containers, so `host.docker.internal` is the best solution. If you need Mineru to access external domains (like mineru.net) and run into DNS errors, make sure to whitelist those domains in your SSRF proxy config as discussed earlier, but that's separate from the host IP issue. Let me know if you need a concrete example `.env` or `docker-compose.yaml` snippet!  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/55f766e0-d6c0-4c4e-a8f1-8d7398d6e46f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/55f766e0-d6c0-4c4e-a8f1-8d7398d6e46f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/55f766e0-d6c0-4c4e-a8f1-8d7398d6e46f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/55f766e0-d6c0-4c4e-a8f1-8d7398d6e46f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/55f766e0-d6c0-4c4e-a8f1-8d7398d6e46f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/55f766e0-d6c0-4c4e-a8f1-8d7398d6e46f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/55f766e0-d6c0-4c4e-a8f1-8d7398d6e46f?feedback_type=other) [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=1.%20When%20you%20switch%20to%20a%20mobile%20hotspot%20and%20set%20FILES_URL%20to%20your%20new%20IP%2C%20Docker%20containers%20on%20Mac%20often%20can%27t%20reach%20the%20host%20at%20that%20IP%20due%20to%20how%20Docker%20Desktop%20for%20Mac%20handles%20networking.%20This%20results%20in%20the%20%22No%20route%20to%20host%22%20error%20for%20Mineru%E2%80%94your%20containers%20can%27t%20access%20the%20host%27s%20file%20server%20via%20the%20hotspot%20IP%2C%20even%20though%20it%20works%20on%20your%20company%20Wi-Fi.%20This%20is%20a%20known%20limitation%20of%20Docker%20networking%20on%20Mac%2C%20especially%20with%20changing%20network%20interfaces%20and%20IPs.%0A%0A2.%20You%20don%27t%20need%20to%20manually%20update%20FILES_URL%20every%20time%20your%20IP%20changes.%20On%20Mac%20%28and%20Windows%29%2C%20Docker%20provides%20a%20special%20DNS%20name%3A%20%60host.docker.internal%60.%20Set%20both%20FILES_URL%20and%20INTERNAL_FILES_URL%20to%20%60http%3A//host.docker.internal%3A5001%60%20in%20your%20%60.env%60%20file.%20This%20alias%20always%20points%20to%20your%20host%20machine%20from%20inside%20containers%2C%20regardless%20of%20your%20current%20network%20or%20IP.%20Make%20sure%20port%205001%20is%20published%20in%20your%20%60docker-compose.yaml%60%20under%20the%20%60api%60%20service%3A%0A%20%20%20%60%60%60yaml%0A%20%20%20ports%3A%0A%20%20%20%20%20-%20%225001%3A5001%22%0A%20%20%20%60%60%60%0A%20%20%20Then%20restart%20your%20containers%20%28%60docker-compose%20down%20%26%26%20docker-compose%20up%20-d%60%29.%20This%20setup%20works%20for%20both%20browser%20image%20display%20and%20plugin%20access%2C%20and%20you%20won%27t%20need%20to%20update%20your%20IP%20again%20when%20switching%20networks.%20%20%0A%20%20%20%5BReference%5D%28https%3A//github.com/langgenius/dify/issues/26860%29%20%7C%20%5BReference%5D%28https%3A//github.com/langgenius/dify/blob/ba73964dfd8f99459a14a73a2297a92ab9c6f156/docker/docker-compose.yaml%23L14-L185%29%0A%0ACloud%20servers%20%28like%20Tencent%20Cloud%29%20work%20with%20%60http%3A//api%3A5001%60%20because%20all%20services%20run%20inside%20Docker%20on%20a%20VM%20with%20a%20static%20internal%20network%2C%20so%20%60api%3A5001%60%20is%20always%20reachable%20from%20both%20plugins%20and%20the%20frontend.%20On%20your%20Mac%2C%20the%20host%27s%20IP%20can%20change%20and%20isn%27t%20always%20reachable%20from%20containers%2C%20so%20%60host.docker.internal%60%20is%20the%20best%20solution.%0A%0AIf%20you%20need%20Mineru%20to%20access%20external%20domains%20%28like%20mineru.net%29%20and%20run%20into%20DNS%20errors%2C%20make%20sure%20to%20whitelist%20those%20domains%20in%20your%20SSRF%20proxy%20config%20as%20discussed%20earlier%2C%20but%20that%27s%20separate%20from%20the%20host%20IP%20issue.%0A%0ALet%20me%20know%20if%20you%20need%20a%20concrete%20example%20%60.env%60%20or%20%60docker-compose.yaml%60%20snippet%21) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/29965)

yindo commented

2026-02-21 20:11:22 -05:00

@comaaxl commented on GitHub (Dec 23, 2025):

@dosu
@dosu

My current settings are as follows:
FILES_URL=http://host.docker.internal:5001/
INTERNAL_FILES_URL=

This configuration has resolved the document parsing issue with the Mineru plugin.

However, a new problem has emerged with another plugin. I am using the "Knowledge Pro" plugin and attempting to insert the results parsed by Mineru into the knowledge base, but the following error occurs:

Failed to create document: One or more files not found.

I have tried changing FILES_URL to http://api:5001 and INTERNAL_FILES_URL to http://api:5001 as well, but neither works.
The service API of the knowledge base (where I intend to insert the parsed results) is shown in the image below:

(Do I need to modify the localhost part in the API endpoint http://localhost/v1 of this service API? I have no idea where I can make this change.)

I can see that the API endpoint is displayed as http://localhost/v1. Currently, in the configuration of the "Knowledge Pro" plugin, I have set it to http://[my IP address]/v1. Even if I modify it to http://host.docker.internal/v1, it still fails to work. If I directly replace it with http://localhost/v1, another error occurs as shown in the following image:

By the way, I have deployed Dify locally on my MacBook via Docker Desktop, and I have also added the following entries to the /etc/hosts file:
127.0.0.1 host.docker.internal
localhost host.docker.internal

Additionally, a colleague of mine has the exact same Dify configuration as mine, except that he deployed it on a Tencent Cloud server, and his "Knowledge Pro" plugin works properly without any issues.

Please help me analyze the root cause of this problem and provide a solution. Thank you!

env.txt

docker-compose.yaml

@comaaxl commented on GitHub (Dec 23, 2025): @dosu [@dosu](https://go.dosu.dev/dosubot) My current settings are as follows: FILES_URL=http://host.docker.internal:5001/ INTERNAL_FILES_URL= This configuration has resolved the document parsing issue with the Mineru plugin. However, a new problem has emerged with another plugin. I am using the "Knowledge Pro" plugin and attempting to insert the results parsed by Mineru into the knowledge base, but the following error occurs: <img width="705" height="117" alt="Image" src="https://github.com/user-attachments/assets/6d6ab646-55bd-45e2-8c85-4c61e67117ca" /> Failed to create document: One or more files not found. <img width="1298" height="717" alt="Image" src="https://github.com/user-attachments/assets/85221518-baed-4bcf-8bcf-cb6528363735" /> I have tried changing FILES_URL to http://api:5001 and INTERNAL_FILES_URL to http://api:5001 as well, but neither works. The service API of the knowledge base (where I intend to insert the parsed results) is shown in the image below: <img width="440" height="236" alt="Image" src="https://github.com/user-attachments/assets/771182d4-39e3-47ba-bab4-64357adb07c0" /> (Do I need to modify the localhost part in the API endpoint http://localhost/v1 of this service API? I have no idea where I can make this change.) I can see that the API endpoint is displayed as http://localhost/v1. Currently, in the configuration of the "Knowledge Pro" plugin, I have set it to http://[my IP address]/v1. Even if I modify it to http://host.docker.internal/v1, it still fails to work. If I directly replace it with http://localhost/v1, another error occurs as shown in the following image: <img width="1096" height="728" alt="Image" src="https://github.com/user-attachments/assets/af3ba72f-734c-432c-9a99-d88cc19d678b" /> By the way, I have deployed Dify locally on my MacBook via Docker Desktop, and I have also added the following entries to the /etc/hosts file: 127.0.0.1 host.docker.internal localhost host.docker.internal Additionally, a colleague of mine has the exact same Dify configuration as mine, except that he deployed it on a Tencent Cloud server, and his "Knowledge Pro" plugin works properly without any issues. Please help me analyze the root cause of this problem and provide a solution. Thank you! [env.txt](https://github.com/user-attachments/files/24311287/env.txt) [docker-compose.yaml](https://github.com/user-attachments/files/24311288/docker-compose.yaml)

yindo commented

2026-02-21 20:11:22 -05:00

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

The "One or more files not found" error in the Knowledge Pro plugin is almost always caused by file URLs that are not accessible from inside the plugin_daemon container. On Mac with Docker Desktop, using host.docker.internal for FILES_URL works for most plugins, but some (like Knowledge Pro) expect to access files via the internal Docker network, just like on cloud servers.

To fix this, set both FILES_URL and INTERNAL_FILES_URL to http://api:5001 in your .env file, and make sure your docker-compose.yaml exposes port 5001 for the api service:

services:
  api:
    ...
    ports:
      - "5001:5001"

After updating, restart all containers. This setup matches what works on your colleague's Tencent Cloud server and is the recommended approach for plugins that need internal access to files and the API [source].

Also, in the Knowledge Pro plugin config, set the API base URL to http://api:5001/v1 (not localhost, not your host IP, not host.docker.internal). The plugin_daemon container can always reach api:5001 on the Docker network, but not localhost or your host IP.

If you still see errors, double-check that the plugin_daemon container can resolve and connect to api:5001:5001 (try docker exec -it <plugin_daemon_container> curl http://api:5001/v1/health).

Let me know if you need a concrete example of the .env or docker-compose.yaml!

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 23, 2025):  The "One or more files not found" error in the Knowledge Pro plugin is almost always caused by file URLs that are not accessible from inside the plugin_daemon container. On Mac with Docker Desktop, using `host.docker.internal` for FILES_URL works for most plugins, but some (like Knowledge Pro) expect to access files via the internal Docker network, just like on cloud servers. To fix this, set both FILES_URL and INTERNAL_FILES_URL to `http://api:5001` in your `.env` file, and make sure your `docker-compose.yaml` exposes port 5001 for the api service: ```yaml services: api: ... ports: - "5001:5001" ``` After updating, restart all containers. This setup matches what works on your colleague's Tencent Cloud server and is the recommended approach for plugins that need internal access to files and the API [[source](https://github.com/langgenius/dify/discussions/28886)]. Also, in the Knowledge Pro plugin config, set the API base URL to `http://api:5001/v1` (not localhost, not your host IP, not host.docker.internal). The plugin_daemon container can always reach `api:5001` on the Docker network, but not `localhost` or your host IP. If you still see errors, double-check that the plugin_daemon container can resolve and connect to `api:5001:5001` (try `docker exec -it <plugin_daemon_container> curl http://api:5001/v1/health`). Let me know if you need a concrete example of the `.env` or `docker-compose.yaml`!  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/11080fce-be64-4f86-bd69-dc78e9b7c626?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/11080fce-be64-4f86-bd69-dc78e9b7c626?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/11080fce-be64-4f86-bd69-dc78e9b7c626?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/11080fce-be64-4f86-bd69-dc78e9b7c626?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/11080fce-be64-4f86-bd69-dc78e9b7c626?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/11080fce-be64-4f86-bd69-dc78e9b7c626?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/11080fce-be64-4f86-bd69-dc78e9b7c626?feedback_type=other) [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20%22One%20or%20more%20files%20not%20found%22%20error%20in%20the%20Knowledge%20Pro%20plugin%20is%20almost%20always%20caused%20by%20file%20URLs%20that%20are%20not%20accessible%20from%20inside%20the%20plugin_daemon%20container.%20On%20Mac%20with%20Docker%20Desktop%2C%20using%20%60host.docker.internal%60%20for%20FILES_URL%20works%20for%20most%20plugins%2C%20but%20some%20%28like%20Knowledge%20Pro%29%20expect%20to%20access%20files%20via%20the%20internal%20Docker%20network%2C%20just%20like%20on%20cloud%20servers.%0A%0ATo%20fix%20this%2C%20set%20both%20FILES_URL%20and%20INTERNAL_FILES_URL%20to%20%60http%3A//api%3A5001%60%20in%20your%20%60.env%60%20file%2C%20and%20make%20sure%20your%20%60docker-compose.yaml%60%20exposes%20port%205001%20for%20the%20api%20service%3A%0A%0A%60%60%60yaml%0Aservices%3A%0A%20%20api%3A%0A%20%20%20%20...%0A%20%20%20%20ports%3A%0A%20%20%20%20%20%20-%20%225001%3A5001%22%0A%60%60%60%0A%0AAfter%20updating%2C%20restart%20all%20containers.%20This%20setup%20matches%20what%20works%20on%20your%20colleague%27s%20Tencent%20Cloud%20server%20and%20is%20the%20recommended%20approach%20for%20plugins%20that%20need%20internal%20access%20to%20files%20and%20the%20API%20%5B%5Bsource%5D%28https%3A//github.com/langgenius/dify/discussions/28886%29%5D.%0A%0AAlso%2C%20in%20the%20Knowledge%20Pro%20plugin%20config%2C%20set%20the%20API%20base%20URL%20to%20%60http%3A//api%3A5001/v1%60%20%28not%20localhost%2C%20not%20your%20host%20IP%2C%20not%20host.docker.internal%29.%20The%20plugin_daemon%20container%20can%20always%20reach%20%60api%3A5001%60%20on%20the%20Docker%20network%2C%20but%20not%20%60localhost%60%20or%20your%20host%20IP.%0A%0AIf%20you%20still%20see%20errors%2C%20double-check%20that%20the%20plugin_daemon%20container%20can%20resolve%20and%20connect%20to%20%60api%3A5001%3A5001%60%20%28try%20%60docker%20exec%20-it%20%3Cplugin_daemon_container%3E%20curl%20http%3A//api%3A5001/v1/health%60%29.%0A%0ALet%20me%20know%20if%20you%20need%20a%20concrete%20example%20of%20the%20%60.env%60%20or%20%60docker-compose.yaml%60%21) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/29965)

yindo commented

2026-02-21 20:11:22 -05:00

@comaaxl commented on GitHub (Dec 23, 2025):

@dosu
@dosu
I have set both FILES_URL and INTERNAL_FILES_URL to http://api:5001 in my .env file and restart all containers.
and exposes port 5001 for the api service.
Also, in the Knowledge Pro plugin config, I set the API base URL to http://api:5001/v1
but it does not works and the following error occurs:

plugin_daemon container ：

@comaaxl commented on GitHub (Dec 23, 2025): @dosu [@dosu](https://go.dosu.dev/dosubot) I have set both FILES_URL and INTERNAL_FILES_URL to http://api:5001 in my .env file and restart all containers. and exposes port 5001 for the api service. Also, in the Knowledge Pro plugin config, I set the API base URL to http://api:5001/v1 but it does not works and the following error occurs: <img width="1298" height="717" alt="Image" src="https://github.com/user-attachments/assets/3333b8f0-5f99-4a94-826f-ee4f7e5a171c" /> plugin_daemon container ： <img width="963" height="335" alt="Image" src="https://github.com/user-attachments/assets/2b703e3b-b394-4db5-bd5e-ecffa34ffb7a" />

yindo commented

2026-02-21 20:11:22 -05:00

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

The "One or more files not found" error in Knowledge Pro means the plugin can't find or access the files referenced by their IDs in the Dify database. This is almost always a network or configuration issue inside Docker.

Your setup—FILES_URL and INTERNAL_FILES_URL both set to http://api:5001, port 5001 exposed, and the Knowledge Pro API base URL set to http://api:5001/v1—is correct for Docker Compose. This matches what works on cloud servers and is the recommended config for plugin file access and API calls (reference, reference).

The 404 errors you see when curling /v1/health are expected—Dify's health check endpoint is /health, not /v1/health (reference). So your containers can reach the API, but the endpoint path is wrong.

If you still get "One or more files not found," double-check these:

The file IDs passed to Knowledge Pro must exist in the Dify database for the current tenant. If the files were uploaded in a different workflow, or the IDs are missing/invalid, you'll get this error (reference).
The plugin_daemon container must be able to reach api:5001 on the Docker network. Try:
```
docker exec -it <plugin_daemon_container> curl http://api:5001/health
```
You should get a JSON response with status "ok".
Make sure your workflow is passing the correct file IDs from the Mineru output to Knowledge Pro. If you can, inspect the JSON input to Knowledge Pro and verify the file IDs are present and match files in the Dify database.

If all of the above checks out and the error persists, it's likely a workflow or data mapping issue—double-check how file IDs are handed off between nodes.

Let me know if you want help inspecting the workflow JSON or debugging the file ID handoff!

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 23, 2025):  The "One or more files not found" error in Knowledge Pro means the plugin can't find or access the files referenced by their IDs in the Dify database. This is almost always a network or configuration issue inside Docker. Your setup—FILES_URL and INTERNAL_FILES_URL both set to `http://api:5001`, port 5001 exposed, and the Knowledge Pro API base URL set to `http://api:5001/v1`—is correct for Docker Compose. This matches what works on cloud servers and is the recommended config for plugin file access and API calls ([reference](https://github.com/langgenius/dify/blob/de021ff3e0b56704878d3a3f062cd34f4eaa0d80/docker/.env.example#L44-L151), [reference](https://github.com/langgenius/dify/blob/de021ff3e0b56704878d3a3f062cd34f4eaa0d80/api/configs/feature/__init__.py#L301-L315)). The 404 errors you see when curling `/v1/health` are expected—Dify's health check endpoint is `/health`, not `/v1/health` ([reference](https://github.com/langgenius/dify/blob/de021ff3e0b56704878d3a3f062cd34f4eaa0d80/api/extensions/ext_app_metrics.py#L19-L25)). So your containers can reach the API, but the endpoint path is wrong. If you still get "One or more files not found," double-check these: - The file IDs passed to Knowledge Pro must exist in the Dify database for the current tenant. If the files were uploaded in a different workflow, or the IDs are missing/invalid, you'll get this error ([reference](https://github.com/langgenius/dify/blob/de021ff3e0b56704878d3a3f062cd34f4eaa0d80/api/services/dataset_service.py#L1662-L1705)). - The plugin_daemon container must be able to reach `api:5001` on the Docker network. Try: ``` docker exec -it <plugin_daemon_container> curl http://api:5001/health ``` You should get a JSON response with status "ok". - Make sure your workflow is passing the correct file IDs from the Mineru output to Knowledge Pro. If you can, inspect the JSON input to Knowledge Pro and verify the file IDs are present and match files in the Dify database. If all of the above checks out and the error persists, it's likely a workflow or data mapping issue—double-check how file IDs are handed off between nodes. Let me know if you want help inspecting the workflow JSON or debugging the file ID handoff!  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/f73ee45f-5e2a-4fe4-b2ba-785da1dfcf98?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f73ee45f-5e2a-4fe4-b2ba-785da1dfcf98?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f73ee45f-5e2a-4fe4-b2ba-785da1dfcf98?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f73ee45f-5e2a-4fe4-b2ba-785da1dfcf98?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f73ee45f-5e2a-4fe4-b2ba-785da1dfcf98?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f73ee45f-5e2a-4fe4-b2ba-785da1dfcf98?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f73ee45f-5e2a-4fe4-b2ba-785da1dfcf98?feedback_type=other) [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20%22One%20or%20more%20files%20not%20found%22%20error%20in%20Knowledge%20Pro%20means%20the%20plugin%20can%27t%20find%20or%20access%20the%20files%20referenced%20by%20their%20IDs%20in%20the%20Dify%20database.%20This%20is%20almost%20always%20a%20network%20or%20configuration%20issue%20inside%20Docker.%0A%0AYour%20setup%E2%80%94FILES_URL%20and%20INTERNAL_FILES_URL%20both%20set%20to%20%60http%3A//api%3A5001%60%2C%20port%205001%20exposed%2C%20and%20the%20Knowledge%20Pro%20API%20base%20URL%20set%20to%20%60http%3A//api%3A5001/v1%60%E2%80%94is%20correct%20for%20Docker%20Compose.%20This%20matches%20what%20works%20on%20cloud%20servers%20and%20is%20the%20recommended%20config%20for%20plugin%20file%20access%20and%20API%20calls%20%28%5Breference%5D%28https%3A//github.com/langgenius/dify/blob/de021ff3e0b56704878d3a3f062cd34f4eaa0d80/docker/.env.example%23L44-L151%29%2C%20%5Breference%5D%28https%3A//github.com/langgenius/dify/blob/de021ff3e0b56704878d3a3f062cd34f4eaa0d80/api/configs/feature/__init__.py%23L301-L315%29%29.%0A%0AThe%20404%20errors%20you%20see%20when%20curling%20%60/v1/health%60%20are%20expected%E2%80%94Dify%27s%20health%20check%20endpoint%20is%20%60/health%60%2C%20not%20%60/v1/health%60%20%28%5Breference%5D%28https%3A//github.com/langgenius/dify/blob/de021ff3e0b56704878d3a3f062cd34f4eaa0d80/api/extensions/ext_app_metrics.py%23L19-L25%29%29.%20So%20your%20containers%20can%20reach%20the%20API%2C%20but%20the%20endpoint%20path%20is%20wrong.%0A%0AIf%20you%20still%20get%20%22One%20or%20more%20files%20not%20found%2C%22%20double-check%20these%3A%0A%0A-%20The%20file%20IDs%20passed%20to%20Knowledge%20Pro%20must%20exist%20in%20the%20Dify%20database%20for%20the%20current%20tenant.%20If%20the%20files%20were%20uploaded%20in%20a%20different%20workflow%2C%20or%20the%20IDs%20are%20missing/invalid%2C%20you%27ll%20get%20this%20error%20%28%5Breference%5D%28https%3A//github.com/langgenius/dify/blob/de021ff3e0b56704878d3a3f062cd34f4eaa0d80/api/services/dataset_service.py%23L1662-L1705%29%29.%0A-%20The%20plugin_daemon%20container%20must%20be%20able%20to%20reach%20%60api%3A5001%60%20on%20the%20Docker%20network.%20Try%3A%20%20%0A%20%20%60%60%60%0A%20%20docker%20exec%20-it%20%3Cplugin_daemon_container%3E%20curl%20http%3A//api%3A5001/health%0A%20%20%60%60%60%0A%20%20You%20should%20get%20a%20JSON%20response%20with%20status%20%22ok%22.%0A-%20Make%20sure%20your%20workflow%20is%20passing%20the%20correct%20file%20IDs%20from%20the%20Mineru%20output%20to%20Knowledge%20Pro.%20If%20you%20can%2C%20inspect%20the%20JSON%20input%20to%20Knowledge%20Pro%20and%20verify%20the%20file%20IDs%20are%20present%20and%20match%20files%20in%20the%20Dify%20database.%0A%0AIf%20all%20of%20the%20above%20checks%20out%20and%20the%20error%20persists%2C%20it%27s%20likely%20a%20workflow%20or%20data%20mapping%20issue%E2%80%94double-check%20how%20file%20IDs%20are%20handed%20off%20between%20nodes.%0A%0ALet%20me%20know%20if%20you%20want%20help%20inspecting%20the%20workflow%20JSON%20or%20debugging%20the%20file%20ID%20handoff%21) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/29965)

yindo commented

2026-02-21 20:11:22 -05:00

@comaaxl commented on GitHub (Dec 23, 2025):

@dosu
@dosu

I suspect the issue might be related to the API endpoint address of the service API. I have redeployed a new instance of Dify on a virtual machine with exactly the same plugin parameter configurations, and the Dify on the virtual machine works properly without any issues. The API endpoint address of the Dify knowledge base service API on the virtual machine is http://[virtual machine IP address]/v1.

So, could it be that I need to replace the "localhost" part in the API endpoint address http://localhost/v1 of the Dify service API deployed on my Mac with the "local machine's IP address" or "host.docker.internal"? However, I have no idea which configuration file I can edit to make this change. Could you please tell me?

@comaaxl commented on GitHub (Dec 23, 2025): @dosu [@dosu](https://go.dosu.dev/dosubot) I suspect the issue might be related to the API endpoint address of the service API. I have redeployed a new instance of Dify on a virtual machine with exactly the same plugin parameter configurations, and the Dify on the virtual machine works properly without any issues. The API endpoint address of the Dify knowledge base service API on the virtual machine is http://[virtual machine IP address]/v1. So, could it be that I need to replace the "localhost" part in the API endpoint address http://localhost/v1 of the Dify service API deployed on my Mac with the "local machine's IP address" or "host.docker.internal"? However, I have no idea which configuration file I can edit to make this change. Could you please tell me?

yindo commented

2026-02-21 20:11:22 -05:00

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

Yes, you should replace "localhost" in the API endpoint address with either your Mac's LAN IP or host.docker.internal for Docker Desktop on Mac. This is because "localhost" inside a container refers to the container itself, not your host machine, so plugins and other containers can't reach the API service at that address source.

To change this, edit your .env file and set:

SERVICE_API_URL=http://host.docker.internal:5001/v1
CONSOLE_API_URL=http://host.docker.internal:5001
APP_API_URL=http://host.docker.internal:5001
DIFY_BIND_ADDRESS=0.0.0.0

Or use your LAN IP instead of host.docker.internal if you prefer. Make sure port 5001 is exposed in your docker-compose.yaml for the api service.

After editing the .env file, restart all Docker containers:

docker-compose down
docker-compose up -d

This will update the API endpoint address shown in the UI and make it accessible to plugins and containers source.

You can verify the change by checking the API endpoint in the UI or running:

docker exec -it <plugin_daemon_container> curl http://host.docker.internal:5001/health

Let me know if you need help with the exact .env or docker-compose.yaml setup!

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 23, 2025):  Yes, you should replace "localhost" in the API endpoint address with either your Mac's LAN IP or `host.docker.internal` for Docker Desktop on Mac. This is because "localhost" inside a container refers to the container itself, not your host machine, so plugins and other containers can't reach the API service at that address [source](https://github.com/langgenius/dify/issues/24909#issuecomment-3241615337). To change this, edit your `.env` file and set: ``` SERVICE_API_URL=http://host.docker.internal:5001/v1 CONSOLE_API_URL=http://host.docker.internal:5001 APP_API_URL=http://host.docker.internal:5001 DIFY_BIND_ADDRESS=0.0.0.0 ``` Or use your LAN IP instead of `host.docker.internal` if you prefer. Make sure port 5001 is exposed in your `docker-compose.yaml` for the `api` service. After editing the `.env` file, restart all Docker containers: ```bash docker-compose down docker-compose up -d ``` This will update the API endpoint address shown in the UI and make it accessible to plugins and containers [source](https://github.com/langgenius/dify/blob/4d48791f3cda0d9ef207be52613d77f4134de168/docker/.env.example#L9-L58). You can verify the change by checking the API endpoint in the UI or running: ```bash docker exec -it <plugin_daemon_container> curl http://host.docker.internal:5001/health ``` Let me know if you need help with the exact `.env` or `docker-compose.yaml` setup!  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/c5c668af-5512-4915-941a-41332311e950?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c5c668af-5512-4915-941a-41332311e950?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c5c668af-5512-4915-941a-41332311e950?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c5c668af-5512-4915-941a-41332311e950?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c5c668af-5512-4915-941a-41332311e950?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c5c668af-5512-4915-941a-41332311e950?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c5c668af-5512-4915-941a-41332311e950?feedback_type=other) [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Yes%2C%20you%20should%20replace%20%22localhost%22%20in%20the%20API%20endpoint%20address%20with%20either%20your%20Mac%27s%20LAN%20IP%20or%20%60host.docker.internal%60%20for%20Docker%20Desktop%20on%20Mac.%20This%20is%20because%20%22localhost%22%20inside%20a%20container%20refers%20to%20the%20container%20itself%2C%20not%20your%20host%20machine%2C%20so%20plugins%20and%20other%20containers%20can%27t%20reach%20the%20API%20service%20at%20that%20address%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/24909%23issuecomment-3241615337%29.%0A%0ATo%20change%20this%2C%20edit%20your%20%60.env%60%20file%20and%20set%3A%0A%0A%60%60%60%0ASERVICE_API_URL%3Dhttp%3A//host.docker.internal%3A5001/v1%0ACONSOLE_API_URL%3Dhttp%3A//host.docker.internal%3A5001%0AAPP_API_URL%3Dhttp%3A//host.docker.internal%3A5001%0ADIFY_BIND_ADDRESS%3D0.0.0.0%0A%60%60%60%0A%0AOr%20use%20your%20LAN%20IP%20instead%20of%20%60host.docker.internal%60%20if%20you%20prefer.%20Make%20sure%20port%205001%20is%20exposed%20in%20your%20%60docker-compose.yaml%60%20for%20the%20%60api%60%20service.%0A%0AAfter%20editing%20the%20%60.env%60%20file%2C%20restart%20all%20Docker%20containers%3A%0A%0A%60%60%60bash%0Adocker-compose%20down%0Adocker-compose%20up%20-d%0A%60%60%60%0A%0AThis%20will%20update%20the%20API%20endpoint%20address%20shown%20in%20the%20UI%20and%20make%20it%20accessible%20to%20plugins%20and%20containers%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/4d48791f3cda0d9ef207be52613d77f4134de168/docker/.env.example%23L9-L58%29.%0A%0AYou%20can%20verify%20the%20change%20by%20checking%20the%20API%20endpoint%20in%20the%20UI%20or%20running%3A%0A%0A%60%60%60bash%0Adocker%20exec%20-it%20%3Cplugin_daemon_container%3E%20curl%20http%3A//host.docker.internal%3A5001/health%0A%60%60%60%0A%0ALet%20me%20know%20if%20you%20need%20help%20with%20the%20exact%20%60.env%60%20or%20%60docker-compose.yaml%60%20setup%21) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/29965)

yindo commented

2026-02-21 20:11:22 -05:00

@comaaxl commented on GitHub (Dec 24, 2025):

@dosu
@dosu

I have tried all the methods you suggested, but the error still persists.
It feels like it’s just not usable at all. I wonder if you have ever tested all Dify functions with a local deployment on a Mac—it really seems to have quite a few issues. o(╥﹏╥)o

@comaaxl commented on GitHub (Dec 24, 2025): @dosu [@dosu](https://go.dosu.dev/dosubot) I have tried all the methods you suggested, but the error still persists. It feels like it’s just not usable at all. I wonder if you have ever tested all Dify functions with a local deployment on a Mac—it really seems to have quite a few issues. o(╥﹏╥)o

yindo commented

2026-02-21 20:11:22 -05:00

@dosubot[bot] commented on GitHub (Dec 24, 2025):

I totally get your frustration—what you’re running into is a common pain point with Docker Desktop on Mac, especially for complex apps like Dify that rely on plugins and internal networking. You’ve already tried all the recommended config changes (FILES_URL, INTERNAL_FILES_URL, SERVICE_API_URL, etc.), but some plugins (like Knowledge Pro) still can’t reliably access files or APIs because of how Docker on Mac handles networking and host/container communication. There aren’t any official platform-specific workarounds in the Dify docs or code for these issues, and the same configs work fine on cloud servers or Linux VMs, which have more predictable networking.

At this point, the most reliable way to get all Dify features and plugins working is to deploy on a Linux VM (locally or in the cloud) or use a remote Docker host. That’s why your colleague’s Tencent Cloud setup works out of the box, while Mac local deployments often hit these weird edge cases. If you want, I can help you set up a Linux VM or walk through your workflow to see if there’s any last thing to try—but for full stability, a Linux-based environment is the best bet.

Let me know if you want step-by-step help with an alternative deployment or if you want to dig deeper into your current workflow!

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 24, 2025):  I totally get your frustration—what you’re running into is a common pain point with Docker Desktop on Mac, especially for complex apps like Dify that rely on plugins and internal networking. You’ve already tried all the recommended config changes (FILES_URL, INTERNAL_FILES_URL, SERVICE_API_URL, etc.), but some plugins (like Knowledge Pro) still can’t reliably access files or APIs because of how Docker on Mac handles networking and host/container communication. There aren’t any official platform-specific workarounds in the Dify docs or code for these issues, and the same configs work fine on cloud servers or Linux VMs, which have more predictable networking. At this point, the most reliable way to get all Dify features and plugins working is to deploy on a Linux VM (locally or in the cloud) or use a remote Docker host. That’s why your colleague’s Tencent Cloud setup works out of the box, while Mac local deployments often hit these weird edge cases. If you want, I can help you set up a Linux VM or walk through your workflow to see if there’s any last thing to try—but for full stability, a Linux-based environment is the best bet. Let me know if you want step-by-step help with an alternative deployment or if you want to dig deeper into your current workflow!  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/368903d7-67a6-4209-bdfd-414917072aad?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/368903d7-67a6-4209-bdfd-414917072aad?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/368903d7-67a6-4209-bdfd-414917072aad?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/368903d7-67a6-4209-bdfd-414917072aad?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/368903d7-67a6-4209-bdfd-414917072aad?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/368903d7-67a6-4209-bdfd-414917072aad?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/368903d7-67a6-4209-bdfd-414917072aad?feedback_type=other) [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=I%20totally%20get%20your%20frustration%E2%80%94what%20you%E2%80%99re%20running%20into%20is%20a%20common%20pain%20point%20with%20Docker%20Desktop%20on%20Mac%2C%20especially%20for%20complex%20apps%20like%20Dify%20that%20rely%20on%20plugins%20and%20internal%20networking.%20You%E2%80%99ve%20already%20tried%20all%20the%20recommended%20config%20changes%20%28FILES_URL%2C%20INTERNAL_FILES_URL%2C%20SERVICE_API_URL%2C%20etc.%29%2C%20but%20some%20plugins%20%28like%20Knowledge%20Pro%29%20still%20can%E2%80%99t%20reliably%20access%20files%20or%20APIs%20because%20of%20how%20Docker%20on%20Mac%20handles%20networking%20and%20host/container%20communication.%20There%20aren%E2%80%99t%20any%20official%20platform-specific%20workarounds%20in%20the%20Dify%20docs%20or%20code%20for%20these%20issues%2C%20and%20the%20same%20configs%20work%20fine%20on%20cloud%20servers%20or%20Linux%20VMs%2C%20which%20have%20more%20predictable%20networking.%0A%0AAt%20this%20point%2C%20the%20most%20reliable%20way%20to%20get%20all%20Dify%20features%20and%20plugins%20working%20is%20to%20deploy%20on%20a%20Linux%20VM%20%28locally%20or%20in%20the%20cloud%29%20or%20use%20a%20remote%20Docker%20host.%20That%E2%80%99s%20why%20your%20colleague%E2%80%99s%20Tencent%20Cloud%20setup%20works%20out%20of%20the%20box%2C%20while%20Mac%20local%20deployments%20often%20hit%20these%20weird%20edge%20cases.%20If%20you%20want%2C%20I%20can%20help%20you%20set%20up%20a%20Linux%20VM%20or%20walk%20through%20your%20workflow%20to%20see%20if%20there%E2%80%99s%20any%20last%20thing%20to%20try%E2%80%94but%20for%20full%20stability%2C%20a%20Linux-based%20environment%20is%20the%20best%20bet.%0A%0ALet%20me%20know%20if%20you%20want%20step-by-step%20help%20with%20an%20alternative%20deployment%20or%20if%20you%20want%20to%20dig%20deeper%20into%20your%20current%20workflow%21) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/29965)

yindo referenced this issue

2026-02-21 20:45:52 -05:00

[PR #21198] Add Env 'CELERY_SENTINEL_PASSWORD' for celery connect redis sentinel. #29595

Sign in to join this conversation.

Branches Tags

main

deploy/enterprise

gareth/esq1-170-rbac-for-agent

yanli/refactor-sandbox-and-e2b

codex/strengthen-tool-provider-types

copilot/fix-security-issue

0721-happy-path-smoke

feat/ws-proxy-support

chore/support-preview-mode-fe

deploy/saas

linw/snp-549-reauth-after-accepting-invitation

0721-document-detail

feat/hitl-im-dev

fix/empty-dataset-list-tip

feat/ce-telemetry-dev

0720-documents-tasks

deploy/agent

release/e-1.11.4

fix/cus-1422-enterprise-api-timeout

hotfix/cus-1422-enterprise-api-timeout

perf/optimize-markdown-renderer

feat/fix-undefined-answer-preview

hotfix/1.15.0-fix.15

dependabot/uv/dify-agent/pillow-12.3.0

0720-crawl-selection

0720-crawl-preview

0720-source-connections

0720-create-knowledge

0720-new-rag-contracts

laipz8200/human-input-loop-iteration

0720-new-rag-list

codex/migrate-knowledge-fs

hotfix/1.15.0-fix.14

lts/1.13.x

deploy/workflow-archive-catalog-discovery

dependabot/uv/api/pydantic-09001a97e5

laipz8200/completion-workflow-entry

dependabot/uv/api/lts/1.13.x/python-packages-6c2bf7110c

dependabot/uv/api/storage-4219cfbece

dependabot/uv/api/lts/1.13.x/dev-6fc4f8b90c

dependabot/uv/api/llm-46e0cee538

dependabot/uv/api/lts/1.13.x/vdb-72526f7860

dependabot/uv/api/opentelemetry-b8005594e1

dependabot/uv/api/lts/1.13.x/storage-4310e8b8d8

dependabot/uv/api/lts/1.13.x/database-c0fba9b420

dependabot/uv/api/lts/1.13.x/llm-5ce1d68736

dependabot/uv/api/lts/1.13.x/pydantic-09001a97e5

dependabot/uv/api/lts/1.13.x/opentelemetry-b8005594e1

dependabot/uv/api/google-68de7a6be5

dependabot/github_actions/lts/1.13.x/github-actions-dependencies-1a36b91cf1

dependabot/uv/api/lts/1.13.x/google-c93828e58f

dependabot/uv/api/lts/1.13.x/flask-1086fc46af

0717-knowledge-fs-contract

feat/secret-scrub-persistence

feat/llm-ft-timeout

feat/appdeploy-selected-workflow-dsl

0715-new-rag

laipz8200/llm-environment-variables

release/ee-1.15.0-hotfix

laipz8200/chore-remove-feature-preview-root-env

dependabot/go_modules/dify-agent-runtime/golang.org/x/net-0.55.0

hotfix/1.15.0-fix.12

hotfix/1.15.0-fix.12-cherrypick

hotfix/1.15.0-fix.13

build/invite-seats-precheck

hotfix/1.15.0-fix.11

laipz8200/workflow-persistence-mixed-mode

hotfix/1.15.0-fix.10

zhangxin/eng-558-licensed-seats-1.15

fix/wta-1307-effect-suspense-read

feat/cli-skills-agents

0713-vp-lint

deploy/dev

fix/agent-roster-answer-completion-main

feat/pay-by-invoice

codex/run-external-e2e-main-ci

agent/remove-sandbox-bind-mounts

feat/agent-v2-e2e-test

hotfix/1.15.0-fix.9

hotfix/1.15.0-fix.8

build/test-archive-export

linw/restore-agent-message-delta-feat

hotfix/1.15.0-fix.7

hotfix/1.15.0-fix.6

codex/pr-38227-session-types

codex/pr-38227-session-scope-split

fix/ui-fix

hotfix/1.15.0-fix.4

codex/review-pr-38480

hotfix/1.15.0-fix.2

copilot/fix-web-full-stack-e2e-job

fix/dify-2738-agent-node-dsl-export

hotfix/1.15.0-fix.3

fix/scope-segment-batch-delete

laipz8200/scope-segment-route-lookup

chore/i18n-sync-7b7956f3e7ca-e901a65a

codex/upgrade-orpc-v2-beta

hotfix/1.15.0-fix.1

codex/upgrade-openapi-ts-autofix

codex/upgrade-next-16-3-preview

hotfix/1.15.0-fix.0

hotfix/web-detail-adjustment-before-release

release/e-1.15.0

codex/replace-lamejs-with-mediabunny

copilot/add-more-tests

deploy/archive-db-resilience

fix/studio-nav-home-button

hotfix/1.14.2-fix.13

worktree-token-expired-error-code

hotfix-1.14.2-fix.12

codex/agent-v2-state-graph

codex/refactor-deployment-detail-components

hotfix/1.14.2-fix.12

build/fix/workflow-error-hanging

work/dify-2585-agent-drafts-pr

fix/dify-2574-soul-files-kv

fix/dify-2554-debug-conversation-per-user

hotfix/1.14.2-fix.11

feat/openapi-rbac

test/cli-e2e-error-body-contract

build/optimize-clean-messages-eligible-apps

zhaohao1004/optimize-clean-messages-cursor

gh-readonly-queue/main/pr-37592-c71f03f5902031b7c02e61af3aff5c2dee6f7d85

build/optimize-clean-messages-cursor

feat/country

codex/vp-fmt-migration

hotfix/1.14.2-fix.10

hotfix/1.14.2-fix.9

hotfix/1.14.2-fix.8

hotfix/1.14.2-fix.7

hotfix/1.14.2-fix.6

codex/page-title-updates

feat/agent-mention-stable-ids

fix/guard-workspace-with-defualt-roles

build/pr-37227-free-plan-workflow-run-cleanup

feat/cli-e2e-test-suite

feat/ui-start-node

feat/hitl-file-in-body

copilot/dify-team-question-agent-node

fix/wta-438-device-sso-redirect-origin

hotfix/1.14.2-fix.5

feat/dev-snippet-fronted

feat/mcp-token-transfer

chore/keep-info-icon-the-same-postion

codex/local-app-list-tag-filter

feat/snippet-new

hotfix/1.14.2-fix.4

codex/migrate-var-reference-combobox

hotfix/1.14.2-fix.3

feat/marketplace-template

chore/deploy-saas-workflow

hotfix/1.14.2-fix.2

build/cli

codex/snp-406-pointer-position-ref

hotfix/1.14.1-fix.3

build/feat/model-type-migration-script

fix/webapp-disabled-not-jump-to-webapp-login

fix/lb-model-type-dedup

song/eng-379-file-output-check-executor

chore/bump-authlib-1.6.12

fix/tag-trigger-preserve-case

chore/bump-sendgrid-lts-1.13.x

fix/model-type-enum-construction

refactor/add-missing-override-decorator

work/web-mcp-1.14.1

copilot/check-runtime-limits

laipz8200/workflow-response-stream-filter

copilot/query-issues-pr-images

laipz8200/fix-autofix-contract-generation

copilot/fix-autofix-job-failure

codex/deprecate-sys-files-compat

codex/fix-scrolling-issue-with-overflow-visible

copilot/research-retrieval-attachment-consumption

copilot/research-agent-node-implementation

chore/upgrade-xyflow-v12

hotfix/1.14.1-fix.1

build/1.14.1-fix.1-langfuse

hotfix/1.14.1-fix.2

feat/lts-lazy-dialogue-count

fix/can-not-create-knowledge

codex/fix-marketplace-hero-shake

codex/tag-name-url-filter

upgrade-graphon-to-0-3-0

codex/app-delete-enter-confirm

build/sample-tidb

codex/revert-pr-35708

chore/remove-dify-deploy-script

chore/simpler-deploy

lts/1.13.x-fix-35910

feat/storage-path-prefix

hotfix/1.13.3-fix10

hotfix/1.13.3-fix9

hotfix/1.14.0-fix.4

hotfix/1.14.0-fix.3

hotfix/1.14.0-fix.2

revert-35748-4-30-open-api

feat/upgrade-graphon

copilot/research-celery-task-ttl

hotfix/1.14.0-fix.1

copilot/fix-css-issue

feat/s3-public-base-url

hotfix/1.13.3-fix8

build/depot-speed-benchmark-20260426

build/depot-speed-benchmark-20260426-warm

hotfix/1.13.3-fix7

feat/evaluation

fix/workflow-line

chore/dependency-upgrade

deploy/zhaohao

feat/replayable-stream

feat/show-the-hierarchy-in-phonenix-trace

p363-reviewed

build/billing-v3

copilot/list-contributions-to-dify

cursor/migrate-tooltip-to-popover-infotips

refactor/quota-service

feat/new-biliing-quota

hotfix/1.13.3-fix6

cursor/dify-ui-infra

p363-hjlarry

cursor/refactor-select-trigger-api

chore/lts-13x-bump-deps

codex/tighten-button-tone-types

locate-queue-autocreate-deps

hotfix/1.13.3-fix5

feat/new-agent-node

hotfix/1.13.3-fix4

feat/per-db-credential

chore/i18n-sync-208604a3a819-9220dd74

chore/i18n-sync-1b369cede4b4-0e13ce3f

chore/i18n-sync-c93e40212e4c-0e13ce3f

codex/fix-vite-audit-in-sdk-test

copilot/fix-agent-dialogue-input-limit

codex/dify-ui-package-migration

4-2-no-global-loading

fix/ps-not-send

3-18-no-global-loading

feat/support-agent-sandbox

hotfix/1.13.3-fix3

hotfix/1.13.3-fix2

4-1-unocss

build/feat/saas-quota-v4

feat/remove-unused-is-deleted-from-conversation

codex-add-podman-compose-dev-scripts

fix-partnerstack-cookie-sync

hotfix/1.13.3-fix1

3-31-vite-task-cache

test/add-test-case-for-prompt-editor

build/feat/saas-quota

build/feat/saas-quota-v2

deploy/agent-dev

yanli/fix-iter-log

review-myscale-sqli

codex/force-node24-for-actions

ci/docker-build-narrowing

chore/dependabot-alert-to-bot

verify-email-reset-flow

3-26-cache-lint-for-autofix

gh-readonly-queue/main/pr-34120-2cbcf9518e40104286a3034f3c3c688cd4ff9fbf

gh-readonly-queue/main/pr-34123-1c72b8d9db03b93b3fc7f86bc522e53806f5a8f0

gh-readonly-queue/main/pr-33960-38285aa1ac6de98614456f49b4d834fe503f4e58

p383

yanli/phase3-code-scope

test/workflow-app

codex/migrate-old-toast-calls-and-update-translations

hotfix/1.13.2-fix2

focal-quokka

codex/fix-issue-33422-in-repository

hotfix/1.13.2-fix1

copilot/refactor-test-config-leak-fix

build/release-1.13.2

fix-kpa-issue

build/release-1.13.1-rc.3

3-18-dev-with-http2

build/release-1.13.1-rc.2

3-16-revert-changes

3-16-add-csp

build/release-1.13.1-rc.1

feat/source-for-plugin-tasks

3-16-next-lib

revert-33484-dependabot/pip/api/python-packages-2eba66ec58

move-trigger-nodes

copilot/refactor-test-config-leak-detection

fix/enterprise-api-error-handling

release/e-1.12.1

fix/vinext-deps

yanli/docx-image-render

copilot/analyze-dify-code

deploy/clean-task-trace

copilot/sub-pr-33044

3-6-type-check

feat/model-provider-refactor

copilot/refactor-unnecessary-cast-call

build/export-app-messages

1.12.1-otel-ee

hotfix/1.13.0-fix.4

update-checker

test/ui-primitive-wrapper-tests-pr

hotfix/1.13.0-fix.3

refactor/base-comp

deploy/memory-usage

hotfix/1.13.0-fix.2

hotfix/1.13.0-fix.1

build/sandbox-clean-job-260302-1

build/sandbox-clean-job

fix/otel-upgrade-e-1.12.1

build/optimize-workflow-run-cleanup

move-core-prompt-runtime

hotfix/1.12.1-fix.6

copilot/remove-pm2-from-docker

move-token-buffer-memory

32589-main-repo

fix/access-mode-sso-verified

refactor/remove-workspace-mutate-from-context

2-11-fix-lint

feat/plugins-marketplace-ssr-prefetch-loading

build/message-clean-performance-log

refactor/template-transform-node

hotfix/1.12.1-fix.5

2-9-stable-test-2

pre-align-hitl-frontend

fix/preserve-UNC-paths-in-conversation-opner

hotfix/1.12.1-fix.4

hotfix/1.12.1-fix.3

feat/add-update-all-plugin-button

refactor/share

hotfix/1.12.1-fix.2

test/inprove-quality

feat/add_templates

hotfix/1.12.1-fix.1

fix/ee-1511-set-default-provider-user-id-bug

copilot/fix-pnpm-test

hotfix/1.12.1-fix.0

feat/vibe-wf

fix/fix-test

fix/console_ns_import

release/1.12.1

fix/workflow-sync-draft

refactor/ssr-prefetch-zustand-removal

1-24-kubb-generate

refactor/migrate-react-window-to-tanstack-virtual

fix/input-ime-onpressenter

1-30-fix-failed-test

feat/structured-output-with-sandbox

yanli/init-ty

hotfix/1.11.4-fix.4

fix/trigger-plugin-output

fix/parallel-generation-render

refactor/configuration

yanli/add-opaque-body

build/billing-refactor-test-2026012701

refactor/debug-and-preview-store

refactor/tools-workflow

build/debug-billing-refactor

build/billing-service

build-billing-service

feat/add-agentation

refactor/app-components

build/collaboration

copilot/sub-pr-31424

refactor/local-storage

refactor/skill-bundler

hotfix/1.11.4-fix.3

build/archive-workflow-run

feat/pull-a-variable

hotfix/1.11.4-fix.2

copilot/sub-pr-30849

hotfix/1.11.4-fix.1

1-21-test-window-is-not-defined

revert-30727-feat/model-total-credits

copilot/sub-pr-31283

zhsama/multi-turn-popup

zhsama/panel-var-popup

12-19-demo-for-app-store

refactor/migrate-app-detail-to-tanstack-query

build/clear-message

feat/credential-sync-fix-ee

feat/llm-first-token-timeout

zhsama/assemble-var-input

release/e-1.11.2

feature/task-quadrant-view

zhsama/llm-warning-ui

build/clear-workflow-run

zhsama/agent-at-nodes

build/1.11.4

release/e-1.6.0-fix.1

release/e-0.15.8-fix.1

1-14-remove-web-app-access-token

refactor/plugins-detail

fix/reset-dev

feat/llm-support-tools

feat/knowledge-summary-index

fix/preact-security-vulnerability

copilot/fix-clear-query-params-test

refactor/query-params-nuqs

chore/upgrade-pnpm-10.28.0

8c92-update-api-core

detached

chore/i18n-sync-20260107-104636

chore/i18n-sync-20260107-102654

feat/grouping-branching

feat/agent-node-v2

hotfix/1.11.2-fix.3

feat/llm-node-support-tools

refactor/remove-axios-dependency

refactor/web-service-hooks

fix/pwa-plugin-migration

chore/refactor-text-generation

hotfix/1.11.2-fix.2

release/e-1.11.1

release/e-1.9.2

release/e-1.8.2

hotfix/1.11.2-hotfix-1

refactor/chat-messages-service-api

fix/knowledge-retrieval-node-affected-by-past-version

fix/esbuild-dependabot-145

chore/automated-i18n-updates-02e0fadef78f0c888b79e7a52ae6714ac73effdc

chore/automated-i18n-updates-eb73f9a9b9fc9eee6be786d2bf5f41fc77e240c4

hotfix/1.11.1-2

refactor-text-generate-item

feat/end-user-oauth

feat/add-qdrant-to-tidb-migration

codex/run-pnpm-lint-fix-and-commit-changes

feat/document-test

feat/e2e-testing

deploy/trigger-dev

hotfix/1.11.1-1

e-260

refactor/use-log-react-query

feat/fallback-interface-for-unauthorized-datasource-node

hotfix/1.10.1-fix.4

refactor/app/components/app/text-generate/item/index.tsx-and-add-test

release/e-1.6.0

hotfix/1.10.1-fix.3

hotfix/1.10.1-fix.2

feat/tracking-1203

deploy/end-user-oauth

hotfix/1.10.1-fix.1

refactor/marketplace-react-query

feat/detect-cognitive-complexity

fix/codeowners

fix/httpx_timeout_parameters

feat/end-user-auth-dummy-apis

chore/re-point-doc-urls

fix/share-markdown-xss

feat/data-tracking

feat/memory-orchestration-be

build/trigger-billing

chore/remove-docker-legacy-dir

copilot/reverse-engineer-dify-application

feat/amplitude

feat/trigger-saas

mysql-adapt

test/build-diff-edition

feat/no-root-image

feat/trigger

feat/ga-tracking

feat/collaboration

mysql-adaptation

feat/sqlalchemy-type-annotations

build/trigger-1

build/self-tenant-queue

mcp-conditional-capability

fix/mcp-capability

hotfix/1.9.2-fix.3

hotfix/1.9.2-fix.2

feat/iteration-node

hotfix/1.9.2-fix.1

hotfix/1.9.1-fix.1

e1ca7a9bdb0443b9f027b6de16

fix/login-status

feat/gtag-1016

test/monaco-editor-and-remix-icon-upgrade

copilot/fix-ce7a9189-f70c-4ea9-81ba-3f49303104d6

feat/memory-orchestration-be-dev-env

build/trigger

feat/add-knowledge-pipeline-template-command

chore/workflow-performance

copilot/fix-fc039c44-aa24-4844-82b2-e9ac237a13e9

test/log-refactor

chore/ssrf-config

feat/pinecone-vdb

copilot/fix-d8c5989d-5a30-418f-8dc4-099cf1f37218

deploy/rag-dev

hotfix/1.9.0-fix.2

pinecone

fix/document-query

feat/trigger_backup

feat/playwright-integration

feat/trigger_merging

feat/chunk-deduplication

feat/crendential-policy-default-check

feat/credential-policy

release/e-1.8.1

fix/template-list

feat/end_user

feat/trigger-fe

revert-25628-refactor-24421-app-datasets-part1

fix/plugin-tag-fallback

fix/unselect-credential

feat/limit-conv-var-desc-length

feat/rag-pipeline-service-api

fix/empty-plugin-list

feat/plugin-readme

feat/plugin-readme-fe

feat/container-node-extract-mapping

bug1

fix/model-credential

feat/big-var-value-show-fe

build/1.7.2-fix.2

release/e-1.7.2

build/boolean-type

feat/oauth-provider-fe

build/0.7.2-fix.1

feat/model-credentials

feat/model-auth

feat/rag-2-preview

release/e-1.7.1

fix/hotfix-tool-provider-deadlock

feat/knowledge-pipeline-access-control

config-tool-file-size

13604-when-using-redis-cluster-for-caching-add-global_prefix-to-all-keys-cached-by-redis

feat/model-credentils

build/oauth

feat/oauth

feat/human-input

build/plugin-auto-upgrade

test/performance

feat/tool-plugin-oauth

feat/tool-oauth

temp-feat-owner-transfer-enterprise-frontend

release/e-3.0.2

feat/plugin-auto-upgrade-fe

chore/offline-the-sys-files

feat/rag-pipeline

feat/r2

release/e-3.2.0

wtw/rag-pipeline

feat/add-retrival-field-in-dataset

feat/webapp-verified-sso-main

fix/app-not-published-error

feat/webapp-verified-sso-260

v141-hotfix

fix/20326-tool-invoke-error-instance-account

fix/19933-account-object-has-no-attribute-_current_tenant-when-workflow-uses-workflow-as-tool-node

hotfix/0519

fix/e-legacy-clean-up

fix/admin-permission

fix/e-admin-permission

feat/model-memory

feat/webapp-auth-api

1.0.0-fix

revert-17133-fix/i16990-text-to-language-settings

e-0156

hotfix/translation-fix

fix/slider-style-error

e-0154

release/0.15.6-alpha-1

cohere/cleanup-free-tenants-logs

chore/auto-dify

fix/rag-infinity-spaces-loop

fix/dataset-admin

fix/expose-debugging-port

fix/tool-info

fix/aws-s3-r2-compatible

feat/knowledge-metabase

fix/fail-branch-stream-output-error

release/0.15.3-fix1

feat/14009-feature-request-support-for-retrieving-historical-conversations-without-from-enduser-id

feat/upgrade-unstructured-version-10.2

feat/classnames-sort

feat/upgrade-unstructured-version

fix/version-check

fix/handle-agent-none-value

fix/agent-params-pasring

fix/agent-parallel

feat/knowledge-dark-mode

feat/custom-tool-input

release/0.15.2-fix1

0.15.1-admin-apis

feat/support-docx-image-view

feat/agent-stream-output

feat/workflow-node-dark-mode

fix/switch-strategy-clean-param

fix/chore-fix

opik-monitoring

provider-gpustack

feat/mecab-japanese-keywords

feat/retry-single-step-debug

revert-12086-feat/parent-child-retrieval

fix/remove-the-retry-index-field

fix/11839

feat/node-execution-retry

feat/support-extractor-tools-update-wip

feat/update-tidb-batchget-endpoint

fix/iteration-thread-pool-error

feat/support-multi-token-count

feat/parent-child-retrieval-api

fix/app-icon-is-missing

feat/support-extractor-tools-update

test/disable_site

build/add-dependabot

feat/support-extractor-tools

fix/docx-extract-image-ssrf

fix/redis-slow-in-gevent

fix/9772-internal-server-error-when-custom-disclaimer-longer-than-64-characters

alert-autofix-89

build/eslint-react-refresh-plugin

build/switch-to-pnpm

revert-9424-feat/update-dataset-clean-rule

fix/external-knowledge-retrieval-issues

feat/login-type-coontrol

feat/external-knowledge-api

feat/rag-external-knowledge-with-api

feat/external-knowledge

fix/notion-table-extract

fix/tooltip

feat/workflow-add-block-shortcut

feat/update-docs

fix/note-node-zoom-issue

fix/model-runtime-quato-issue

fix/db-lock-timeout

feat/new-tooltip

feat/web-app-sso

chore/optimize-app-workflow-deletion-slow-sql

fix/trace_app_config_app_id_idx

fix/extra-table-tracing-app-config

feat/update-beat-job-time-to-env

fix/index-estimate-error

chore/enterprise-license-status

fix/remove-tsne_position

feat/2p

feat/aws-iam-auth-check

feat/add-flashrank

feat/support-milvus-2.4

feat/add-resource-from-tools

bai

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify#21191