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

install plugin locally-PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature #21874

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

Originally created by @QiNing110 on GitHub (Jan 24, 2026).

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

In my dify deployment on the server, all containers have network _ mode: host set in the docker-compose. yaml.

Signature Verification Error when Installing the TongYi Plugin locally(used dify-plugin-repackaging to repackage the plugin)

Error Message:
req_id: 563aa9c510 PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature

Image

The problem persists even after modifying FORCE_VERIFYING_SIGNATURE=false;ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES=false both .env and docker-compose.yaml

Image Image

✔️ Expected Behavior

When installing plugins offline, the plugin should be uploaded and then installed successfully.

❌ Actual Behavior

upload failed

Originally created by @QiNing110 on GitHub (Jan 24, 2026). ### 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 In my dify deployment on the server, all containers have `network _ mode: host ` set in the docker-compose. yaml. Signature Verification Error when Installing the TongYi Plugin locally(used dify-plugin-repackaging to repackage the plugin) Error Message: req_id: 563aa9c510 PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature <img width="569" height="227" alt="Image" src="https://github.com/user-attachments/assets/1cde421c-e35c-4060-9ce9-371a6ca6e06c" /> The problem persists even after modifying FORCE_VERIFYING_SIGNATURE=false;ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES=false both .env and docker-compose.yaml <img width="459" height="188" alt="Image" src="https://github.com/user-attachments/assets/033d7426-ae85-42b4-bb8e-400dc28fb646" /> <img width="839" height="500" alt="Image" src="https://github.com/user-attachments/assets/b7065232-5695-484b-b1ca-a7e43fca7a33" /> ### ✔️ Expected Behavior When installing plugins offline, the plugin should be uploaded and then installed successfully. ### ❌ Actual Behavior upload failed
yindo added the 🐞 bug label 2026-02-21 20:14:41 -05:00
yindo closed this issue 2026-02-21 20:14:41 -05:00
yindo commented 2026-02-21 20:14:41 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @QiNing110! I'm Dosu and I’m helping the dify team.

To disable plugin signature verification in your Docker deployment, make sure both FORCE_VERIFYING_SIGNATURE=false and ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES=false are set in your .env and docker-compose.yaml before starting the containers. After updating these, you must fully restart (not just reload) the plugin daemon container so it picks up the new settings—otherwise, the defaults will keep verification enabled source.

If you still see signature errors, check that your plugin package is correctly repackaged and all dependencies are bundled. Some users resolved similar issues by using the dify-plugin-repackaging tool to create an offline .difypkg and then uploading it via the local file option in the Dify web interface source. Also, ensure the plugin's model name matches its ID, and that any key-pair files used for signing do not have extra newlines source.

If the problem persists after these steps, there may be a bug or a configuration issue not covered by current documentation. Double-check your container environment variables using docker inspect <container_id> to confirm they are set as expected.

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 (Jan 24, 2026): <!-- Greeting --> Hi @QiNing110! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> To disable plugin signature verification in your Docker deployment, make sure both `FORCE_VERIFYING_SIGNATURE=false` and `ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES=false` are set in your `.env` and `docker-compose.yaml` before starting the containers. After updating these, you must fully restart (not just reload) the plugin daemon container so it picks up the new settings—otherwise, the defaults will keep verification enabled [source](https://github.com/langgenius/dify/blob/9d38af6d99d6a2f2b64004895d154ae5d59ca64d/docker/docker-compose.yaml#L956-L1010). If you still see signature errors, check that your plugin package is correctly repackaged and all dependencies are bundled. Some users resolved similar issues by using the `dify-plugin-repackaging` tool to create an offline `.difypkg` and then uploading it via the local file option in the Dify web interface [source](https://github.com/langgenius/dify-official-plugins/issues/1629). Also, ensure the plugin's model name matches its ID, and that any key-pair files used for signing do not have extra newlines [source](https://github.com/langgenius/dify-docs/issues/85). If the problem persists after these steps, there may be a bug or a configuration issue not covered by current documentation. Double-check your container environment variables using `docker inspect <container_id>` to confirm they are set as expected. <!-- 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/496d2686-d139-47bc-92d5-7238cf66b826?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/496d2686-d139-47bc-92d5-7238cf66b826?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/496d2686-d139-47bc-92d5-7238cf66b826?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/496d2686-d139-47bc-92d5-7238cf66b826?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/496d2686-d139-47bc-92d5-7238cf66b826?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/496d2686-d139-47bc-92d5-7238cf66b826?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/496d2686-d139-47bc-92d5-7238cf66b826?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=To%20disable%20plugin%20signature%20verification%20in%20your%20Docker%20deployment%2C%20make%20sure%20both%20%60FORCE_VERIFYING_SIGNATURE%3Dfalse%60%20and%20%60ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES%3Dfalse%60%20are%20set%20in%20your%20%60.env%60%20and%20%60docker-compose.yaml%60%20before%20starting%20the%20containers.%20After%20updating%20these%2C%20you%20must%20fully%20restart%20%28not%20just%20reload%29%20the%20plugin%20daemon%20container%20so%20it%20picks%20up%20the%20new%20settings%E2%80%94otherwise%2C%20the%20defaults%20will%20keep%20verification%20enabled%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/9d38af6d99d6a2f2b64004895d154ae5d59ca64d/docker/docker-compose.yaml%23L956-L1010%29.%0A%0AIf%20you%20still%20see%20signature%20errors%2C%20check%20that%20your%20plugin%20package%20is%20correctly%20repackaged%20and%20all%20dependencies%20are%20bundled.%20Some%20users%20resolved%20similar%20issues%20by%20using%20the%20%60dify-plugin-repackaging%60%20tool%20to%20create%20an%20offline%20%60.difypkg%60%20and%20then%20uploading%20it%20via%20the%20local%20file%20option%20in%20the%20Dify%20web%20interface%20%5Bsource%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1629%29.%20Also%2C%20ensure%20the%20plugin%27s%20model%20name%20matches%20its%20ID%2C%20and%20that%20any%20key-pair%20files%20used%20for%20signing%20do%20not%20have%20extra%20newlines%20%5Bsource%5D%28https%3A//github.com/langgenius/dify-docs/issues/85%29.%0A%0AIf%20the%20problem%20persists%20after%20these%20steps%2C%20there%20may%20be%20a%20bug%20or%20a%20configuration%20issue%20not%20covered%20by%20current%20documentation.%20Double-check%20your%20container%20environment%20variables%20using%20%60docker%20inspect%20%3Ccontainer_id%3E%60%20to%20confirm%20they%20are%20set%20as%20expected.)&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/31486)
yindo commented 2026-02-21 20:14:41 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 24, 2026):

