Unable to add Gemini token #255

Closed
opened 2026-02-16 10:18:36 -05:00 by yindo · 2 comments
Owner

Originally created by @Jerry-0202 on GitHub (May 6, 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

1.3.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When adding the Gemini API, clicking the save button prompts the following message:
"404 models/gemini-pro is not found for API version v1beta, or is not supported for generateContent. Call ListModels to see the list of available models and their supported methods."

Throughout the process, I can ensure the correctness of the API key.

✔️ Expected Behavior

Correct preservation.

Actual Behavior

Error message

Originally created by @Jerry-0202 on GitHub (May 6, 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 1.3.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When adding the Gemini API, clicking the save button prompts the following message: "404 models/gemini-pro is not found for API version v1beta, or is not supported for generateContent. Call ListModels to see the list of available models and their supported methods." Throughout the process, I can ensure the correctness of the API key. ### ✔️ Expected Behavior Correct preservation. ### ❌ Actual Behavior Error message
yindo closed this issue 2026-02-16 10:18:36 -05:00
Author
Owner

@QIN2DIM commented on GitHub (May 6, 2025):

@Jerry-0202 hi, What is the version of the GEMINI plugin you are using?

@QIN2DIM commented on GitHub (May 6, 2025): @Jerry-0202 hi, What is the version of the GEMINI plugin you are using?
Author
Owner

@Jerry-0202 commented on GitHub (May 7, 2025):

A somewhat amusing situation occurred. I followed the official tutorial to execute a local deployment and found that the version I opened was Version 0.15.3.

https://docs.dify.ai/en/getting-started/install-self-hosted/docker-compose

Then I realized that the documentation provided this:

Clone Dify
Clone the Dify source code to your local machine:

# Assuming current latest version is 0.15.3
git clone https://github.com/langgenius/dify.git --branch 0.15.3

So when you mentioned the concept of plugins, I realized it might be a version issue. By default, I assumed the version I downloaded yesterday was the latest. Then I used the update commands:

cd dify/docker
docker compose down
git pull origin main
docker compose pull
docker compose up -d

After testing the API again, I found it was working normally. Thanks for reminding me about using plugins.
Everything boiled down to a version problem.

@Jerry-0202 commented on GitHub (May 7, 2025): A somewhat amusing situation occurred. I followed the official tutorial to execute a local deployment and found that the version I opened was Version 0.15.3. https://docs.dify.ai/en/getting-started/install-self-hosted/docker-compose Then I realized that the documentation provided this: Clone Dify Clone the Dify source code to your local machine: ```bash # Assuming current latest version is 0.15.3 git clone https://github.com/langgenius/dify.git --branch 0.15.3 ``` So when you mentioned the concept of plugins, I realized it might be a version issue. By default, I assumed the version I downloaded yesterday was the latest. Then I used the update commands: ```bash cd dify/docker docker compose down git pull origin main docker compose pull docker compose up -d ``` After testing the API again, I found it was working normally. Thanks for reminding me about using plugins. Everything boiled down to a version problem.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#255