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

api always 500 #21006

New Issue
Closed
opened 2026-02-21 20:10:13 -05:00 by yindo · 8 comments
yindo commented 2026-02-21 20:10:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @lixc123 on GitHub (Dec 12, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I always get this error no matter what I request:
2025-12-12 07:19:13.413 ERROR [Thread-575 (_generate_conversation_name_worker)] [base.py:211] - Error in stream reponse for plugin {'code': -500, 'message': '{"message":"{\"args\":{\"description\":\"[models] Connection Error, Connection error.\"},\"error_type\":\"InvokeConnectionError\",\"message\":\"[models] Connection Error, Connection error.\"}","error_type":"PluginInvokeError","args":null}', 'data': None}

2025-12-12 07:20:44.522 ERROR [Thread-581 (_generate_conversation_name_worker)] [base.py:211] - Error in stream reponse for plugin {'code': -500, 'message': '{"message":"{\"args\":{\"description\":\"[models] Connection Error, Connection error.\"},\"error_type\":\"InvokeConnectionError\",\"message\":\"[models] Connection Error, Connection error.\"}","error_type":"PluginInvokeError","args":null}', 'data': None}

2025-12-12 07:20:58.819 ERROR [Thread-585 (_generate_conversation_name_worker)] [base.py:211] - Error in stream reponse for plugin {'code': -500, 'message': '{"message":"{\"args\":{\"description\":\"[models] Connection Error, Connection error.\"},\"error_type\":\"InvokeConnectionError\",\"message\":\"[models] Connection Error, Connection error.\"}","error_type":"PluginInvokeError","args":null}', 'data': None}

Error in docker-api-1

✔️ Expected Behavior

No error reported

❌ Actual Behavior

No response

Originally created by @lixc123 on GitHub (Dec 12, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I always get this error no matter what I request: 2025-12-12 07:19:13.413 ERROR [Thread-575 (_generate_conversation_name_worker)] [base.py:211] - Error in stream reponse for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{\\"description\\":\\"[models] Connection Error, Connection error.\\"},\\"error_type\\":\\"InvokeConnectionError\\",\\"message\\":\\"[models] Connection Error, Connection error.\\"}","error_type":"PluginInvokeError","args":null}', 'data': None} 2025-12-12 07:20:44.522 ERROR [Thread-581 (_generate_conversation_name_worker)] [base.py:211] - Error in stream reponse for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{\\"description\\":\\"[models] Connection Error, Connection error.\\"},\\"error_type\\":\\"InvokeConnectionError\\",\\"message\\":\\"[models] Connection Error, Connection error.\\"}","error_type":"PluginInvokeError","args":null}', 'data': None} 2025-12-12 07:20:58.819 ERROR [Thread-585 (_generate_conversation_name_worker)] [base.py:211] - Error in stream reponse for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{\\"description\\":\\"[models] Connection Error, Connection error.\\"},\\"error_type\\":\\"InvokeConnectionError\\",\\"message\\":\\"[models] Connection Error, Connection error.\\"}","error_type":"PluginInvokeError","args":null}', 'data': None} Error in docker-api-1 ### ✔️ Expected Behavior No error reported ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 20:10:13 -05:00
yindo closed this issue 2026-02-21 20:10:14 -05:00
yindo commented 2026-02-21 20:10:14 -05:00
Author
Owner
Copy Link
Copy Source

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

Your error means the Dify API can't connect to the model/plugin backend, usually due to a Docker network or config problem. Here’s a focused checklist to help you debug:

  1. Check all containers: Run docker ps and make sure api, plugin_daemon, your model/vector DB (like weaviate), redis, and database containers are running and healthy. If any are missing or unhealthy, check their logs for errors.
  2. Environment variables: In your .env and docker-compose.yaml, confirm all critical variables are set and match the Docker service names, not localhost or 127.0.0.1. For example, PLUGIN_DAEMON_URL should be http://plugin_daemon:5002, and WEAVIATE_ENDPOINT should be http://weaviate:8080 if you use Weaviate.
  3. API keys and model access: If using OpenAI or another provider, make sure your API key is valid and has access to at least one supported model. If not, Dify will fail to connect and throw 500 errors during provider setup (source).
  4. Network connectivity: Test from inside the api container: 
    docker exec -it <api_container> curl http://plugin_daemon:5002/health
