langgenius/dify-plugin-daemon
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-daemon.git synced 2026-07-21 17:25:23 -04:00
Code Issues 111 Packages Projects Releases 10 Wiki Activity

I encountered a plugin issue when visiting the homepage #242

New Issue
Open
opened 2026-02-16 01:15:05 -05:00 by yindo · 8 comments
yindo commented 2026-02-16 01:15:05 -05:00
Owner
Copy Link
Copy Source

Originally created by @AlanChan1993 on GitHub (Feb 4, 2026).

Dear ,I encountered a plugin issue when visiting the homepage:

1.[ERROR]failed to get plugin identity, check if your declaration is invalid: plugin_unique_identifier is not valid: :@
Versions
My Dify version is '1.11.4'
dify-api: 1.11.4
aify-plugin-daemon 0.5.2-local

2.plugin_daemon-1 | 2026/02/05 00:52:25 client.go:39: [PANIC]Failed to ping serverless connector%!(EXTRA *json.SyntaxError=invalid character '<' looking for beginning of value)
plugin_daemon-1 | panic: [PANIC]Failed to ping serverless connector%!(EXTRA *json.SyntaxError=invalid character '<' looking for beginning of value)
Versions
My Dify version is '1.11.4'
dify-api: 1.11.4
aify-plugin-daemon 0.5.2-serverless

Best Regards

Originally created by @AlanChan1993 on GitHub (Feb 4, 2026). Dear ,I encountered a plugin issue when visiting the homepage: 1.[ERROR]failed to get plugin identity, check if your declaration is invalid: plugin_unique_identifier is not valid: :@ **Versions** My Dify version is '1.11.4' dify-api: 1.11.4 aify-plugin-daemon 0.5.2-local 2.plugin_daemon-1 | 2026/02/05 00:52:25 client.go:39: [PANIC]Failed to ping serverless connector%!(EXTRA *json.SyntaxError=invalid character '<' looking for beginning of value) plugin_daemon-1 | panic: [PANIC]Failed to ping serverless connector%!(EXTRA *json.SyntaxError=invalid character '<' looking for beginning of value) **Versions** My Dify version is '1.11.4' dify-api: 1.11.4 aify-plugin-daemon 0.5.2-serverless Best Regards
yindo added the plugin-daemonbug labels 2026-02-16 01:15:05 -05:00
yindo commented 2026-02-16 01:15:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 4, 2026):

Hi @AlanChan1993! I'm Dosu and I’m helping the dify-plugin-daemon team.

Here’s what’s causing your issues and how to fix them:

1. Plugin identity error (plugin_unique_identifier is not valid: :@):
This means your plugin declaration is missing required fields or is incorrectly formatted. The identifier must follow the pattern: author/plugin_id:version@checksum (all lowercase, with specific length and character constraints) see code validation.
Common causes:

  • Missing or invalid fields in manifest.yaml or provider yaml files (especially the author field).
  • Corrupted plugin data in the database or plugin storage directories.
  • On Windows, using backslashes in paths or unsupported characters like : in filenames.

How to fix:

  • Check your plugin’s manifest.yaml and provider yaml files. Make sure all required fields are present and correctly formatted.
  • Clear invalid plugin entries from your database tables (plugin_installations, plugin_declarations, ai_model_installations, plugins) and remove plugin files from storage directories (/app/storage/cwd/plugins/plugin, plugin-working, persistence, plugin-root) step-by-step guide.
  • Update the author field to match your GitHub ID, repackage and reinstall the plugin, then restart the plugin daemon.
  • If you’re on Windows, use forward slashes in paths and avoid : in filenames Windows-specific advice.

2. Serverless connector ping failure (invalid character '<' looking for beginning of value):
This error means the serverless connector endpoint is returning HTML (like an error page) instead of the expected JSON response.
Common causes:

  • The DIFY_PLUGIN_SERVERLESS_CONNECTOR_URL environment variable is set incorrectly, or the service isn’t running.
  • Network misconfiguration (Docker network, firewall, or endpoint unreachable).

How to fix:

  • Double-check the DIFY_PLUGIN_SERVERLESS_CONNECTOR_URL value. Make sure the serverless connector service is running and accessible.
  • The /ping endpoint must respond with the string pong to a POST request ping logic.
  • If you’re running in Docker, don’t use localhost or 127.0.0.1 for service endpoints—use host.docker.internal or your host’s internal IP network troubleshooting.
  • Make sure the connector service is not returning an error page (HTML) due to a bad URL, missing service, or authentication failure.

If you still see errors after these checks, please share your actual plugin manifest.yaml or the full error logs for more targeted help.

