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

There is an error when adding the DeepSeek appkey. 分享 #8155

New Issue
Closed
opened 2026-02-21 18:24:15 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:24:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @lizhichao999 on GitHub (Feb 11, 2025).

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.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Expected Behavior

You can use it normally after adding the DeepSeek appkey correctly.

❌ Actual Behavior

No response

Originally created by @lizhichao999 on GitHub (Feb 11, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/6a39a072-c024-498f-88d0-4e3531f4f96d) ### ✔️ Expected Behavior You can use it normally after adding the DeepSeek appkey correctly. ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:24:15 -05:00
yindo commented 2026-02-21 18:24:15 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 11, 2025):

Hello, @lizhichao999! I'm here to help you with any bugs, questions, or contributions you may have for the DeepSeek appkey issue. Let's figure this out together!

I found a similar closed issue regarding the "Credentials validation failed with status code 402" error when setting up DeepSeek in Dify version 0.15.3 on a cloud environment. The suggested solution involves ensuring that the credentials are correct and valid. Here are some steps to troubleshoot and resolve the issue:

  1. Check Credentials Format: Ensure that the credentials dictionary is correctly formatted and contains all necessary fields. For DeepSeek, the required field is api_key, and there is an optional endpoint_url field for a custom API endpoint URL.

  2. Verify Credentials: Make sure the api_key is up-to-date and has the necessary permissions for accessing the DeepSeek service.

  3. Default Endpoint URL: If you are using a custom endpoint_url, verify that it is correct. The default value is "https://api.deepseek.com".

If the credentials are correct and the error persists, you may need to check with the service provider to ensure there are no issues with the account or service status [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Feb 11, 2025): <!-- Greeting --> Hello, @lizhichao999! I'm here to help you with any bugs, questions, or contributions you may have for the DeepSeek appkey issue. Let's figure this out together! <!-- Answer --> I found a similar closed issue regarding the "Credentials validation failed with status code 402" error when setting up DeepSeek in Dify version 0.15.3 on a cloud environment. The suggested solution involves ensuring that the credentials are correct and valid. Here are some steps to troubleshoot and resolve the issue: 1. **Check Credentials Format**: Ensure that the credentials dictionary is correctly formatted and contains all necessary fields. For DeepSeek, the required field is `api_key`, and there is an optional `endpoint_url` field for a custom API endpoint URL. 2. **Verify Credentials**: Make sure the `api_key` is up-to-date and has the necessary permissions for accessing the DeepSeek service. 3. **Default Endpoint URL**: If you are using a custom `endpoint_url`, verify that it is correct. The default value is `"https://api.deepseek.com"`. If the credentials are correct and the error persists, you may need to check with the service provider to ensure there are no issues with the account or service status <sup>[[1]](https://github.com/langgenius/dify/issues/13515)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/90898321-14fc-4ed3-af8d-799e6cb9757f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/90898321-14fc-4ed3-af8d-799e6cb9757f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/90898321-14fc-4ed3-af8d-799e6cb9757f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/90898321-14fc-4ed3-af8d-799e6cb9757f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/90898321-14fc-4ed3-af8d-799e6cb9757f?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/90898321-14fc-4ed3-af8d-799e6cb9757f?feedback_type=other)</sup>
yindo commented 2026-02-21 18:24:15 -05:00
Author
Owner
Copy Link
Copy Source

@gyzuike commented on GitHub (Mar 25, 2025):

402是余额不足，给deepseek充点钱就行，1块起充

@gyzuike commented on GitHub (Mar 25, 2025): 402是余额不足，给deepseek充点钱就行，1块起充
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
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#8155
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?