docker exec -it <api_container> curl http://weaviate:8080/v1/
    If these fail, it's a Docker network or service config issue (source).
  5. Logs and debug mode: Set LOG_LEVEL=DEBUG and ENABLE_REQUEST_LOGGING=True in your .env, then restart containers. Check logs from api, plugin_daemon, and worker for more details (source).
  6. Frontend URL validation: If you use the web UI, make sure the API base URL is your LAN IP or host.docker.internal, not localhost or a private IP (source).
  7. Upgrades/migrations: If you recently upgraded or restored from backup, run the official migration commands to restore plugin/model data (source).
  8. Corporate proxy/SSL: If you’re behind a proxy that intercepts HTTPS, the Go-based plugin_daemon may not trust your custom CA even if installed in the container (source).

If you still get 500 errors, please share:

  • Output of docker ps
  • Results of the curl tests above
  • Any relevant error logs from api, plugin_daemon, or model/vector DB containers

This will help pinpoint where the connection is breaking.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 12, 2025): <!-- Answer --> Your error means the Dify API can't connect to the model/plugin backend, usually due to a Docker network or config problem. Here’s a focused checklist to help you debug: 1. **Check all containers**: Run `docker ps` and make sure `api`, `plugin_daemon`, your model/vector DB (like `weaviate`), `redis`, and database containers are running and healthy. If any are missing or unhealthy, check their logs for errors. 2. **Environment variables**: In your `.env` and `docker-compose.yaml`, confirm all critical variables are set and match the Docker service names, not `localhost` or `127.0.0.1`. For example, `PLUGIN_DAEMON_URL` should be `http://plugin_daemon:5002`, and `WEAVIATE_ENDPOINT` should be `http://weaviate:8080` if you use Weaviate. 3. **API keys and model access**: If using OpenAI or another provider, make sure your API key is valid and has access to at least one supported model. If not, Dify will fail to connect and throw 500 errors during provider setup ([source](https://github.com/langgenius/dify/issues/28235)). 4. **Network connectivity**: Test from inside the `api` container: ```bash docker exec -it <api_container> curl http://plugin_daemon:5002/health docker exec -it <api_container> curl http://weaviate:8080/v1/ ``` If these fail, it's a Docker network or service config issue ([source](https://github.com/langgenius/dify/issues/27825)). 5. **Logs and debug mode**: Set `LOG_LEVEL=DEBUG` and `ENABLE_REQUEST_LOGGING=True` in your `.env`, then restart containers. Check logs from `api`, `plugin_daemon`, and `worker` for more details ([source](https://github.com/langgenius/dify/issues/25491)). 6. **Frontend URL validation**: If you use the web UI, make sure the API base URL is your LAN IP or `host.docker.internal`, not `localhost` or a private IP ([source](https://github.com/langgenius/dify-docs/issues/543)). 7. **Upgrades/migrations**: If you recently upgraded or restored from backup, run the official migration commands to restore plugin/model data ([source](https://github.com/langgenius/dify/issues/21363)). 8. **Corporate proxy/SSL**: If you’re behind a proxy that intercepts HTTPS, the Go-based `plugin_daemon` may not trust your custom CA even if installed in the container ([source](https://github.com/langgenius/dify/issues/20722)). If you still get 500 errors, please share: - Output of `docker ps` - Results of the `curl` tests above - Any relevant error logs from `api`, `plugin_daemon`, or model/vector DB containers This will help pinpoint where the connection is breaking. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/0bdaa2b1-2ff3-4125-8c12-4db43c6ea9aa?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0bdaa2b1-2ff3-4125-8c12-4db43c6ea9aa?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0bdaa2b1-2ff3-4125-8c12-4db43c6ea9aa?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0bdaa2b1-2ff3-4125-8c12-4db43c6ea9aa?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0bdaa2b1-2ff3-4125-8c12-4db43c6ea9aa?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0bdaa2b1-2ff3-4125-8c12-4db43c6ea9aa?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0bdaa2b1-2ff3-4125-8c12-4db43c6ea9aa?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Your%20error%20means%20the%20Dify%20API%20can%27t%20connect%20to%20the%20model/plugin%20backend%2C%20usually%20due%20to%20a%20Docker%20network%20or%20config%20problem.%20Here%E2%80%99s%20a%20focused%20checklist%20to%20help%20you%20debug%3A%0A%0A1.%20%2A%2ACheck%20all%20containers%2A%2A%3A%20Run%20%60docker%20ps%60%20and%20make%20sure%20%60api%60%2C%20%60plugin_daemon%60%2C%20your%20model/vector%20DB%20%28like%20%60weaviate%60%29%2C%20%60redis%60%2C%20and%20database%20containers%20are%20running%20and%20healthy.%20If%20any%20are%20missing%20or%20unhealthy%2C%20check%20their%20logs%20for%20errors.%20%20%0A2.%20%2A%2AEnvironment%20variables%2A%2A%3A%20In%20your%20%60.env%60%20and%20%60docker-compose.yaml%60%2C%20confirm%20all%20critical%20variables%20are%20set%20and%20match%20the%20Docker%20service%20names%2C%20not%20%60localhost%60%20or%20%60127.0.0.1%60.%20For%20example%2C%20%60PLUGIN_DAEMON_URL%60%20should%20be%20%60http%3A//plugin_daemon%3A5002%60%2C%20and%20%60WEAVIATE_ENDPOINT%60%20should%20be%20%60http%3A//weaviate%3A8080%60%20if%20you%20use%20Weaviate.%20%20%0A3.%20%2A%2AAPI%20keys%20and%20model%20access%2A%2A%3A%20If%20using%20OpenAI%20or%20another%20provider%2C%20make%20sure%20your%20API%20key%20is%20valid%20and%20has%20access%20to%20at%20least%20one%20supported%20model.%20If%20not%2C%20Dify%20will%20fail%20to%20connect%20and%20throw%20500%20errors%20during%20provider%20setup%C2%A0%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/28235%29%29.%20%20%0A4.%20%2A%2ANetwork%20connectivity%2A%2A%3A%20Test%20from%20inside%20the%20%60api%60%20container%3A%0A%20%20%20%60%60%60bash%0A%20%20%20docker%20exec%20-it%20%3Capi_container%3E%20curl%20http%3A//plugin_daemon%3A5002/health%0A%20%20%20docker%20exec%20-it%20%3Capi_container%3E%20curl%20http%3A//weaviate%3A8080/v1/%0A%20%20%20%60%60%60%0A%20%20%20If%20these%20fail%2C%20it%27s%20a%20Docker%20network%20or%20service%20config%20issue%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/27825%29%29.%20%20%0A5.%20%2A%2ALogs%20and%20debug%20mode%2A%2A%3A%20Set%20%60LOG_LEVEL%3DDEBUG%60%20and%20%60ENABLE_REQUEST_LOGGING%3DTrue%60%20in%20your%20%60.env%60%2C%20then%20restart%20containers.%20Check%20logs%20from%20%60api%60%2C%20%60plugin_daemon%60%2C%20and%20%60worker%60%20for%20more%20details%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/25491%29%29.%20%20%0A6.%20%2A%2AFrontend%20URL%20validation%2A%2A%3A%20If%20you%20use%20the%20web%20UI%2C%20make%20sure%20the%20API%20base%20URL%20is%20your%20LAN%20IP%20or%20%60host.docker.internal%60%2C%20not%20%60localhost%60%20or%20a%20private%20IP%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify-docs/issues/543%29%29.%20%20%0A7.%20%2A%2AUpgrades/migrations%2A%2A%3A%20If%20you%20recently%20upgraded%20or%20restored%20from%20backup%2C%20run%20the%20official%20migration%20commands%20to%20restore%20plugin/model%20data%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/21363%29%29.%20%20%0A8.%20%2A%2ACorporate%20proxy/SSL%2A%2A%3A%20If%20you%E2%80%99re%20behind%20a%20proxy%20that%20intercepts%20HTTPS%2C%20the%20Go-based%20%60plugin_daemon%60%20may%20not%20trust%20your%20custom%20CA%20even%20if%20installed%20in%20the%20container%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/20722%29%29.%0A%0AIf%20you%20still%20get%20500%20errors%2C%20please%20share%3A%0A-%20Output%20of%20%60docker%20ps%60%0A-%20Results%20of%20the%20%60curl%60%20tests%20above%0A-%20Any%20relevant%20error%20logs%20from%20%60api%60%2C%20%60plugin_daemon%60%2C%20or%20model/vector%20DB%20containers%0A%0AThis%20will%20help%20pinpoint%20where%20the%20connection%20is%20breaking.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/29574)
yindo commented 2026-02-21 20:10:14 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 12, 2025):

Please provide more information if possible.

@crazywoola commented on GitHub (Dec 12, 2025): Please provide more information if possible.
yindo commented 2026-02-21 20:10:14 -05:00
Author
Owner
Copy Link
Copy Source

@lixc123 commented on GitHub (Dec 12, 2025):

2025-12-12 12:38:49.403 INFO [GraphWorker-0] [_client.py:1038]  - HTTP Request: GET [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256) "HTTP/1.1 200 OK"

2025-12-12 12:38:49.608 INFO [GraphWorker-0] [_client.py:1038]  - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/model/schema⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/model/schema) "HTTP/1.1 200 OK"