To reply, just mention @dosu.

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

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 4, 2026): <!-- Greeting --> Hi @AlanChan1993! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-plugin-daemon team. <!-- Answer --> Here’s what’s causing your issues and how to fix them: **1. Plugin identity error (`plugin_unique_identifier is not valid: :@`):** This means your plugin declaration is missing required fields or is incorrectly formatted. The identifier must follow the pattern: `author/plugin_id:version@checksum` (all lowercase, with specific length and character constraints) [see code validation](https://github.com/langgenius/dify-plugin-daemon/blob/f272e6c3fcd8a18c6ff571d7fcbfde857f63ef99/pkg/entities/plugin_entities/identity.go#L17-L96). Common causes: - Missing or invalid fields in `manifest.yaml` or provider yaml files (especially the `author` field). - Corrupted plugin data in the database or plugin storage directories. - On Windows, using backslashes in paths or unsupported characters like `:` in filenames. **How to fix:** - Check your plugin’s `manifest.yaml` and provider yaml files. Make sure all required fields are present and correctly formatted. - Clear invalid plugin entries from your database tables (`plugin_installations`, `plugin_declarations`, `ai_model_installations`, `plugins`) and remove plugin files from storage directories (`/app/storage/cwd/plugins/plugin`, `plugin-working`, `persistence`, `plugin-root`) [step-by-step guide](https://github.com/langgenius/dify-plugin-daemon/issues/112#issuecomment-2731612627). - Update the `author` field to match your GitHub ID, repackage and reinstall the plugin, then restart the plugin daemon. - If you’re on Windows, use forward slashes in paths and avoid `:` in filenames [Windows-specific advice](https://github.com/langgenius/dify-plugin-daemon/issues/133#issuecomment-2753960103). **2. Serverless connector ping failure (`invalid character '<' looking for beginning of value`):** This error means the serverless connector endpoint is returning HTML (like an error page) instead of the expected JSON response. Common causes: - The `DIFY_PLUGIN_SERVERLESS_CONNECTOR_URL` environment variable is set incorrectly, or the service isn’t running. - Network misconfiguration (Docker network, firewall, or endpoint unreachable). **How to fix:** - Double-check the `DIFY_PLUGIN_SERVERLESS_CONNECTOR_URL` value. Make sure the serverless connector service is running and accessible. - The `/ping` endpoint must respond with the string `pong` to a POST request [ping logic](https://github.com/langgenius/dify-plugin-daemon/blob/f272e6c3fcd8a18c6ff571d7fcbfde857f63ef99/internal/core/serverless_connector/connector.go#L27-L232). - If you’re running in Docker, don’t use `localhost` or `127.0.0.1` for service endpoints—use `host.docker.internal` or your host’s internal IP [network troubleshooting](https://github.com/langgenius/dify-plugin-daemon/issues/436). - Make sure the connector service is not returning an error page (HTML) due to a bad URL, missing service, or authentication failure. If you still see errors after these checks, please share your actual plugin `manifest.yaml` or the full error logs for more targeted help. <!-- 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/80de6e8a-95a5-4280-95b6-b8fd3e6c0b6c?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/80de6e8a-95a5-4280-95b6-b8fd3e6c0b6c?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/80de6e8a-95a5-4280-95b6-b8fd3e6c0b6c?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/80de6e8a-95a5-4280-95b6-b8fd3e6c0b6c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/80de6e8a-95a5-4280-95b6-b8fd3e6c0b6c?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/80de6e8a-95a5-4280-95b6-b8fd3e6c0b6c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/80de6e8a-95a5-4280-95b6-b8fd3e6c0b6c?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Here%E2%80%99s%20what%E2%80%99s%20causing%20your%20issues%20and%20how%20to%20fix%20them%3A%0A%0A%2A%2A1.%20Plugin%20identity%20error%20%28%60plugin_unique_identifier%20is%20not%20valid%3A%20%3A%40%60%29%3A%2A%2A%20%20%0AThis%20means%20your%20plugin%20declaration%20is%20missing%20required%20fields%20or%20is%20incorrectly%20formatted.%20The%20identifier%20must%20follow%20the%20pattern%3A%20%60author/plugin_id%3Aversion%40checksum%60%20%28all%20lowercase%2C%20with%20specific%20length%20and%20character%20constraints%29%20%5Bsee%20code%20validation%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/blob/f272e6c3fcd8a18c6ff571d7fcbfde857f63ef99/pkg/entities/plugin_entities/identity.go%23L17-L96%29.%20%20%0ACommon%20causes%3A%20%20%0A-%20Missing%20or%20invalid%20fields%20in%20%60manifest.yaml%60%20or%20provider%20yaml%20files%20%28especially%20the%20%60author%60%20field%29.%0A-%20Corrupted%20plugin%20data%20in%20the%20database%20or%20plugin%20storage%20directories.%0A-%20On%20Windows%2C%20using%20backslashes%20in%20paths%20or%20unsupported%20characters%20like%20%60%3A%60%20in%20filenames.%0A%0A%2A%2AHow%20to%20fix%3A%2A%2A%20%20%0A-%20Check%20your%20plugin%E2%80%99s%20%60manifest.yaml%60%20and%20provider%20yaml%20files.%20Make%20sure%20all%20required%20fields%20are%20present%20and%20correctly%20formatted.%0A-%20Clear%20invalid%20plugin%20entries%20from%20your%20database%20tables%20%28%60plugin_installations%60%2C%20%60plugin_declarations%60%2C%20%60ai_model_installations%60%2C%20%60plugins%60%29%20and%20remove%20plugin%20files%20from%20storage%20directories%20%28%60/app/storage/cwd/plugins/plugin%60%2C%20%60plugin-working%60%2C%20%60persistence%60%2C%20%60plugin-root%60%29%20%5Bstep-by-step%20guide%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/112%23issuecomment-2731612627%29.%0A-%20Update%20the%20%60author%60%20field%20to%20match%20your%20GitHub%20ID%2C%20repackage%20and%20reinstall%20the%20plugin%2C%20then%20restart%20the%20plugin%20daemon.%0A-%20If%20you%E2%80%99re%20on%20Windows%2C%20use%20forward%20slashes%20in%20paths%20and%20avoid%20%60%3A%60%20in%20filenames%20%5BWindows-specific%20advice%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/133%23issuecomment-2753960103%29.%0A%0A%2A%2A2.%20Serverless%20connector%20ping%20failure%20%28%60invalid%20character%20%27%3C%27%20looking%20for%20beginning%20of%20value%60%29%3A%2A%2A%20%20%0AThis%20error%20means%20the%20serverless%20connector%20endpoint%20is%20returning%20HTML%20%28like%20an%20error%20page%29%20instead%20of%20the%20expected%20JSON%20response.%20%20%0ACommon%20causes%3A%20%20%0A-%20The%20%60DIFY_PLUGIN_SERVERLESS_CONNECTOR_URL%60%20environment%20variable%20is%20set%20incorrectly%2C%20or%20the%20service%20isn%E2%80%99t%20running.%0A-%20Network%20misconfiguration%20%28Docker%20network%2C%20firewall%2C%20or%20endpoint%20unreachable%29.%0A%0A%2A%2AHow%20to%20fix%3A%2A%2A%20%20%0A-%20Double-check%20the%20%60DIFY_PLUGIN_SERVERLESS_CONNECTOR_URL%60%20value.%20Make%20sure%20the%20serverless%20connector%20service%20is%20running%20and%20accessible.%0A-%20The%20%60/ping%60%20endpoint%20must%20respond%20with%20the%20string%20%60pong%60%20to%20a%20POST%20request%20%5Bping%20logic%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/blob/f272e6c3fcd8a18c6ff571d7fcbfde857f63ef99/internal/core/serverless_connector/connector.go%23L27-L232%29.%0A-%20If%20you%E2%80%99re%20running%20in%20Docker%2C%20don%E2%80%99t%20use%20%60localhost%60%20or%20%60127.0.0.1%60%20for%20service%20endpoints%E2%80%94use%20%60host.docker.internal%60%20or%20your%20host%E2%80%99s%20internal%20IP%20%5Bnetwork%20troubleshooting%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/436%29.%0A-%20Make%20sure%20the%20connector%20service%20is%20not%20returning%20an%20error%20page%20%28HTML%29%20due%20to%20a%20bad%20URL%2C%20missing%20service%2C%20or%20authentication%20failure.%0A%0AIf%20you%20still%20see%20errors%20after%20these%20checks%2C%20please%20share%20your%20actual%20plugin%20%60manifest.yaml%60%20or%20the%20full%20error%20logs%20for%20more%20targeted%20help.)&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-plugin-daemon/issues/597)
yindo commented 2026-02-16 01:15:05 -05:00
Author
Owner
Copy Link
Copy Source

@AlanChan1993 commented on GitHub (Feb 4, 2026):

Hi Dosu, I have a new issue.

api-1 | 2026-02-05 01:10:45,838.838 ERROR [Dummy-81] [base.py:88] f16af259446c5538a881b6e1ead106e7 - Request to Plugin Daemon Service failed

@AlanChan1993 commented on GitHub (Feb 4, 2026): Hi Dosu, I have a new issue. api-1 | 2026-02-05 01:10:45,838.838 ERROR [Dummy-81] [base.py:88] f16af259446c5538a881b6e1ead106e7 - Request to Plugin Daemon Service failed
yindo commented 2026-02-16 01:15:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 4, 2026):

This error usually means the API service can't reach the Plugin Daemon Service. The most common causes are: the plugin daemon container isn't running or is unreachable (network/Docker misconfiguration), the PLUGIN_DAEMON_URL or SERVER_HOST/SERVER_PORT settings are wrong, or there's proxy interference (http_proxy/https_proxy not unset or no_proxy not set for local services) source source.

