Provider does not exist

[SilvaZhang]

Self Checks

• 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 (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

0.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. add my provider in api/core/model_runtime/model_provider
2. build docker image of api
3. change api image to local in dify/docker/docker-compose.yaml
4. docker compose up -d
5. login to the site and add text embedding model of my provider
6. import document to knowledge

✔️ Expected Behavior

The document can be used.

❌ Actual Behavior

The state of document imported shows error - Provider does not exist.

[dosubot]

Hello, @SilvaZhang! I'm here to help you with any bugs, questions, or contributions you have regarding Dify. Let's work together to solve the issue you're experiencing.

The "Provider does not exist" error typically occurs when the requested provider configuration is not found in the provider configurations for a given tenant. This can happen if the provider is not properly registered or recognized in the system ^[1].

Here are some steps you can take to troubleshoot and resolve this issue:

1. Verify Provider Configuration: Ensure that the provider YAML file is correctly created and placed in the appropriate directory. The YAML file should be written according to the Provider Schema and include all necessary details about the provider, such as supported model types and credential rules ^[2].

2. Check Provider Code Implementation: Make sure that the provider code is correctly implemented in the model_providers directory. The class should inherit from the Provider base class and include methods for validating provider credentials ^[2].

3. Update Docker Configuration: Ensure that the Docker configuration is correctly set up to recognize the new provider. This includes updating the docker-compose.yaml file to use the local API image that includes your provider changes.

4. Rebuild and Restart Docker Containers: After making changes, rebuild the Docker image and restart the containers to ensure that the new provider configuration is loaded.

5. Check Logs for Errors: Review the logs for any errors or warnings that might provide more insight into why the provider is not being recognized.

By following these steps, you should be able to resolve the "Provider does not exist" error and ensure that your provider is correctly registered and recognized in the Dify platform.

To continue talking to Dosu, mention @dosu.

[crazywoola]

Check the provider settings in settings -> model providers -> system models.