2025-12-12 12:38:51.116 INFO [GraphWorker-0] [_client.py:1038]  - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke) "HTTP/1.1 200 OK"

2025-12-12 12:38:51.620 INFO [Dummy-35] [_client.py:1038]  - HTTP Request: GET [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256) "HTTP/1.1 200 OK"

2025-12-12 12:38:51.630 INFO [Dummy-72] [_client.py:1038]  - HTTP Request: GET [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256) "HTTP/1.1 200 OK"

2025-12-12 12:38:52.330 INFO [Dummy-72] [_client.py:1038]  - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke) "HTTP/1.1 200 OK"

2025-12-12 12:38:52.331 ERROR [Dummy-72] [base.py:277]  - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{\\"description\\":\\"[models] Connection Error, Connection error.\\"},\\"error_type\\":\\"InvokeConnectionError\\",\\"message\\":\\"[models] Connection Error, Connection error.\\"}","error_type":"PluginInvokeError","args":null}', 'data': None}

2025-12-12 12:38:52.338 INFO [Dummy-35] [_client.py:1038]  - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke) "HTTP/1.1 200 OK"

2025-12-12 12:38:52.339 ERROR [Dummy-35] [base.py:277]  - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{\\"description\\":\\"[models] Connection Error, Connection error.\\"},\\"error_type\\":\\"InvokeConnectionError\\",\\"message\\":\\"[models] Connection Error, Connection error.\\"}","error_type":"PluginInvokeError","args":null}', 'data': None}