Self Checks

  • I have read the Contributing Guide and Language Policy.[x] This is only for bug report, if you would like to ask a question, please head to Discussions.[x] I have searched for existing issues search for existing 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

In my dify deployment on the server, all containers have network _ mode: host set in the docker-compose. yaml.

Signature Verification Error when Installing the TongYi Plugin locally(used dify-plugin-repackaging to repackage the plugin)

Error Message: req_id: 563aa9c510 PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature

Image The problem persists even after modifying FORCE_VERIFYING_SIGNATURE=false;ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES=false both .env and docker-compose.yaml

Image Image

✔️ Expected Behavior

When installing plugins offline, the plugin should be uploaded and then installed successfully.

❌ Actual Behavior

upload failed

you can disable it FORCE_VERIFYING_SIGNATURE=false

@fatelei commented on GitHub (Jan 24, 2026): > ### 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 > In my dify deployment on the server, all containers have `network _ mode: host ` set in the docker-compose. yaml. > > Signature Verification Error when Installing the TongYi Plugin locally(used dify-plugin-repackaging to repackage the plugin) > > Error Message: req_id: 563aa9c510 PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature > > <img alt="Image" width="569" height="227" src="https://private-user-images.githubusercontent.com/201568797/540077844-1cde421c-e35c-4060-9ce9-371a6ca6e06c.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjkyNjUxNzEsIm5iZiI6MTc2OTI2NDg3MSwicGF0aCI6Ii8yMDE1Njg3OTcvNTQwMDc3ODQ0LTFjZGU0MjFjLWUzNWMtNDA2MC05Y2U5LTM3MWE2Y2E2ZTA2Yy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTI0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEyNFQxNDI3NTFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zZDYwZjRhZWI4NzgzOGEwNDAzNGM0YjJiNThmMzI2OWE0YzJhNTJkOGVjZjk3YmRhODA2ZGE2MzJmNjlmN2Q1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.27d0DVB15RvVUQUmE_Y1zjvW-2mkbOzWidccWVlVRBo"> > The problem persists even after modifying FORCE_VERIFYING_SIGNATURE=false;ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES=false both .env and docker-compose.yaml > > <img alt="Image" width="459" height="188" src="https://private-user-images.githubusercontent.com/201568797/540078040-033d7426-ae85-42b4-bb8e-400dc28fb646.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjkyNjUxNzEsIm5iZiI6MTc2OTI2NDg3MSwicGF0aCI6Ii8yMDE1Njg3OTcvNTQwMDc4MDQwLTAzM2Q3NDI2LWFlODUtNDJiNC1iYjhlLTQwMGRjMjhmYjY0Ni5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTI0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEyNFQxNDI3NTFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mNjMxYjc5ZmJjYTY1YjkxMzE3YjhjMGM1YTRmMjQwYWM0MGY0M2YyMzlhNjZhMGM3NTYwODVkZTRiNzFhY2E3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.PlG1KTYvmnx_0mANo3Jigx1Q9JX4XpbyueriwlgwnA4"> <img alt="Image" width="839" height="500" src="https://private-user-images.githubusercontent.com/201568797/540078163-b7065232-5695-484b-b1ca-a7e43fca7a33.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjkyNjUxNzEsIm5iZiI6MTc2OTI2NDg3MSwicGF0aCI6Ii8yMDE1Njg3OTcvNTQwMDc4MTYzLWI3MDY1MjMyLTU2OTUtNDg0Yi1iMWNhLWE3ZTQzZmNhN2EzMy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTI0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEyNFQxNDI3NTFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iMjU2NzE5ZGYxNzUwYWIwNDY5NmI1MzEyNjY3ZGI2MmRkNmJlYjRmNjE3ZGZjODJmNzc5YzRhNmY0N2RhMjc0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.YEIU_Teqoe0w_TbrD7RRrT9UyqENoWXS9oJho_dKzn0"> > ### ✔️ Expected Behavior > When installing plugins offline, the plugin should be uploaded and then installed successfully. > > ### ❌ Actual Behavior > upload failed you can disable it FORCE_VERIFYING_SIGNATURE=false
yindo commented 2026-02-21 20:14:41 -05:00
Author
Owner
Copy Link
Copy Source

