langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.
https://dify.ai
Other
42.77k stars 5.92k forks source link

Credentials validation failed with status code 403 #6114

Closed Kyrie-LiuX closed 1 week ago

Kyrie-LiuX commented 1 month ago

Self Checks

Dify version

7.1st download

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

In Dify, when adding the Grog API key, an error occurs: "Credentials validation failed with status code 403".I add 讯飞星火 API key success,but grog don't work.Please help me.

✔️ Expected Behavior

I want you to analysis why this happen and solve it.

❌ Actual Behavior

No response

dosubot[bot] commented 1 month ago

@Kyrie-LiuX Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let's work on solving your issue together.

The "Credentials validation failed with status code 403" error when adding the Grog API key in Dify version 7.1 is likely due to invalid or unauthorized credentials. Here are some steps to troubleshoot and resolve the issue:

  1. Check API Key Validity: Ensure that the Grog API key is correct and has the necessary permissions. Invalid or expired keys can cause a 403 error.

  2. API Key Configuration: Follow the specific requirements and steps for adding API keys in Dify:

    • Go to the settings interface in Dify.
    • Add the API extension configuration by entering the name, API endpoint, and API Key in the "Add API-based Extension" dialog box.
    • Save the configuration.
    • Use the API in applications by adding it as a tool and referencing it in your prompts [1].
  3. Debugging Tools: Use Dify's debugging tools to get more detailed information about the API key validation process. Ensure the API key is set before debugging [2].

  4. Error Codes: Review specific error codes and messages related to a 403 status code in Dify's codebase to understand the context better [3][4][5].

If the issue persists, double-check the Grog API documentation for any specific configuration or permission requirements that might be needed for integration with Dify.

To continue talking to Dosu, mention @dosu.

Kyrie-LiuX commented 1 month ago

I need people to help me.Your advice doesn't work.

pei55 commented 1 month ago

I had the same problem.

crazywoola commented 3 weeks ago

Can not reproduce this on latest branch