mirror of
https://github.com/langgenius/dify-docs.git
synced 2026-03-27 13:28:32 +07:00
60 lines
2.4 KiB
Plaintext
60 lines
2.4 KiB
Plaintext
---
|
|
title: FAQ
|
|
description: 'Author: Allen'
|
|
---
|
|
|
|
|
|
{/*
|
|
CONTRIBUTOR NOTE:
|
|
----------------
|
|
This is a legacy document that is being deprecated.
|
|
Please DO NOT make changes to this version.
|
|
All updates should be directed to the new version at:
|
|
/plugin-dev-en/0331-faq
|
|
*/}
|
|
|
|
<Card title="This Documentation is Being Deprecated" icon="circle-exclamation" href="/plugin-dev-en/0331-faq">
|
|
<p>This page is being phased out as part of our documentation reorganization.</p>
|
|
|
|
<p><strong>Click this card</strong> to be redirected to the updated version with the most current information.</p>
|
|
|
|
<p>If you notice any discrepancies or areas needing improvement in the new documentation, please use the "Report an issue" button at the bottom of the page.</p>
|
|
</Card>
|
|
|
|
## How to handle plugin upload failure during installation?
|
|
|
|
**Error Details**: The error message shows `PluginDaemonBadRequestError: plugin_unique_identifier is not valid`.
|
|
|
|
**Solution**: Modify the `author` field in both the `manifest.yaml` file in the plugin project and the `.yaml` file under the `/provider` path to your GitHub ID.
|
|
|
|
Retype the plugin packaging command and install the new plugin package.
|
|
|
|
## How to handle errors when installing plugins?
|
|
|
|
**Issue**: If you encounter the error message: `plugin verification has been enabled, and the plugin you want to install has a bad signature`, how to handle the issue?
|
|
|
|
**Solution**: Add the following line to the end of your `/docker/.env` configuration file: `FORCE_VERIFYING_SIGNATURE=false`. Run the following commands to restart the Dify service:
|
|
|
|
```bash
|
|
cd docker
|
|
docker compose down
|
|
docker compose up -d
|
|
```
|
|
|
|
Once this field is added, the Dify platform will allow the installation of all plugins that are not listed (and thus not verified) in the Dify Marketplace.
|
|
|
|
**Note**: For security reasons, always install plugins from unknown sources in a test or sandbox environment first. Confirm their safety before deploying to the production environment.
|
|
|
|
If you want to more strictly control which plugins are allowed to be installed, refer to [Signing Plugins for Third-Party Signature Verification](./publish-plugins/signing-plugins-for-third-party-signature-verification).
|
|
|
|
{/*
|
|
Contributing Section
|
|
DO NOT edit this section!
|
|
It will be automatically generated by the script.
|
|
*/}
|
|
|
|
---
|
|
|
|
[Edit this page](https://github.com/langgenius/dify-docs/edit/main/en/plugins/faq.mdx) | [Report an issue](https://github.com/langgenius/dify-docs/issues/new?template=docs.yml)
|
|
|