Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] 更新到 2.14.1 之后 Gemini Free Tier 无法使用 #5255

Closed
Dakai opened this issue Aug 12, 2024 · 5 comments
Closed

[Bug] 更新到 2.14.1 之后 Gemini Free Tier 无法使用 #5255

Dakai opened this issue Aug 12, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@Dakai
Copy link
Contributor

Dakai commented Aug 12, 2024

📦 部署方式

Vercel

📌 软件版本

2.14.1

💻 系统环境

Other Linux

📌 系统版本

Linux 6.10.3-1

🌐 浏览器

Other

📌 浏览器版本

Version 1.68.128 Chromium: 127.0.6533.73 (Official Build) (64-bit)

🐛 问题描述

从 2.14.0 升级到 2.14.1 之后 Gemini-1.5-pro-latest 和 Gemini-1.5-flash-latest 这两个模型都无法使用,提示回复说:

{
  "error": {
    "code": 400,
    "message": "Gemini API free tier is not available in your country. Please enable billing on your project in Google AI Studio.",
    "status": "FAILED_PRECONDITION"
  }
}

Vercel 的 Function Region 地点都选择了北美地区。
Rollback 回 2.14.0 恢复正常

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

@Dakai Dakai added the bug Something isn't working label Aug 12, 2024
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Title: [Bug] Gemini Free Tier cannot be used after updating to 2.14.1

@mountainguan
Copy link

我也是,而且我自己加了一个worker代理地址,然后这个地址通过linux的curl调用非常正常,填进去配置里以后,就是间歇性抽风,也不是百分百不行,时不时可以,又时不时跟你一样的提示

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Me too, and I added a worker proxy address myself, and then calling this address through curl in Linux is very normal. After filling it in the configuration, I have intermittent convulsions, which is not 100% impossible. It works from time to time, and sometimes it is the same as yours. tips

@mountainguan
Copy link

上个图,圈住的两个请求,请求内容一致,一个一请求就400,另一个是正常200。这个异常时发生在请求应用路由阶段,后续的Fetch URL的逻辑也正常运行,但是400出来过后,就跟题主的内容一样,提示异常。这个应用时部署在vercel上的,gemini做了一个worker的简单代理,就是直接转发。在旧版本中,请求是直接发生在浏览器这边,没有出现过这种异常,现在请求需要从vercel这边对worker代理进行触发,就会间歇性抽风
image

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


In the picture above, the two requests circled have the same request content. One request is 400, and the other is 200 normally. This exception occurred during the request application routing phase, and the subsequent Fetch URL logic also ran normally, but after the 400 came out, it was the same as the content of the subject, and an exception was prompted. This application is deployed on vercel. Gemini makes a simple proxy for workers, which is forwarding directly. In the old version, the request occurred directly on the browser side, and no such exception occurred. Now the request needs to be triggered from the vercel side to the worker agent, which will cause intermittent convulsions.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants