langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

GroqCloud plugin request error #652

New Issue
Closed
opened 2026-02-16 10:20:04 -05:00 by yindo · 7 comments
yindo commented 2026-02-16 10:20:04 -05:00
Owner
Copy Link
Copy Source

Originally created by @Mgrsc on GitHub (Sep 16, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

v1.8.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Configured the GroqCloud model provider, but the requested model was actually x.ai's grok-code-fast-1-0825.
Error:

Credentials validation failed with status code 404 and response body {"error":{"message":"The model `grok-code-fast-1-0825` does not exist or you do not have access to it.","type":"invalid_request_error","code":"model_not_found"}}
Image

✔️ Expected Behavior

Models owned by the Groq model provider should be requested.

❌ Actual Behavior

Configured the GroqCloud model provider, but the requested model was actually x.ai's grok-code-fast-1-0825.

Originally created by @Mgrsc on GitHub (Sep 16, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version v1.8.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Configured the GroqCloud model provider, but the requested model was actually x.ai's grok-code-fast-1-0825. Error: ``` Credentials validation failed with status code 404 and response body {"error":{"message":"The model `grok-code-fast-1-0825` does not exist or you do not have access to it.","type":"invalid_request_error","code":"model_not_found"}} ``` <img width="983" height="816" alt="Image" src="https://github.com/user-attachments/assets/48b76b6b-6a24-46bc-96f7-ba194cbf0886" /> ### ✔️ Expected Behavior Models owned by the Groq model provider should be requested. ### ❌ Actual Behavior Configured the GroqCloud model provider, but the requested model was actually x.ai's grok-code-fast-1-0825.
yindo added the good first issuebug labels 2026-02-16 10:20:04 -05:00
yindo closed this issue 2026-02-16 10:20:04 -05:00
yindo commented 2026-02-16 10:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 16, 2025):

Dify strictly enforces model-provider mapping: only models explicitly declared in the GroqCloud plugin manifest can be used with the GroqCloud provider. If you try to request a model that isn't registered under GroqCloud (like an x.ai model), you'll always get a model_not_found error—there's no fallback or cross-provider mapping by design.

To resolve this, make sure your dify-official-plugins and GroqCloud plugin are fully up to date, as recent updates add/remove supported models and fix validation logic. In your Dify admin UI, check that only GroqCloud-supported models are selectable for the GroqCloud provider. If you still see the error after updating, restart both the plugin_daemon and Dify containers to clear any stale state or cache. If you need to add or remove models for GroqCloud, update the plugin manifest/YAML files and restart the plugin_daemon.

If you’re running into persistent 404 errors during credential validation, double-check your Docker proxy (Squid) config and logs, as network/proxy misconfiguration can also block model validation requests in self-hosted setups (reference). For plugin or model deprecation issues, updating to the latest plugin version or patching the model name in the plugin code is required (reference).

There is no mechanism in Dify to request x.ai models from GroqCloud or vice versa—each provider is isolated and only supports its own declared models (reference).

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 16, 2025): <!-- Answer --> Dify strictly enforces model-provider mapping: only models explicitly declared in the GroqCloud plugin manifest can be used with the GroqCloud provider. If you try to request a model that isn't registered under GroqCloud (like an x.ai model), you'll always get a `model_not_found` error—there's no fallback or cross-provider mapping by design. To resolve this, make sure your dify-official-plugins and GroqCloud plugin are fully up to date, as recent updates add/remove supported models and fix validation logic. In your Dify admin UI, check that only GroqCloud-supported models are selectable for the GroqCloud provider. If you still see the error after updating, restart both the plugin_daemon and Dify containers to clear any stale state or cache. If you need to add or remove models for GroqCloud, update the plugin manifest/YAML files and restart the plugin_daemon. If you’re running into persistent 404 errors during credential validation, double-check your Docker proxy (Squid) config and logs, as network/proxy misconfiguration can also block model validation requests in self-hosted setups ([reference](https://github.com/langgenius/dify-official-plugins/issues/1259)). For plugin or model deprecation issues, updating to the latest plugin version or patching the model name in the plugin code is required ([reference](https://github.com/langgenius/dify/issues/25524)). There is no mechanism in Dify to request x.ai models from GroqCloud or vice versa—each provider is isolated and only supports its own declared models ([reference](https://github.com/langgenius/dify/blob/b5a7e64e19ef1f1cac7ac6467a4df6bdd3e42d59/api/core/model_runtime/model_providers/model_provider_factory.py)). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/c166e957-7687-4939-9d47-c84ad07ac9b8?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c166e957-7687-4939-9d47-c84ad07ac9b8?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c166e957-7687-4939-9d47-c84ad07ac9b8?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c166e957-7687-4939-9d47-c84ad07ac9b8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c166e957-7687-4939-9d47-c84ad07ac9b8?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c166e957-7687-4939-9d47-c84ad07ac9b8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c166e957-7687-4939-9d47-c84ad07ac9b8?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/25786)
yindo commented 2026-02-16 10:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 16, 2025):