@QiNing110 commented on GitHub (Jan 25, 2026):

Image Image Image

I have annotated FORCE_VERIFYING_SIGNATURE=false completely,it did't work

@QiNing110 commented on GitHub (Jan 25, 2026): <img width="606" height="260" alt="Image" src="https://github.com/user-attachments/assets/42148d8a-8b89-4451-8ff5-20bd4cf8b789" /> <img width="818" height="479" alt="Image" src="https://github.com/user-attachments/assets/9d4dab65-c2d8-4d4d-bffc-ee8fa46634dc" /> <img width="841" height="389" alt="Image" src="https://github.com/user-attachments/assets/70a49b38-a4b5-4097-a05c-9c2d67050e36" /> I have annotated ` FORCE_VERIFYING_SIGNATURE=false` completely,it did't work
yindo commented 2026-02-21 20:14:41 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 25, 2026):

do you restart the docker ?

@fatelei commented on GitHub (Jan 25, 2026): do you restart the docker ?
yindo commented 2026-02-21 20:14:41 -05:00
Author
Owner
Copy Link
Copy Source

@QiNing110 commented on GitHub (Jan 25, 2026):

do you restart the docker ?

yes

@QiNing110 commented on GitHub (Jan 25, 2026): > do you restart the docker ? yes
yindo commented 2026-02-21 20:14:41 -05:00
Author
Owner
Copy Link
Copy Source

@QiNing110 commented on GitHub (Jan 25, 2026):

do you restart the docker ?

yes

and the container docker-api-1 logs show like this:

Traceback (most recent call last): File "/app/api/services/plugin/plugin_service.py", line 68, in fetch_latest_plugin_version for manifest in marketplace.batch_fetch_plugin_manifests(cache_not_exists) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/helper/marketplace.py", line 26, in batch_fetch_plugin_manifests response = httpx.post(url, json={"plugin_ids": plugin_ids}, headers={"X-Dify-Version": dify_config.project.version}) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 331, in post return request( ^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request return client.request( ^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request return self.send(request, auth=auth, follow_redirects=follow_redirects) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send response = self._send_handling_auth( ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth response = self._send_handling_redirects( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects response = self._send_single_request(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request response = transport.handle_request(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request with map_httpcore_exceptions(): ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ self.gen.throw(value) File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions raise mapped_exc(message) from exc httpx.ConnectTimeout: The handshake operation timed out

@QiNing110 commented on GitHub (Jan 25, 2026): > > do you restart the docker ? > > yes and the container docker-api-1 logs show like this: `Traceback (most recent call last): File "/app/api/services/plugin/plugin_service.py", line 68, in fetch_latest_plugin_version for manifest in marketplace.batch_fetch_plugin_manifests(cache_not_exists) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/helper/marketplace.py", line 26, in batch_fetch_plugin_manifests response = httpx.post(url, json={"plugin_ids": plugin_ids}, headers={"X-Dify-Version": dify_config.project.version}) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 331, in post return request( ^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_api.py", line 118, in request return client.request( ^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 837, in request return self.send(request, auth=auth, follow_redirects=follow_redirects) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 926, in send response = self._send_handling_auth( ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 954, in _send_handling_auth response = self._send_handling_redirects( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 991, in _send_handling_redirects response = self._send_single_request(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_client.py", line 1027, in _send_single_request response = transport.handle_request(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 235, in handle_request with map_httpcore_exceptions(): ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__ self.gen.throw(value) File "/app/api/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions raise mapped_exc(message) from exc httpx.ConnectTimeout: The handshake operation timed out `
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
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#21874
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?