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

Failed to save Groq ApiKey , Credentials validation failed with status code 404 #8419

New Issue
Closed
opened 2026-02-21 18:25:37 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:25:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @yaoshengting on GitHub (Feb 19, 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

Add GroqCloud key in model providers.

✔️ Expected Behavior

Save successfully.

❌ Actual Behavior

Credentials validation failed with status code 404

Originally created by @yaoshengting on GitHub (Feb 19, 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 Add GroqCloud key in model providers. ### ✔️ Expected Behavior Save successfully. ### ❌ Actual Behavior Credentials validation failed with status code 404
yindo added the 🐞 bug label 2026-02-21 18:25:37 -05:00
yindo closed this issue 2026-02-21 18:25:37 -05:00
yindo commented 2026-02-21 18:25:37 -05:00
Author
Owner
Copy Link
Copy Source

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

Hello @yaoshengting! I'm here to help you with any bugs, questions, or contributions you have for the project. Let me know how I can assist you!

I found a similar closed issue titled "Failed to save Groq Cloud Key in model providers" which was resolved by a pull request that fixed the credentials validation for GroqCloud [1]. The "Credentials validation failed with status code 404" error typically indicates that the endpoint URL is incorrect or the endpoint does not exist. To resolve this, ensure that the endpoint_url is correct and accessible, and that the endpoint paths (chat/completions, completions, or embeddings) are valid for the given mode [2].

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 19, 2025): <!-- Greeting --> Hello @yaoshengting! I'm here to help you with any bugs, questions, or contributions you have for the project. Let me know how I can assist you! <!-- Answer --> I found a similar closed issue titled "Failed to save Groq Cloud Key in model providers" which was resolved by a pull request that fixed the credentials validation for GroqCloud <sup>[[1]](https://github.com/langgenius/dify/issues/3811)</sup>. The "Credentials validation failed with status code 404" error typically indicates that the endpoint URL is incorrect or the endpoint does not exist. To resolve this, ensure that the `endpoint_url` is correct and accessible, and that the endpoint paths (`chat/completions`, `completions`, or `embeddings`) are valid for the given mode <sup>[[2]](https://github.com/langgenius/dify/issues/6027)</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/a86b433b-24ff-4e46-b65b-725b5343b53f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/a86b433b-24ff-4e46-b65b-725b5343b53f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/a86b433b-24ff-4e46-b65b-725b5343b53f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/a86b433b-24ff-4e46-b65b-725b5343b53f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a86b433b-24ff-4e46-b65b-725b5343b53f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/a86b433b-24ff-4e46-b65b-725b5343b53f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a86b433b-24ff-4e46-b65b-725b5343b53f?feedback_type=other)</sup>
yindo commented 2026-02-21 18:25:37 -05:00
Author
Owner
Copy Link
Copy Source

@yaoshengting commented on GitHub (Feb 19, 2025):

@dosu , Where can I check the endpoint paths, it just asks me to enter the api key

Image

@yaoshengting commented on GitHub (Feb 19, 2025): @dosu , Where can I check the endpoint paths, it just asks me to enter the api key ![Image](https://github.com/user-attachments/assets/db7f654c-ef61-4177-aadb-161154c08626)
yindo commented 2026-02-21 18:25:37 -05:00
Author
Owner
Copy Link
Copy Source

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

The specific endpoint paths for GroqCloud API integration in Dify are not directly available in the documentation or codebase that I have access to. However, the error message you encountered suggests that the endpoint URL might be incorrect or inaccessible. Typically, endpoint paths for APIs like GroqCloud might include paths such as /chat/completions, /completions, or /embeddings based on the functionality you are trying to access.

To resolve the issue, you should verify the endpoint URL you are using and ensure it matches the expected paths for GroqCloud. If you have access to GroqCloud's API documentation, it would be beneficial to check there for the correct endpoint paths. Additionally, ensure that your network settings allow access to these endpoints.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 19, 2025): <!-- Answer --> The specific endpoint paths for GroqCloud API integration in Dify are not directly available in the documentation or codebase that I have access to. However, the error message you encountered suggests that the endpoint URL might be incorrect or inaccessible. Typically, endpoint paths for APIs like GroqCloud might include paths such as `/chat/completions`, `/completions`, or `/embeddings` based on the functionality you are trying to access. To resolve the issue, you should verify the endpoint URL you are using and ensure it matches the expected paths for GroqCloud. If you have access to GroqCloud's API documentation, it would be beneficial to check there for the correct endpoint paths. Additionally, ensure that your network settings allow access to these endpoints. <!-- 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/51910d5d-90b0-4daa-a16a-39e3b12e92cc?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/51910d5d-90b0-4daa-a16a-39e3b12e92cc?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/51910d5d-90b0-4daa-a16a-39e3b12e92cc?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/51910d5d-90b0-4daa-a16a-39e3b12e92cc?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/51910d5d-90b0-4daa-a16a-39e3b12e92cc?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/51910d5d-90b0-4daa-a16a-39e3b12e92cc?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/51910d5d-90b0-4daa-a16a-39e3b12e92cc?feedback_type=other)</sup>
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 🐞 bug
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#8419
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?