I cleared the logs, and when I sent a conversation request, the logs displayed in the API were as shown above,

@lixc123 commented on GitHub (Dec 12, 2025): ``` 2025-12-12 12:38:49.403 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256) "HTTP/1.1 200 OK" 2025-12-12 12:38:49.608 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/model/schema⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/model/schema) "HTTP/1.1 200 OK" 2025-12-12 12:38:51.116 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke) "HTTP/1.1 200 OK" 2025-12-12 12:38:51.620 INFO [Dummy-35] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256) "HTTP/1.1 200 OK" 2025-12-12 12:38:51.630 INFO [Dummy-72] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256) "HTTP/1.1 200 OK" 2025-12-12 12:38:52.330 INFO [Dummy-72] [_client.py:1038] - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke) "HTTP/1.1 200 OK" 2025-12-12 12:38:52.331 ERROR [Dummy-72] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{\\"description\\":\\"[models] Connection Error, Connection error.\\"},\\"error_type\\":\\"InvokeConnectionError\\",\\"message\\":\\"[models] Connection Error, Connection error.\\"}","error_type":"PluginInvokeError","args":null}', 'data': None} 2025-12-12 12:38:52.338 INFO [Dummy-35] [_client.py:1038] - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke) "HTTP/1.1 200 OK" 2025-12-12 12:38:52.339 ERROR [Dummy-35] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{\\"description\\":\\"[models] Connection Error, Connection error.\\"},\\"error_type\\":\\"InvokeConnectionError\\",\\"message\\":\\"[models] Connection Error, Connection error.\\"}","error_type":"PluginInvokeError","args":null}', 'data': None} ``` I cleared the logs, and when I sent a conversation request, the logs displayed in the API were as shown above,
yindo commented 2026-02-21 20:10:14 -05:00
Author
Owner
Copy Link
Copy Source

@lixc123 commented on GitHub (Dec 12, 2025):

I updated to version 1.11.1 and it's the same @crazywoola

@lixc123 commented on GitHub (Dec 12, 2025): I updated to version 1.11.1 and it's the same @crazywoola
yindo commented 2026-02-21 20:10:14 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 12, 2025):

From the provided information I haven't see any useful clues to investigate. Please provide more details for example:

  • the name of the plugin
  • the version of the plugin
  • the version of the plugin_daemon
    BTW

If you’re experiencing issues with plugins, please report them using this template: https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml.

@crazywoola commented on GitHub (Dec 12, 2025): From the provided information I haven't see any useful clues to investigate. Please provide more details for example: - the name of the plugin - the version of the plugin - the version of the plugin_daemon BTW If you’re experiencing issues with plugins, please report them using this template: [https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml](https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml).
yindo commented 2026-02-21 20:10:14 -05:00
Author
Owner
Copy Link
Copy Source