The error happens because grok-code-fast-1-0825 is an x.ai Grok model, not a GroqCloud model—GroqCloud and x.ai are separate providers with different model lists. GroqCloud does not support any x.ai Grok models, so trying to add or request one from the GroqCloud provider will always return a 404 "model not found" error. Only models explicitly listed for GroqCloud in the Dify UI or plugin (like allam-2-7b, groq/compound, llama-3.1-8b-instant, etc.) will work with the GroqCloud plugin. To use x.ai Grok models, you need to configure the x.ai/Grok provider instead of GroqCloud. If you see x.ai models under GroqCloud, it's likely a configuration or data issue, not a code bug—make sure only Groq models are selectable for GroqCloud in your provider/model lists and database. More details here: source.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 16, 2025): <!-- Answer --> The error happens because `grok-code-fast-1-0825` is an x.ai Grok model, not a GroqCloud model—GroqCloud and x.ai are separate providers with different model lists. GroqCloud does not support any x.ai Grok models, so trying to add or request one from the GroqCloud provider will always return a 404 "model not found" error. Only models explicitly listed for GroqCloud in the Dify UI or plugin (like `allam-2-7b`, `groq/compound`, `llama-3.1-8b-instant`, etc.) will work with the GroqCloud plugin. To use x.ai Grok models, you need to configure the x.ai/Grok provider instead of GroqCloud. If you see x.ai models under GroqCloud, it's likely a configuration or data issue, not a code bug—make sure only Groq models are selectable for GroqCloud in your provider/model lists and database. More details here: [source](https://github.com/langgenius/dify-official-plugins/issues/1722). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/778a3eeb-57c9-40c9-9617-f65cfabaf3e1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/778a3eeb-57c9-40c9-9617-f65cfabaf3e1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/778a3eeb-57c9-40c9-9617-f65cfabaf3e1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/778a3eeb-57c9-40c9-9617-f65cfabaf3e1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/778a3eeb-57c9-40c9-9617-f65cfabaf3e1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/778a3eeb-57c9-40c9-9617-f65cfabaf3e1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/778a3eeb-57c9-40c9-9617-f65cfabaf3e1?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1723)
yindo commented 2026-02-16 10:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@npgfg commented on GitHub (Oct 6, 2025):

Hi, exact same issue here just when i try to save my Groq API Key. Any plans on a fix?

Image
@npgfg commented on GitHub (Oct 6, 2025): Hi, exact same issue here just when i try to save my Groq API Key. Any plans on a fix? <img width="418" height="187" alt="Image" src="https://github.com/user-attachments/assets/2a210d5b-1748-4255-a7d2-bf5340c3d180" />
yindo commented 2026-02-16 10:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 22, 2025):

Hi, @Mgrsc. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that configuring the GroqCloud provider in Dify v1.8.1 led to requests for an x.ai Grok model, causing 404 errors.
  • The root cause was that GroqCloud does not support x.ai models, and Dify enforces strict provider-model mappings.
  • It was clarified that x.ai models must be requested via the x.ai provider, not GroqCloud.
  • Another user experienced a similar issue related to API key saving, indicating a configuration or data error rather than a code bug.
  • The issue was resolved by ensuring correct provider-model usage according to Dify's rules.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of dify-official-plugins; if so, you can keep the discussion open by commenting here.
  • Otherwise, I will automatically close this issue in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 22, 2025): Hi, @Mgrsc. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that configuring the GroqCloud provider in Dify v1.8.1 led to requests for an x.ai Grok model, causing 404 errors. - The root cause was that GroqCloud does not support x.ai models, and Dify enforces strict provider-model mappings. - It was clarified that x.ai models must be requested via the x.ai provider, not GroqCloud. - Another user experienced a similar issue related to API key saving, indicating a configuration or data error rather than a code bug. - The issue was resolved by ensuring correct provider-model usage according to Dify's rules. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of dify-official-plugins; if so, you can keep the discussion open by commenting here. - Otherwise, I will automatically close this issue in 5 days. Thank you for your understanding and contribution!
yindo commented 2026-02-16 10:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@syedkhalid0 commented on GitHub (Oct 22, 2025):

The problem is you are not understanding.

We are not trying to call grok-code-fast-1-0825 via GroqCloud, and we do know it's an x.ai model.

We are trying to CONFIGURE the GroqCloud Model Provider. After installing GroqCloud as provider, when we try to configure it by adding an API KEY, it's throwing an error:

Credentials validation failed with status code 404 and response body {"error":{"message":"The model `grok-code-fast-1-0825` does not exist or you do not have access to it.","type":"invalid_request_error","code":"model_not_found"}}

Hence, the GroqCloud extension/plugin is calling the model while saving the API KEY.

Additionally we can clearly see on Groq's Logs (Dashboard > Logs) that Dify is trying to call a model on Groq that is not supported:

{
  "request_id": "req_01k87a4ztnfe6s1zs7y54pzpmg",
  "created_at": "2025-10-23T01:15:21.813Z",
  "error": {
    "message": "The model `grok-code-fast-1-0825` does not exist or you do not have access to it.",
    "type": "invalid_request_error",
    "param": "",
    "code": "model_not_found"
  }
}

