mirror of
https://github.com/langgenius/dify-docs.git
synced 2026-03-27 13:28:32 +07:00
52 lines
2.6 KiB
Plaintext
52 lines
2.6 KiB
Plaintext
---
|
|
dimensions:
|
|
type:
|
|
primary: operational
|
|
detail: maintenance
|
|
level: beginner
|
|
todo: Developers (Contributors) should thoroughly test before releasing; debugging
|
|
should not be the user's (Dify User / Consumer) responsibility.
|
|
standard_title: Faq
|
|
language: en
|
|
title: Frequently Asked Questions
|
|
description: This document answers common questions about Dify plugin development
|
|
and installation, including how to resolve plugin upload failures (by modifying
|
|
the author field) and how to handle verification exceptions during plugin installation
|
|
(by setting the FORCE_VERIFYING_SIGNATURE environment variable).
|
|
---
|
|
|
|
## What should I do if the plugin upload fails during installation?
|
|
|
|
**Error Details**: An error message `PluginDaemonBadRequestError: plugin_unique_identifier is not valid` appears.
|
|
|
|
**Solution**: Modify the `author` field in the `manifest.yaml` file under the plugin project and the `.yaml` file under the `/provider` path to your GitHub ID.
|
|
|
|
Rerun the plugin packaging command and install the new plugin package.
|
|
|
|
## How should I handle exceptions encountered during plugin installation?
|
|
|
|
**Problem Description**: An exception message is encountered during plugin installation: `plugin verification has been enabled, and the plugin you want to install has a bad signature`. How should this be handled?
|
|
|
|
**Solution**: Add the field `FORCE_VERIFYING_SIGNATURE=false` to the end of the `/docker/.env` configuration file. Then, run the following commands to restart the Dify service:
|
|
|
|
```bash
|
|
cd docker
|
|
docker compose down
|
|
docker compose up -d
|
|
```
|
|
|
|
After adding this field, the Dify platform will allow the installation of all plugins not listed (reviewed) on the Dify Marketplace, which may pose security risks.
|
|
|
|
It is recommended to install plugins in a testing/sandbox environment first and confirm their safety before installing them in a production environment.
|
|
|
|
{/*
|
|
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/plugin-dev-en/0331-faq.mdx) | [Report an issue](https://github.com/langgenius/dify-docs/issues/new?title=Documentation%20Issue%3A%20&body=%23%23%20Issue%20Description%0A%3C%21--%20Please%20briefly%20describe%20the%20issue%20you%20found%20--%3E%0A%0A%23%23%20Page%20Link%0Ahttps%3A%2F%2Fgithub.com%2Flanggenius%2Fdify-docs%2Fblob%2Fmain%2Fplugin-dev-en%2F0331-faq.mdx%0A%0A%23%23%20Suggested%20Changes%0A%3C%21--%20If%20you%20have%20specific%20suggestions%20for%20changes%2C%20please%20describe%20them%20here%20--%3E%0A%0A%3C%21--%20Thank%20you%20for%20helping%20improve%20our%20documentation%21%20--%3E)
|
|
|