@lixc123 commented on GitHub (Dec 12, 2025):

Image

2025-12-12 15:08:57.654 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠ "HTTP/1.1 200 OK"

2025-12-12 15:08:57.765 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/model/schema⁠ "HTTP/1.1 200 OK"

2025-12-12 15:08:59.102 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠ "HTTP/1.1 200 OK"

2025-12-12 15:08:59.870 INFO [Dummy-42] [_client.py:1038] - HTTP Request: GET http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠ "HTTP/1.1 200 OK"

2025-12-12 15:09:00.667 INFO [Dummy-42] [_client.py:1038] - HTTP Request: POST http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠ "HTTP/1.1 200 OK"

2025-12-12 15:09:00.668 ERROR [Dummy-42] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\"args\":{\"description\":\"[models] Connection Error, Connection error.\"},\"error_type\":\"InvokeConnectionError\",\"message\":\"[models] Connection Error, Connection error.\"}","error_type":"PluginInvokeError","args":null}', 'data': None}
When I use a webapp to access independently in a browser, no matter which workflow or plugin, there will always be a 500 error

@lixc123 commented on GitHub (Dec 12, 2025): <img width="443" height="327" alt="Image" src="https://github.com/user-attachments/assets/c190b56c-d713-49b1-bc0b-9c8930e16205" /> <!-- Failed to upload "image.png" --> 2025-12-12 15:08:57.654 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256) "HTTP/1.1 200 OK" 2025-12-12 15:08:57.765 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/model/schema⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/model/schema) "HTTP/1.1 200 OK" 2025-12-12 15:08:59.102 INFO [GraphWorker-0] [_client.py:1038] - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke) "HTTP/1.1 200 OK" 2025-12-12 15:08:59.870 INFO [Dummy-42] [_client.py:1038] - HTTP Request: GET [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/management/models?page=1&page_size=256) "HTTP/1.1 200 OK" 2025-12-12 15:09:00.667 INFO [Dummy-42] [_client.py:1038] - HTTP Request: POST [http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke⁠](http://plugin_daemon:5002/plugin/8ba9c9cc-51bf-434d-bb7e-7fa9ddd024fb/dispatch/llm/invoke) "HTTP/1.1 200 OK" 2025-12-12 15:09:00.668 ERROR [Dummy-42] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"args\\":{\\"description\\":\\"[models] Connection Error, Connection error.\\"},\\"error_type\\":\\"InvokeConnectionError\\",\\"message\\":\\"[models] Connection Error, Connection error.\\"}","error_type":"PluginInvokeError","args":null}', 'data': None} When I use a webapp to access independently in a browser, no matter which workflow or plugin, there will always be a 500 error
yindo commented 2026-02-21 20:10:14 -05:00
Author
Owner
Copy Link
Copy Source

@lixc123 commented on GitHub (Dec 12, 2025):

Image

this page

@lixc123 commented on GitHub (Dec 12, 2025): <img width="2260" height="1266" alt="Image" src="https://github.com/user-attachments/assets/c658c432-b57a-42d0-b792-83307ffa4f3a" /> this page
yindo commented 2026-02-21 20:10:14 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @lixc123. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported persistent 500 errors with "PluginInvokeError" when using the self-hosted Dify API (v1.9.2 and v1.11.1).
  • Logs indicate successful HTTP requests to the plugin daemon but subsequent connection failures during streaming responses.
  • A detailed troubleshooting checklist was provided covering Docker health, environment variables, API keys, network, and proxy settings.
  • You have shared logs and screenshots, but the root cause has not yet been identified.
  • I have requested additional plugin and environment details to continue investigation.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify by commenting here.
  • If no further updates are provided, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 14, 2026): Hi, @lixc123. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported persistent 500 errors with "PluginInvokeError" when using the self-hosted Dify API (v1.9.2 and v1.11.1). - Logs indicate successful HTTP requests to the plugin daemon but subsequent connection failures during streaming responses. - A detailed troubleshooting checklist was provided covering Docker health, environment variables, API keys, network, and proxy settings. - You have shared logs and screenshots, but the root cause has not yet been identified. - I have requested additional plugin and environment details to continue investigation. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of Dify by commenting here. - If no further updates are provided, I will automatically close this issue in 15 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug 🤔 cant-reproduce
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21006
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?