Check that the plugin daemon is running and healthy, PLUGIN_DAEMON_URL points to the correct host and port (not localhost/127.0.0.1 in Docker), and that your .env and compose files set SERVER_HOST=0.0.0.0 and include no_proxy for local addresses. Also, review plugin daemon logs for errors at the time of failure, and make sure the daemon has outbound internet access on first run.

If you can, share the relevant logs from both API and plugin daemon, your environment variable settings, and confirm if you made any recent changes to your deployment or configuration. This will help narrow down the root cause.

To reply, just mention @dosu.

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

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 4, 2026): <!-- Answer --> This error usually means the API service can't reach the Plugin Daemon Service. The most common causes are: the plugin daemon container isn't running or is unreachable (network/Docker misconfiguration), the PLUGIN_DAEMON_URL or SERVER_HOST/SERVER_PORT settings are wrong, or there's proxy interference (http_proxy/https_proxy not unset or no_proxy not set for local services) [source](https://github.com/langgenius/dify-plugin-daemon/issues/436#issuecomment-3231978898) [source](https://github.com/langgenius/dify-plugin-daemon/issues/373#issuecomment-3047099015). Check that the plugin daemon is running and healthy, PLUGIN_DAEMON_URL points to the correct host and port (not localhost/127.0.0.1 in Docker), and that your .env and compose files set SERVER_HOST=0.0.0.0 and include no_proxy for local addresses. Also, review plugin daemon logs for errors at the time of failure, and make sure the daemon has outbound internet access on first run. If you can, share the relevant logs from both API and plugin daemon, your environment variable settings, and confirm if you made any recent changes to your deployment or configuration. This will help narrow down the root cause. <!-- 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/1cf1615f-4723-45c8-a2fc-704ba840d64a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1cf1615f-4723-45c8-a2fc-704ba840d64a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1cf1615f-4723-45c8-a2fc-704ba840d64a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1cf1615f-4723-45c8-a2fc-704ba840d64a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1cf1615f-4723-45c8-a2fc-704ba840d64a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1cf1615f-4723-45c8-a2fc-704ba840d64a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1cf1615f-4723-45c8-a2fc-704ba840d64a?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20error%20usually%20means%20the%20API%20service%20can%27t%20reach%20the%20Plugin%20Daemon%20Service.%20The%20most%20common%20causes%20are%3A%20the%20plugin%20daemon%20container%20isn%27t%20running%20or%20is%20unreachable%20%28network/Docker%20misconfiguration%29%2C%20the%20PLUGIN_DAEMON_URL%20or%20SERVER_HOST/SERVER_PORT%20settings%20are%20wrong%2C%20or%20there%27s%20proxy%20interference%20%28http_proxy/https_proxy%20not%20unset%20or%20no_proxy%20not%20set%20for%20local%20services%29%20%5Bsource%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/436%23issuecomment-3231978898%29%20%5Bsource%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/373%23issuecomment-3047099015%29.%0A%0ACheck%20that%20the%20plugin%20daemon%20is%20running%20and%20healthy%2C%20PLUGIN_DAEMON_URL%20points%20to%20the%20correct%20host%20and%20port%20%28not%20localhost/127.0.0.1%20in%20Docker%29%2C%20and%20that%20your%20.env%20and%20compose%20files%20set%20SERVER_HOST%3D0.0.0.0%20and%20include%20no_proxy%20for%20local%20addresses.%20Also%2C%20review%20plugin%20daemon%20logs%20for%20errors%20at%20the%20time%20of%20failure%2C%20and%20make%20sure%20the%20daemon%20has%20outbound%20internet%20access%20on%20first%20run.%0A%0AIf%20you%20can%2C%20share%20the%20relevant%20logs%20from%20both%20API%20and%20plugin%20daemon%2C%20your%20environment%20variable%20settings%2C%20and%20confirm%20if%20you%20made%20any%20recent%20changes%20to%20your%20deployment%20or%20configuration.%20This%20will%20help%20narrow%20down%20the%20root%20cause.)&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-plugin-daemon/issues/597)
yindo commented 2026-02-16 01:15:06 -05:00
Author
Owner
Copy Link
Copy Source

@AlanChan1993 commented on GitHub (Feb 4, 2026):

docker-compose.yaml:
plugin_daemon:
image: langgenius/dify-plugin-daemon:0.5.2-serverless
# image: langgenius/dify-plugin-daemon:0.5.2-local
container_name: docker-plugin_daemon-1
restart: always
depends_on:
- api
- redis
- postgres
ports:
- "5003:5003"
environment:
- REDIS_HOST=redis
- REDIS_PORT=6379
- REDIS_PASSWORD=difyai123456
- DIFY_INNER_API_URL=http://api:5001
- DIFY_INNER_API_KEY=1qaz2wsx0okm9ijn3edfv4rfgb
- DB_USERNAME=postgres
- DB_PASSWORD=difyai123456
- DB_HOST=postgres
- DB_PORT=5432
- DB_DATABASE=dify
- DB_TYPE=postgresql
- DB_DEFAULT_DATABASE=dify
- PLUGIN_SERVER_PORT=5003
- PLUGIN_INSTALLING_HOST=http://api:5001
- SERVER_KEY=1qaz2wsx0okm9ijn3edfv4rfgb
- INNER_API_KEY_FOR_PLUGIN=1qaz2wsx0okm9ijn3edfv4rfgb
- PLUGIN_REMOTE_INSTALLING_HOST=0.0.0.0
- PLUGIN_REMOTE_INSTALLING_PORT=5003
- LOG_LEVEL=INFO
- PLUGIN_WORKING_PATH=/app/storage/cwd
- DIFY_API_URL=http://api:5001
- DIFY_API_KEY=1qaz2wsx0okm9ijn3edfv4rfgb
volumes:
- dify_logs:/app/logs
- dify_plugins:/app/storage/cwd
networks:
- default

.env :
DISABLE_PLUGIN_SCAN=false
DB_PLUGIN_DATABASE=dify
EXPOSE_PLUGIN_DAEMON_PORT=5003
PLUGIN_DAEMON_HOST=0.0.0.0
PLUGIN_DAEMON_PORT=5003
PLUGIN_DAEMON_SERVER_KEY=1qaz2wsx0okm9ijn3edfv4rfgb
PLUGIN_DAEMON_KEY=1qaz2wsx0okm9ijn3edfv4rfgb
PLUGIN_DAEMON_URL=http://plugin_daemon:5003
PLUGIN_MAX_PACKAGE_SIZE=52428800
PLUGIN_PPROF_ENABLED=false
PLUGIN_DEBUGGING_HOST=0.0.0.0
PLUGIN_DEBUGGING_PORT=5003
EXPOSE_PLUGIN_DEBUGGING_HOST=10.180.214.1
EXPOSE_PLUGIN_DEBUGGING_PORT=5003
PLUGIN_DIFY_INNER_API_KEY=1qaz2wsx0okm9ijn3edfv4rfgb
PLUGIN_DIFY_INNER_API_URL=http://api:5001

