mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
GroqCloud plugin request error #653
Reference in New Issue
Block a user
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?
Originally created by @Mgrsc on GitHub (Sep 16, 2025).
Self Checks
Dify version
v1.8.1
Plugin version
0.0.11
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.
grok model list:
allam-2-7b,deepseek-r1-distill-llama-70b,gemma2-9b-it,groq/compound,groq/compound-mini,llama-3.1-8b-instant,llama-3.3-70b-versatile,meta-llama/llama-4-maverick-17b-128e-instruct,meta-llama/llama-4-scout-17b-16e-instruct,meta-llama/llama-guard-4-12b,meta-llama/llama-prompt-guard-2-22m,meta-llama/llama-prompt-guard-2-86m,moonshotai/kimi-k2-instruct,moonshotai/kimi-k2-instruct-0905,openai/gpt-oss-120b,openai/gpt-oss-20b,playai-tts,playai-tts-arabic,qwen/qwen3-32b,whisper-large-v3,whisper-large-v3-turbo
Error in model settings in the code
✔️ Error log
Error:
@dosubot[bot] commented on GitHub (Sep 16, 2025):
The error happens because
grok-code-fast-1-0825is 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 of the x.ai Grok models, so trying to add one to the GroqCloud provider will always return a 404 "model not found" error. Only the models explicitly listed for GroqCloud in the Dify UI or plugin are supported.To use x.ai Grok models like
grok-code-fast-1-0825, you need to configure the x.ai/Grok provider, not GroqCloud. If you want to use GroqCloud, select from its supported models (such asallam-2-7b,groq/compound,llama-3.1-8b-instant, etc.)—these are the only ones that will validate and work with the GroqCloud plugin.If you are still seeing issues with valid GroqCloud models, make sure your Dify and dify-official-plugins are up to date, and check that your database migrations are complete, especially if you recently upgraded or are running in an offline Docker setup. Credential validation failures with 404 errors almost always mean the model is not available for the selected provider, or the provider/model linkage is broken in the backend (details, details, details).
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