Steps to recreate this error on Dify Cloud:

  1. Go-to: Settings -> Model Provider (under workspace)
  2. Install GroqCloud (if not already installed)
  3. Under the installed provider, GroqCloud -> Setup.
  4. Add the Groq API KEY, and click save.
  5. Congratulations, your eyes can finally see the exact same error message.

Try to understand the problem first before drawing any conclusion.

@syedkhalid0 commented on GitHub (Oct 22, 2025): ### The problem is you are not understanding. We are not trying to call `grok-code-fast-1-0825` via `GroqCloud`, and we do know it's an x.ai model. We are trying to **CONFIGURE** the *GroqCloud* Model Provider. After installing GroqCloud as provider, when we try to configure it by adding an **API KEY**, it's throwing an error: ``` Credentials validation failed with status code 404 and response body {"error":{"message":"The model `grok-code-fast-1-0825` does not exist or you do not have access to it.","type":"invalid_request_error","code":"model_not_found"}} ``` *Hence, the GroqCloud extension/plugin is calling the model while saving the API KEY.* Additionally we can clearly see on Groq's Logs *(Dashboard > Logs)* that Dify is trying to call a model on Groq that is not supported: ```json { "request_id": "req_01k87a4ztnfe6s1zs7y54pzpmg", "created_at": "2025-10-23T01:15:21.813Z", "error": { "message": "The model `grok-code-fast-1-0825` does not exist or you do not have access to it.", "type": "invalid_request_error", "param": "", "code": "model_not_found" } } ``` Steps to recreate this error on Dify Cloud: 1. Go-to: Settings -> Model Provider *(under workspace)* 2. Install `GroqCloud` *(if not already installed)* 3. Under the installed provider, GroqCloud -> Setup. 4. Add the Groq API KEY, and click save. 5. Congratulations, your eyes can finally see the exact same error message. > Try to understand the problem first before drawing any conclusion.
yindo commented 2026-02-16 10:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@syedkhalid0 commented on GitHub (Oct 22, 2025):

I found the problem.

on file models/groq/provider/groq.py

class GroqProvider(ModelProvider):
    def validate_provider_credentials(self, credentials: dict) -> None:
        """
        Validate provider credentials
        if validate failed, raise exception

        :param credentials: provider credentials, credentials form defined in `provider_credential_schema`.
        """
        try:
            model_instance = self.get_model_instance(ModelType.LLM)
            model_instance.validate_credentials(model="grok-code-fast-1-0825", credentials=credentials)   # <--- HERE YOU CAN SEE THE PLUGIN IS CALLING WRING MODEL.
        except CredentialsValidateFailedError as ex:
            raise ex
        except Exception as ex:
            logger.exception(f"{self.get_provider_schema().provider} credentials validate failed")
            raise ex

if you want, I can fix and open a PR. Do let me know.

@syedkhalid0 commented on GitHub (Oct 22, 2025): ### I found the problem. on file [models/groq/provider/groq.py](https://github.com/langgenius/dify-official-plugins/blob/main/models/groq/provider/groq.py) ```python class GroqProvider(ModelProvider): def validate_provider_credentials(self, credentials: dict) -> None: """ Validate provider credentials if validate failed, raise exception :param credentials: provider credentials, credentials form defined in `provider_credential_schema`. """ try: model_instance = self.get_model_instance(ModelType.LLM) model_instance.validate_credentials(model="grok-code-fast-1-0825", credentials=credentials) # <--- HERE YOU CAN SEE THE PLUGIN IS CALLING WRING MODEL. except CredentialsValidateFailedError as ex: raise ex except Exception as ex: logger.exception(f"{self.get_provider_schema().provider} credentials validate failed") raise ex ``` > if you want, I can fix and open a PR. Do let me know.
yindo commented 2026-02-16 10:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 8, 2025):

Hi, @Mgrsc. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a 404 error when configuring the GroqCloud provider in Dify v1.8.1 due to an unsupported x.ai Grok model being requested.
  • The error is caused by strict provider-model mappings in Dify, which prevent GroqCloud from accessing x.ai models.
  • Another user identified that the GroqCloud plugin's credential validation incorrectly calls the x.ai model during API key setup.
  • A potential fix has been offered but the issue remains unresolved and open for confirmation or patch.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If no further updates are provided, I will automatically close this issue in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Nov 8, 2025): Hi, @Mgrsc. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a 404 error when configuring the GroqCloud provider in Dify v1.8.1 due to an unsupported x.ai Grok model being requested. - The error is caused by strict provider-model mappings in Dify, which prevent GroqCloud from accessing x.ai models. - Another user identified that the GroqCloud plugin's credential validation incorrectly calls the x.ai model during API key setup. - A potential fix has been offered but the issue remains unresolved and open for confirmation or patch. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If no further updates are provided, I will automatically close this issue in 5 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug good first issue
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-official-plugins#652
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?