@AlanChan1993 commented on GitHub (Feb 4, 2026): docker-compose.yaml: plugin_daemon: image: langgenius/dify-plugin-daemon:0.5.2-serverless # image: langgenius/dify-plugin-daemon:0.5.2-local container_name: docker-plugin_daemon-1 restart: always depends_on: - api - redis - postgres ports: - "5003:5003" environment: - REDIS_HOST=redis - REDIS_PORT=6379 - REDIS_PASSWORD=difyai123456 - DIFY_INNER_API_URL=http://api:5001 - DIFY_INNER_API_KEY=1qaz2wsx0okm9ijn3edfv4rfgb - DB_USERNAME=postgres - DB_PASSWORD=difyai123456 - DB_HOST=postgres - DB_PORT=5432 - DB_DATABASE=dify - DB_TYPE=postgresql - DB_DEFAULT_DATABASE=dify - PLUGIN_SERVER_PORT=5003 - PLUGIN_INSTALLING_HOST=http://api:5001 - SERVER_KEY=1qaz2wsx0okm9ijn3edfv4rfgb - INNER_API_KEY_FOR_PLUGIN=1qaz2wsx0okm9ijn3edfv4rfgb - PLUGIN_REMOTE_INSTALLING_HOST=0.0.0.0 - PLUGIN_REMOTE_INSTALLING_PORT=5003 - LOG_LEVEL=INFO - PLUGIN_WORKING_PATH=/app/storage/cwd - DIFY_API_URL=http://api:5001 - DIFY_API_KEY=1qaz2wsx0okm9ijn3edfv4rfgb volumes: - dify_logs:/app/logs - dify_plugins:/app/storage/cwd networks: - default .env : DISABLE_PLUGIN_SCAN=false DB_PLUGIN_DATABASE=dify EXPOSE_PLUGIN_DAEMON_PORT=5003 PLUGIN_DAEMON_HOST=0.0.0.0 PLUGIN_DAEMON_PORT=5003 PLUGIN_DAEMON_SERVER_KEY=1qaz2wsx0okm9ijn3edfv4rfgb PLUGIN_DAEMON_KEY=1qaz2wsx0okm9ijn3edfv4rfgb PLUGIN_DAEMON_URL=http://plugin_daemon:5003 PLUGIN_MAX_PACKAGE_SIZE=52428800 PLUGIN_PPROF_ENABLED=false PLUGIN_DEBUGGING_HOST=0.0.0.0 PLUGIN_DEBUGGING_PORT=5003 EXPOSE_PLUGIN_DEBUGGING_HOST=10.180.214.1 EXPOSE_PLUGIN_DEBUGGING_PORT=5003 PLUGIN_DIFY_INNER_API_KEY=1qaz2wsx0okm9ijn3edfv4rfgb PLUGIN_DIFY_INNER_API_URL=http://api:5001
yindo commented 2026-02-16 01:15:06 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 4, 2026):

Your config is close, but a few things can cause the "Request to Plugin Daemon Service failed" error in Docker Compose:

  1. Make sure the API service uses PLUGIN_DAEMON_URL=http://plugin_daemon:5003 (not localhost or 127.0.0.1) for inter-container calls. This matches your Compose service name and port, which is correct for Docker networking [source].

  2. Add no_proxy=localhost,127.0.0.1,db,redis,plugin_daemon,api to your .env file and propagate it to the API service environment. This prevents proxy settings from interfering with local service communication [source].

  3. Confirm that SERVER_HOST (or PLUGIN_DAEMON_HOST) is set to 0.0.0.0 and SERVER_PORT (or PLUGIN_DAEMON_PORT) is set to 5003 in both your .env and Compose environment. The plugin daemon must bind to all interfaces on the correct port [source].

  4. If you use a corporate proxy, you may need to build a custom plugin_daemon image with your CA certificate included, and use a wrapper entrypoint for Python services to update the certifi bundle [source].

  5. Double-check that all services are healthy and that the plugin_daemon container is actually listening on port 5003. You can exec into the API container and run curl http://plugin_daemon:5003/health/check to verify connectivity.

If you follow these steps and still see errors, check the plugin_daemon logs for panics or binding errors at startup. Let me know if you need help with a specific log or error message.

