mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
404 NOT_FOUND for Gemini embedding models. #954
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 @MrunalSinagde on GitHub (Jan 28, 2026).
Self Checks
Dify version
1.7.2
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Error appears for models such as:
embedding-001gemini-embedding-exp-03-07text-embedding-004Even though:
Steps to Reproduce
404 NOT_FOUND: Model not found✔️ Expected Behavior
The embedding should be carried out without any errors
❌ Actual Behavior
Error:
404 NOT_FOUND, message: 'Model is not found: models/model name'
@dosubot[bot] commented on GitHub (Jan 28, 2026):
This 404 error is a known issue and is almost always caused by changes on the provider/plugin side—specifically, Google deprecating or renaming Gemini model IDs, or requiring the API version to be set to
v1instead ofv1betadiscussion issue. Dify fetches the list of supported Gemini models dynamically from the plugin daemon, so if Google or the plugin updates the available models, old names likeembedding-001orgemini-embedding-exp-03-07will suddenly return 404s.How to fix:
gemini-1.5-pro,gemini-1.5-flash,gemini-2.0-flash, ortext-embedding-004. Avoid deprecated names likegemini-proorembedding-001discussion.v1: In your Docker.envor environment, make sureGOOGLE_API_VERSION=v1(notv1beta) discussion.If you still get 404 errors after these steps, double-check that your Google Cloud project has the Generative AI API enabled, billing is active, and your API key has access to the models you want to use discussion.
For more details and troubleshooting, see the related issue and discussion.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@dosubot[bot] commented on GitHub (Jan 28, 2026):
The 404 NOT_FOUND error for Gemini embedding models like
embedding-001,gemini-embedding-exp-03-07, andtext-embedding-004is happening because these models have likely been retired or are no longer supported by the Google Gemini backend. This is a systemic issue affecting multiple users and is not related to your API key, billing, or Dify configuration changes. The plugin and Dify core dynamically pass the model name to the backend, so if the backend no longer recognizes the model, you'll get this error—even if the model is still listed in plugin config files [source].To resolve this, switch to a currently supported Gemini model. You can check which models your API key supports by running:
For embedding tasks, consider using models like
gemini-1.5-pro,gemini-1.5-flash, orgemini-2.0-flashif they appear in your available models list. Make sure your Dify and Gemini plugin versions are up to date, and update your model configuration to use one of these supported models [source].If you specifically need Gemini text embeddings, note that Dify currently only supports Gemini LLM models and not the Gemini Text Embeddings API (which includes the models you listed). Support for Gemini embedding models may be added in the future, so keep an eye on plugin updates and changelogs [source].
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@HideenHuang commented on GitHub (Jan 28, 2026):
those model has been deprecated.
https://www.reddit.com/r/RooCode/comments/1pdcx4k/google_is_deprecating_the_textembedding004/
@xuanmit1001 commented on GitHub (Jan 28, 2026):
I recently transitioned from using Gemini’s text-embedding-004 model to the Nomic‑embed‑text model provided by Ollama. This change completely resolved the issues I had been encountering, and my system has been running smoothly ever since.
If you are still experiencing similar problems, I recommend installing Ollama and integrating it with your application. This adjustment may help you resolve the issue as well.
@crazywoola commented on GitHub (Feb 3, 2026):
Hi @MrunalSinagde, thanks for opening this issue.
Why this is being closed
Dify issue tracking requires English-only issue title and description for consistent collaboration.
Next steps
Please open a new issue in English and include clear details so maintainers can help efficiently.
Thanks for understanding and for your support.