To reply, just mention @dosu.

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

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 4, 2026): <!-- Answer --> Your config is close, but a few things can cause the "Request to Plugin Daemon Service failed" error in Docker Compose: 1. Make sure the API service uses `PLUGIN_DAEMON_URL=http://plugin_daemon:5003` (not localhost or 127.0.0.1) for inter-container calls. This matches your Compose service name and port, which is correct for Docker networking [[source]](https://github.com/langgenius/dify-plugin-daemon/issues/373#issuecomment-3684589054). 2. Add `no_proxy=localhost,127.0.0.1,db,redis,plugin_daemon,api` to your `.env` file and propagate it to the API service environment. This prevents proxy settings from interfering with local service communication [[source]](https://github.com/langgenius/dify-plugin-daemon/issues/373#issuecomment-3684589054). 3. Confirm that `SERVER_HOST` (or `PLUGIN_DAEMON_HOST`) is set to `0.0.0.0` and `SERVER_PORT` (or `PLUGIN_DAEMON_PORT`) is set to `5003` in both your `.env` and Compose environment. The plugin daemon must bind to all interfaces on the correct port [[source]](https://github.com/langgenius/dify-plugin-daemon/blob/f272e6c3fcd8a18c6ff571d7fcbfde857f63ef99/.env.example#L1-L194). 4. If you use a corporate proxy, you may need to build a custom plugin_daemon image with your CA certificate included, and use a wrapper entrypoint for Python services to update the certifi bundle [[source]](https://github.com/langgenius/dify-plugin-daemon/issues/329#issuecomment-2948268275). 5. Double-check that all services are healthy and that the plugin_daemon container is actually listening on port 5003. You can exec into the API container and run `curl http://plugin_daemon:5003/health/check` to verify connectivity. If you follow these steps and still see errors, check the plugin_daemon logs for panics or binding errors at startup. Let me know if you need help with a specific log or error message. <!-- 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/aa94b3cf-ed5a-414f-a62b-9d758630e973?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/aa94b3cf-ed5a-414f-a62b-9d758630e973?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/aa94b3cf-ed5a-414f-a62b-9d758630e973?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/aa94b3cf-ed5a-414f-a62b-9d758630e973?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/aa94b3cf-ed5a-414f-a62b-9d758630e973?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/aa94b3cf-ed5a-414f-a62b-9d758630e973?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/aa94b3cf-ed5a-414f-a62b-9d758630e973?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Your%20config%20is%20close%2C%20but%20a%20few%20things%20can%20cause%20the%20%22Request%20to%20Plugin%20Daemon%20Service%20failed%22%20error%20in%20Docker%20Compose%3A%0A%0A1.%20Make%20sure%20the%20API%20service%20uses%20%60PLUGIN_DAEMON_URL%3Dhttp%3A//plugin_daemon%3A5003%60%20%28not%20localhost%20or%20127.0.0.1%29%20for%20inter-container%20calls.%20This%20matches%20your%20Compose%20service%20name%20and%20port%2C%20which%20is%20correct%20for%20Docker%20networking%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/373%23issuecomment-3684589054%29.%0A%0A2.%20Add%20%60no_proxy%3Dlocalhost%2C127.0.0.1%2Cdb%2Credis%2Cplugin_daemon%2Capi%60%20to%20your%20%60.env%60%20file%20and%20propagate%20it%20to%20the%20API%20service%20environment.%20This%20prevents%20proxy%20settings%20from%20interfering%20with%20local%20service%20communication%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/373%23issuecomment-3684589054%29.%0A%0A3.%20Confirm%20that%20%60SERVER_HOST%60%20%28or%20%60PLUGIN_DAEMON_HOST%60%29%20is%20set%20to%20%600.0.0.0%60%20and%20%60SERVER_PORT%60%20%28or%20%60PLUGIN_DAEMON_PORT%60%29%20is%20set%20to%20%605003%60%20in%20both%20your%20%60.env%60%20and%20Compose%20environment.%20The%20plugin%20daemon%20must%20bind%20to%20all%20interfaces%20on%20the%20correct%20port%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/blob/f272e6c3fcd8a18c6ff571d7fcbfde857f63ef99/.env.example%23L1-L194%29.%0A%0A4.%20If%20you%20use%20a%20corporate%20proxy%2C%20you%20may%20need%20to%20build%20a%20custom%20plugin_daemon%20image%20with%20your%20CA%20certificate%20included%2C%20and%20use%20a%20wrapper%20entrypoint%20for%20Python%20services%20to%20update%20the%20certifi%20bundle%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/329%23issuecomment-2948268275%29.%0A%0A5.%20Double-check%20that%20all%20services%20are%20healthy%20and%20that%20the%20plugin_daemon%20container%20is%20actually%20listening%20on%20port%205003.%20You%20can%20exec%20into%20the%20API%20container%20and%20run%20%60curl%20http%3A//plugin_daemon%3A5003/health/check%60%20to%20verify%20connectivity.%0A%0AIf%20you%20follow%20these%20steps%20and%20still%20see%20errors%2C%20check%20the%20plugin_daemon%20logs%20for%20panics%20or%20binding%20errors%20at%20startup.%20Let%20me%20know%20if%20you%20need%20help%20with%20a%20specific%20log%20or%20error%20message.)&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-plugin-daemon/issues/597)
yindo commented 2026-02-16 01:15:06 -05:00
Author
Owner
Copy Link
Copy Source

@AlanChan1993 commented on GitHub (Feb 4, 2026):

modify the file . but create a new issue:

api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/plugin/impl/base.py", line 234, in _request_with_plugin_daemon_response
api-1 | response = self._request(method, path, headers, data, params, files)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/core/plugin/impl/base.py", line 89, in _request
api-1 | raise PluginDaemonInnerError(code=-500, message="Request to Plugin Daemon Service failed")
api-1 | core.plugin.entities.plugin_daemon.PluginDaemonInnerError
api-1 | 2026-02-05 02:40:16,320.320 ERROR [Dummy-45] [base.py:88] 49970c2a0a2b5b50abd34ecb1a91b041 - Request to Plugin Daemon Service failed
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions
api-1 | yield
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 236, in handle_request
api-1 | resp = self._pool.handle_request(req)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 256, in handle_request
api-1 | raise exc from None
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 236, in handle_request
api-1 | response = connection.handle_request(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 101, in handle_request
api-1 | raise exc
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 78, in handle_request
api-1 | stream = self._connect(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 124, in _connect
api-1 | stream = self._network_backend.connect_tcp(**kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_backends/sync.py", line 207, in connect_tcp
api-1 | with map_exceptions(exc_map):
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit
api-1 | self.gen.throw(value)
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
api-1 | raise to_exc(exc) from exc
api-1 | httpcore.ConnectError: [Errno -2] Name or service not known
api-1 |
api-1 | The above exception was the direct cause of the following exception:
api-1 |
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/plugin/impl/base.py", line 86, in _request
api-1 | response = httpx.request(**request_kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request
api-1 | return client.request(
api-1 | ^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request
api-1 | return self.send(request, auth=auth, follow_redirects=follow_redirects)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send
api-1 | response = self._send_handling_auth(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth
api-1 | response = self._send_handling_redirects(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects
api-1 | response = self._send_single_request(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request
api-1 | response = transport.handle_request(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request
api-1 | with map_httpcore_exceptions():
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit
api-1 | self.gen.throw(value)
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions
api-1 | raise mapped_exc(message) from exc
api-1 | httpx.ConnectError: [Errno -2] Name or service not known
api-1 | 2026-02-05 02:40:16,321.321 ERROR [Dummy-45] [base.py:241] 49970c2a0a2b5b50abd34ecb1a91b041 - Failed to request plugin daemon, url: plugin/c3297e11-18c9-4237-95e2-a85c6a56776d/management/install/tasks
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions
api-1 | yield
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 236, in handle_request
api-1 | resp = self._pool.handle_request(req)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 256, in handle_request
api-1 | raise exc from None
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 236, in handle_request
api-1 | response = connection.handle_request(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 101, in handle_request
api-1 | raise exc
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 78, in handle_request
api-1 | stream = self._connect(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 124, in _connect
api-1 | stream = self._network_backend.connect_tcp(**kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_backends/sync.py", line 207, in connect_tcp
api-1 | with map_exceptions(exc_map):
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit
api-1 | self.gen.throw(value)
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
api-1 | raise to_exc(exc) from exc
api-1 | httpcore.ConnectError: [Errno -2] Name or service not known
api-1 |
api-1 | The above exception was the direct cause of the following exception:
api-1 |
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/plugin/impl/base.py", line 86, in _request
api-1 | response = httpx.request(**request_kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request
api-1 | return client.request(
api-1 | ^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request
api-1 | return self.send(request, auth=auth, follow_redirects=follow_redirects)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send
api-1 | response = self._send_handling_auth(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth
api-1 | response = self._send_handling_redirects(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects
api-1 | response = self._send_single_request(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request
api-1 | response = transport.handle_request(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request
api-1 | with map_httpcore_exceptions():
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit
api-1 | self.gen.throw(value)
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions
api-1 | raise mapped_exc(message) from exc
api-1 | httpx.ConnectError: [Errno -2] Name or service not known
api-1 |
api-1 | During handling of the above exception, another exception occurred:
api-1 |
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/plugin/impl/base.py", line 234, in _request_with_plugin_daemon_response
api-1 | response = self._request(method, path, headers, data, params, files)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/core/plugin/impl/base.py", line 89, in _request
api-1 | raise PluginDaemonInnerError(code=-500, message="Request to Plugin Daemon Service failed")
api-1 | core.plugin.entities.plugin_daemon.PluginDaemonInnerError
api-1 | 2026-02-05 02:40:16,349.349 ERROR [Dummy-46] [base.py:88] dd6e411d9bf25bd6a64262be2ff74ea5 - Request to Plugin Daemon Service failed
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions
api-1 | yield
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 236, in handle_request
api-1 | resp = self._pool.handle_request(req)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 256, in handle_request
api-1 | raise exc from None
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 236, in handle_request
api-1 | response = connection.handle_request(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 101, in handle_request
api-1 | raise exc
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 78, in handle_request
api-1 | stream = self._connect(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 124, in _connect
api-1 | stream = self._network_backend.connect_tcp(**kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_backends/sync.py", line 207, in connect_tcp
api-1 | with map_exceptions(exc_map):
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit
api-1 | self.gen.throw(value)
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
api-1 | raise to_exc(exc) from exc
api-1 | httpcore.ConnectError: [Errno -2] Name or service not known
api-1 |
api-1 | The above exception was the direct cause of the following exception:
api-1 |
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/plugin/impl/base.py", line 86, in _request
api-1 | response = httpx.request(**request_kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request
api-1 | return client.request(
api-1 | ^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request
api-1 | return self.send(request, auth=auth, follow_redirects=follow_redirects)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send
api-1 | response = self._send_handling_auth(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth
api-1 | response = self._send_handling_redirects(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects
api-1 | response = self._send_single_request(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request
api-1 | response = transport.handle_request(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request
api-1 | with map_httpcore_exceptions():
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit
api-1 | self.gen.throw(value)
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions
api-1 | raise mapped_exc(message) from exc
api-1 | httpx.ConnectError: [Errno -2] Name or service not known
api-1 | 2026-02-05 02:40:16,350.350 ERROR [Dummy-46] [base.py:241] dd6e411d9bf25bd6a64262be2ff74ea5 - Failed to request plugin daemon, url: plugin/c3297e11-18c9-4237-95e2-a85c6a56776d/management/models
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions
api-1 | yield
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 236, in handle_request
api-1 | resp = self._pool.handle_request(req)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 256, in handle_request
api-1 | raise exc from None
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 236, in handle_request
api-1 | response = connection.handle_request(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 101, in handle_request
api-1 | raise exc
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 78, in handle_request
api-1 | stream = self._connect(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 124, in _connect
api-1 | stream = self._network_backend.connect_tcp(**kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_backends/sync.py", line 207, in connect_tcp
api-1 | with map_exceptions(exc_map):
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit
api-1 | self.gen.throw(value)
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
api-1 | raise to_exc(exc) from exc
api-1 | httpcore.ConnectError: [Errno -2] Name or service not known
api-1 |
api-1 | The above exception was the direct cause of the following exception:
api-1 |
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/plugin/impl/base.py", line 86, in _request
api-1 | response = httpx.request(**request_kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request
api-1 | return client.request(
api-1 | ^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request
api-1 | return self.send(request, auth=auth, follow_redirects=follow_redirects)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send
api-1 | response = self._send_handling_auth(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth
api-1 | response = self._send_handling_redirects(
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects
api-1 | response = self._send_single_request(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request
api-1 | response = transport.handle_request(request)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request
api-1 | with map_httpcore_exceptions():
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit
api-1 | self.gen.throw(value)
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions
api-1 | raise mapped_exc(message) from exc
api-1 | httpx.ConnectError: [Errno -2] Name or service not known
api-1 |
api-1 | During handling of the above exception, another exception occurred:
api-1 |
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/plugin/impl/base.py", line 234, in _request_with_plugin_daemon_response
api-1 | response = self._request(method, path, headers, data, params, files)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/core/plugin/impl/base.py", line 89, in _request
api-1 | raise PluginDaemonInnerError(code=-500, message="Request to Plugin Daemon Service failed")
api-1 | core.plugin.entities.plugin_daemon.PluginDaemonInnerError

@AlanChan1993 commented on GitHub (Feb 4, 2026): modify the file . but create a new issue: api-1 | Traceback (most recent call last): api-1 | File "/app/api/core/plugin/impl/base.py", line 234, in _request_with_plugin_daemon_response api-1 | response = self._request(method, path, headers, data, params, files) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/core/plugin/impl/base.py", line 89, in _request api-1 | raise PluginDaemonInnerError(code=-500, message="Request to Plugin Daemon Service failed") api-1 | core.plugin.entities.plugin_daemon.PluginDaemonInnerError api-1 | 2026-02-05 02:40:16,320.320 ERROR [Dummy-45] [base.py:88] 49970c2a0a2b5b50abd34ecb1a91b041 - Request to Plugin Daemon Service failed api-1 | Traceback (most recent call last): api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions api-1 | yield api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 236, in handle_request api-1 | resp = self._pool.handle_request(req) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 256, in handle_request api-1 | raise exc from None api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 236, in handle_request api-1 | response = connection.handle_request( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 101, in handle_request api-1 | raise exc api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 78, in handle_request api-1 | stream = self._connect(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 124, in _connect api-1 | stream = self._network_backend.connect_tcp(**kwargs) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_backends/sync.py", line 207, in connect_tcp api-1 | with map_exceptions(exc_map): api-1 | ^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ api-1 | self.gen.throw(value) api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions api-1 | raise to_exc(exc) from exc api-1 | httpcore.ConnectError: [Errno -2] Name or service not known api-1 | api-1 | The above exception was the direct cause of the following exception: api-1 | api-1 | Traceback (most recent call last): api-1 | File "/app/api/core/plugin/impl/base.py", line 86, in _request api-1 | response = httpx.request(**request_kwargs) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request api-1 | return client.request( api-1 | ^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request api-1 | return self.send(request, auth=auth, follow_redirects=follow_redirects) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send api-1 | response = self._send_handling_auth( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth api-1 | response = self._send_handling_redirects( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects api-1 | response = self._send_single_request(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request api-1 | response = transport.handle_request(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request api-1 | with map_httpcore_exceptions(): api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ api-1 | self.gen.throw(value) api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions api-1 | raise mapped_exc(message) from exc api-1 | httpx.ConnectError: [Errno -2] Name or service not known api-1 | 2026-02-05 02:40:16,321.321 ERROR [Dummy-45] [base.py:241] 49970c2a0a2b5b50abd34ecb1a91b041 - Failed to request plugin daemon, url: plugin/c3297e11-18c9-4237-95e2-a85c6a56776d/management/install/tasks api-1 | Traceback (most recent call last): api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions api-1 | yield api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 236, in handle_request api-1 | resp = self._pool.handle_request(req) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 256, in handle_request api-1 | raise exc from None api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 236, in handle_request api-1 | response = connection.handle_request( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 101, in handle_request api-1 | raise exc api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 78, in handle_request api-1 | stream = self._connect(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 124, in _connect api-1 | stream = self._network_backend.connect_tcp(**kwargs) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_backends/sync.py", line 207, in connect_tcp api-1 | with map_exceptions(exc_map): api-1 | ^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ api-1 | self.gen.throw(value) api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions api-1 | raise to_exc(exc) from exc api-1 | httpcore.ConnectError: [Errno -2] Name or service not known api-1 | api-1 | The above exception was the direct cause of the following exception: api-1 | api-1 | Traceback (most recent call last): api-1 | File "/app/api/core/plugin/impl/base.py", line 86, in _request api-1 | response = httpx.request(**request_kwargs) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request api-1 | return client.request( api-1 | ^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request api-1 | return self.send(request, auth=auth, follow_redirects=follow_redirects) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send api-1 | response = self._send_handling_auth( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth api-1 | response = self._send_handling_redirects( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects api-1 | response = self._send_single_request(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request api-1 | response = transport.handle_request(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request api-1 | with map_httpcore_exceptions(): api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ api-1 | self.gen.throw(value) api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions api-1 | raise mapped_exc(message) from exc api-1 | httpx.ConnectError: [Errno -2] Name or service not known api-1 | api-1 | During handling of the above exception, another exception occurred: api-1 | api-1 | Traceback (most recent call last): api-1 | File "/app/api/core/plugin/impl/base.py", line 234, in _request_with_plugin_daemon_response api-1 | response = self._request(method, path, headers, data, params, files) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/core/plugin/impl/base.py", line 89, in _request api-1 | raise PluginDaemonInnerError(code=-500, message="Request to Plugin Daemon Service failed") api-1 | core.plugin.entities.plugin_daemon.PluginDaemonInnerError api-1 | 2026-02-05 02:40:16,349.349 ERROR [Dummy-46] [base.py:88] dd6e411d9bf25bd6a64262be2ff74ea5 - Request to Plugin Daemon Service failed api-1 | Traceback (most recent call last): api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions api-1 | yield api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 236, in handle_request api-1 | resp = self._pool.handle_request(req) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 256, in handle_request api-1 | raise exc from None api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 236, in handle_request api-1 | response = connection.handle_request( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 101, in handle_request api-1 | raise exc api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 78, in handle_request api-1 | stream = self._connect(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 124, in _connect api-1 | stream = self._network_backend.connect_tcp(**kwargs) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_backends/sync.py", line 207, in connect_tcp api-1 | with map_exceptions(exc_map): api-1 | ^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ api-1 | self.gen.throw(value) api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions api-1 | raise to_exc(exc) from exc api-1 | httpcore.ConnectError: [Errno -2] Name or service not known api-1 | api-1 | The above exception was the direct cause of the following exception: api-1 | api-1 | Traceback (most recent call last): api-1 | File "/app/api/core/plugin/impl/base.py", line 86, in _request api-1 | response = httpx.request(**request_kwargs) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request api-1 | return client.request( api-1 | ^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request api-1 | return self.send(request, auth=auth, follow_redirects=follow_redirects) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send api-1 | response = self._send_handling_auth( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth api-1 | response = self._send_handling_redirects( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects api-1 | response = self._send_single_request(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request api-1 | response = transport.handle_request(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request api-1 | with map_httpcore_exceptions(): api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ api-1 | self.gen.throw(value) api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions api-1 | raise mapped_exc(message) from exc api-1 | httpx.ConnectError: [Errno -2] Name or service not known api-1 | 2026-02-05 02:40:16,350.350 ERROR [Dummy-46] [base.py:241] dd6e411d9bf25bd6a64262be2ff74ea5 - Failed to request plugin daemon, url: plugin/c3297e11-18c9-4237-95e2-a85c6a56776d/management/models api-1 | Traceback (most recent call last): api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions api-1 | yield api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 236, in handle_request api-1 | resp = self._pool.handle_request(req) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 256, in handle_request api-1 | raise exc from None api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection_pool.py", line 236, in handle_request api-1 | response = connection.handle_request( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 101, in handle_request api-1 | raise exc api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 78, in handle_request api-1 | stream = self._connect(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_sync/connection.py", line 124, in _connect api-1 | stream = self._network_backend.connect_tcp(**kwargs) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_backends/sync.py", line 207, in connect_tcp api-1 | with map_exceptions(exc_map): api-1 | ^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ api-1 | self.gen.throw(value) api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions api-1 | raise to_exc(exc) from exc api-1 | httpcore.ConnectError: [Errno -2] Name or service not known api-1 | api-1 | The above exception was the direct cause of the following exception: api-1 | api-1 | Traceback (most recent call last): api-1 | File "/app/api/core/plugin/impl/base.py", line 86, in _request api-1 | response = httpx.request(**request_kwargs) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request api-1 | return client.request( api-1 | ^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request api-1 | return self.send(request, auth=auth, follow_redirects=follow_redirects) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send api-1 | response = self._send_handling_auth( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth api-1 | response = self._send_handling_redirects( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects api-1 | response = self._send_single_request(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request api-1 | response = transport.handle_request(request) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request api-1 | with map_httpcore_exceptions(): api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ api-1 | self.gen.throw(value) api-1 | File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions api-1 | raise mapped_exc(message) from exc api-1 | httpx.ConnectError: [Errno -2] Name or service not known api-1 | api-1 | During handling of the above exception, another exception occurred: api-1 | api-1 | Traceback (most recent call last): api-1 | File "/app/api/core/plugin/impl/base.py", line 234, in _request_with_plugin_daemon_response api-1 | response = self._request(method, path, headers, data, params, files) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/core/plugin/impl/base.py", line 89, in _request api-1 | raise PluginDaemonInnerError(code=-500, message="Request to Plugin Daemon Service failed") api-1 | core.plugin.entities.plugin_daemon.PluginDaemonInnerError
yindo commented 2026-02-16 01:15:06 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 4, 2026):

The error likely points to one of these root causes:

  1. Invalid or corrupted plugin unique identifier: If your plugin's manifest.yaml or provider yaml files have missing or incorrect author or name fields, or if the identifier doesn't match the required format, the daemon will reject it and management endpoints will fail. This can also happen if the identifier starts with a / or contains uppercase letters. Fix by ensuring all plugin metadata is correct and matches the expected pattern, then repackage and reinstall the plugin. Reference Reference

  2. Stale or corrupted plugin data: Old or invalid plugin records in your database or plugin storage directories can cause persistent errors. Clear the plugin-related tables (plugin_installations, plugin_declarations, ai_model_installations, plugins) and remove plugin files from /app/storage/cwd/plugins/ (plugin, plugin-working, persistence, plugin-root), then restart the plugin daemon. Reference

  3. Malformed JSON from the daemon: If the daemon returns malformed or unexpected JSON (wrong shape, missing fields, etc.), the API will fail to parse it, resulting in errors like this. Add a sanitizer/normalizer in the API before parsing the daemon response to catch and log malformed data, returning a clear error instead of a stack trace. Reference

  4. Missing Python dependencies: Some plugins (like ollama) require dependencies such as numpy. If these are missing in the plugin daemon container, the daemon may panic or return 500 errors at management endpoints. Install the required dependencies inside the container if needed. Reference

To move forward, please:

  • Specify which file(s) you modified before this error appeared.
  • Check the plugin daemon logs for errors at the time of failure.
  • Confirm the plugin with ID c3297e11-18c9-4237-95e2-a85c6a56776d is valid and present in your database.
  • Try cleaning up plugin data as described above and restart the daemon.

If you suspect malformed JSON, try hitting the /plugin/c3297e11-18c9-4237-95e2-a85c6a56776d/management/models endpoint directly (e.g., with curl) and inspect the raw response. If it’s not a valid JSON object, add a sanitizer as suggested in the linked thread.

To reply, just mention @dosu.

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

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 4, 2026): <!-- Answer --> The error likely points to one of these root causes: 1. **Invalid or corrupted plugin unique identifier**: If your plugin's `manifest.yaml` or provider yaml files have missing or incorrect `author` or `name` fields, or if the identifier doesn't match the required format, the daemon will reject it and management endpoints will fail. This can also happen if the identifier starts with a `/` or contains uppercase letters. Fix by ensuring all plugin metadata is correct and matches the expected pattern, then repackage and reinstall the plugin. [Reference](https://github.com/langgenius/dify-plugin-daemon/issues/112#issuecomment-2731612627) [Reference](https://github.com/langgenius/dify-plugin-daemon/issues/395) 2. **Stale or corrupted plugin data**: Old or invalid plugin records in your database or plugin storage directories can cause persistent errors. Clear the plugin-related tables (`plugin_installations`, `plugin_declarations`, `ai_model_installations`, `plugins`) and remove plugin files from `/app/storage/cwd/plugins/` (plugin, plugin-working, persistence, plugin-root), then restart the plugin daemon. [Reference](https://github.com/langgenius/dify-plugin-daemon/issues/353#issuecomment-2987160303) 3. **Malformed JSON from the daemon**: If the daemon returns malformed or unexpected JSON (wrong shape, missing fields, etc.), the API will fail to parse it, resulting in errors like this. Add a sanitizer/normalizer in the API before parsing the daemon response to catch and log malformed data, returning a clear error instead of a stack trace. [Reference](https://github.com/langgenius/dify-plugin-daemon/issues/427#issuecomment-3217669677) 4. **Missing Python dependencies**: Some plugins (like ollama) require dependencies such as numpy. If these are missing in the plugin daemon container, the daemon may panic or return 500 errors at management endpoints. Install the required dependencies inside the container if needed. [Reference](https://github.com/langgenius/dify-plugin-daemon/issues/331) To move forward, please: - Specify which file(s) you modified before this error appeared. - Check the plugin daemon logs for errors at the time of failure. - Confirm the plugin with ID `c3297e11-18c9-4237-95e2-a85c6a56776d` is valid and present in your database. - Try cleaning up plugin data as described above and restart the daemon. If you suspect malformed JSON, try hitting the `/plugin/c3297e11-18c9-4237-95e2-a85c6a56776d/management/models` endpoint directly (e.g., with curl) and inspect the raw response. If it’s not a valid JSON object, add a sanitizer as suggested in the linked thread. <!-- 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/dd300261-c5ca-49c9-8718-8e4c2eca6c06?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/dd300261-c5ca-49c9-8718-8e4c2eca6c06?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/dd300261-c5ca-49c9-8718-8e4c2eca6c06?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/dd300261-c5ca-49c9-8718-8e4c2eca6c06?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/dd300261-c5ca-49c9-8718-8e4c2eca6c06?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/dd300261-c5ca-49c9-8718-8e4c2eca6c06?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/dd300261-c5ca-49c9-8718-8e4c2eca6c06?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20error%20likely%20points%20to%20one%20of%20these%20root%20causes%3A%0A%0A1.%20%2A%2AInvalid%20or%20corrupted%20plugin%20unique%20identifier%2A%2A%3A%20If%20your%20plugin%27s%20%60manifest.yaml%60%20or%20provider%20yaml%20files%20have%20missing%20or%20incorrect%20%60author%60%20or%20%60name%60%20fields%2C%20or%20if%20the%20identifier%20doesn%27t%20match%20the%20required%20format%2C%20the%20daemon%20will%20reject%20it%20and%20management%20endpoints%20will%20fail.%20This%20can%20also%20happen%20if%20the%20identifier%20starts%20with%20a%20%60/%60%20or%20contains%20uppercase%20letters.%20Fix%20by%20ensuring%20all%20plugin%20metadata%20is%20correct%20and%20matches%20the%20expected%20pattern%2C%20then%20repackage%20and%20reinstall%20the%20plugin.%20%5BReference%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/112%23issuecomment-2731612627%29%20%5BReference%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/395%29%0A%0A2.%20%2A%2AStale%20or%20corrupted%20plugin%20data%2A%2A%3A%20Old%20or%20invalid%20plugin%20records%20in%20your%20database%20or%20plugin%20storage%20directories%20can%20cause%20persistent%20errors.%20Clear%20the%20plugin-related%20tables%20%28%60plugin_installations%60%2C%20%60plugin_declarations%60%2C%20%60ai_model_installations%60%2C%20%60plugins%60%29%20and%20remove%20plugin%20files%20from%20%60/app/storage/cwd/plugins/%60%20%28plugin%2C%20plugin-working%2C%20persistence%2C%20plugin-root%29%2C%20then%20restart%20the%20plugin%20daemon.%20%5BReference%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/353%23issuecomment-2987160303%29%0A%0A3.%20%2A%2AMalformed%20JSON%20from%20the%20daemon%2A%2A%3A%20If%20the%20daemon%20returns%20malformed%20or%20unexpected%20JSON%20%28wrong%20shape%2C%20missing%20fields%2C%20etc.%29%2C%20the%20API%20will%20fail%20to%20parse%20it%2C%20resulting%20in%20errors%20like%20this.%20Add%20a%20sanitizer/normalizer%20in%20the%20API%20before%20parsing%20the%20daemon%20response%20to%20catch%20and%20log%20malformed%20data%2C%20returning%20a%20clear%20error%20instead%20of%20a%20stack%20trace.%20%5BReference%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/427%23issuecomment-3217669677%29%0A%0A4.%20%2A%2AMissing%20Python%20dependencies%2A%2A%3A%20Some%20plugins%20%28like%20ollama%29%20require%20dependencies%20such%20as%20numpy.%20If%20these%20are%20missing%20in%20the%20plugin%20daemon%20container%2C%20the%20daemon%20may%20panic%20or%20return%20500%20errors%20at%20management%20endpoints.%20Install%20the%20required%20dependencies%20inside%20the%20container%20if%20needed.%20%5BReference%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/issues/331%29%0A%0ATo%20move%20forward%2C%20please%3A%0A-%20Specify%20which%20file%28s%29%20you%20modified%20before%20this%20error%20appeared.%0A-%20Check%20the%20plugin%20daemon%20logs%20for%20errors%20at%20the%20time%20of%20failure.%0A-%20Confirm%20the%20plugin%20with%20ID%20%60c3297e11-18c9-4237-95e2-a85c6a56776d%60%20is%20valid%20and%20present%20in%20your%20database.%0A-%20Try%20cleaning%20up%20plugin%20data%20as%20described%20above%20and%20restart%20the%20daemon.%0A%0AIf%20you%20suspect%20malformed%20JSON%2C%20try%20hitting%20the%20%60/plugin/c3297e11-18c9-4237-95e2-a85c6a56776d/management/models%60%20endpoint%20directly%20%28e.g.%2C%20with%20curl%29%20and%20inspect%20the%20raw%20response.%20If%20it%E2%80%99s%20not%20a%20valid%20JSON%20object%2C%20add%20a%20sanitizer%20as%20suggested%20in%20the%20linked%20thread.)&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-plugin-daemon/issues/597)
yindo commented 2026-02-16 01:15:06 -05:00
Author
Owner
Copy Link
Copy Source

@AlanChan1993 commented on GitHub (Feb 4, 2026):

Is it necessary to install the python runtime environment in a docker container

@AlanChan1993 commented on GitHub (Feb 4, 2026): Is it necessary to install the python runtime environment in a docker container
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Windows
bug
cmd
documentation
enhancement
go
good first issue
plugin-daemon
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug plugin-daemon
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-plugin-daemon#242
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?