[Bug] gemini-1.5-pro-latest模型使用不了

[xxbsxy]

📦 部署方式

Docker

📌 软件版本

v2.15.3

💻 系统环境

Other Linux

📌 系统版本

Debian 12

🌐 浏览器

Chrome

📌 浏览器版本

129.0.6668.59

🐛 问题描述

[gemini-1.5-pro-latest调用不了 配置的是vercel的代理地址 但是使用LobeChat可以调用 看了控制台好像是key传递的方式不一样

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[Issues-translate-bot]

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

---

Title: [Bug] gemini-1.5-pro-latest model cannot be used

📦 Deployment method

Docker

📌 Software version

v2.15.3

💻 System environment

Other Linux

📌 System version

Debian 12

🌐 Browser

Chrome

📌 Browser version

129.0.6668.59

🐛 Problem description

[gemini-1.5-pro-latest cannot be called. The proxy address of vercel is configured. However, it can be called using LobeChat. After looking at the console, it seems that the key transfer method is different.

📷 Steps to reproduce

No response

🚦 Expected results

No response

📝 Supplementary information

No response

[toniexly]

mistral的也调用不了，好象是因为不支持penalty参数。。

[Issues-translate-bot]

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

---

Mistral cannot be called either, it seems because the penalty parameter is not supported. .

[xxbsxy]

在客户端可以但是在浏览器端不行

[Issues-translate-bot]

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

---

It works on the client side but not on the browser side.

[mountainguan]

the same

[dupl]

📦 部署方式

Docker

📌 软件版本

v2.15.3

💻 系统环境

Other Linux

📌 系统版本

Debian 12

🌐 浏览器

Chrome

📌 浏览器版本

129.0.6668.59

🐛 问题描述

[gemini-1.5-pro-latest调用不了 配置的是vercel的代理地址 但是使用LobeChat可以调用 看了控制台好像是key传递的方式不一样

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

Gemini无法用的bug咋还不修复�，急的我又部署了lobe🐱

[Issues-translate-bot]

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

---

📦 Deployment method

Docker

📌 Software version

v2.15.3

💻 System environment

Other Linux

📌 System version

Debian 12

🌐 Browser

Chrome

📌 Browser version

129.0.6668.59

🐛 Problem description

[gemini-1.5-pro-latest cannot be called. The configuration is the proxy address of vercel, but it can be called using LobeChat. Looking at the console, it seems that the way of key transfer is different! [Snipaste_2024-09-26_15-59-04](https: //private-user-images.githubusercontent.com/88436533/371041262-53c6e762-81b2-4050-9e33-d561dec6b5e7.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..SwiLeqoWr_D_0Lks Jb5OA8AaiH4iTo0v4abALw4Zqgk) 

📷 Steps to reproduce

No response

🚦 Expected results

No response

📝 Supplementary information

No response

The bug that Gemini cannot be used has not been fixed yet. I was anxious and deployed lobe again🐱

[lloydzhou]

#5541 这个pr应该已经处理了google的api发送api key的方式。已经合并到main分支，只是没有发新版。
如果使用vercel部署，可以直接更新。
docker版本，需要等发新版的时候才会有新的docker镜像

[Issues-translate-bot]

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

---

#5541 This PR should have dealt with the way Google’s API sends API keys. It has been merged into the main branch, but a new version has not been released.
If you use vercel deployment, you can update directly.
docker version, you need to wait until a new version is released before there will be a new docker image

[mountainguan]

#5541 这个pr应该已经处理了google的api发送api key的方式。已经合并到main分支，只是没有发新版。 如果使用vercel部署，可以直接更新。 docker版本，需要等发新版的时候才会有新的docker镜像

目前测试并不行

[Issues-translate-bot]

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

---

#5541 This PR should have dealt with the way Google's API sends API keys. It has been merged into the main branch, but a new version has not been released. If you use vercel deployment, you can update directly. docker version, you need to wait until a new version is released before there will be a new docker image

Testing is currently not possible

[mountainguan]

📦 部署方式

Docker

📌 软件版本

v2.15.3

💻 系统环境

Other Linux

📌 系统版本

Debian 12

🌐 浏览器

Chrome

📌 浏览器版本

129.0.6668.59

🐛 问题描述

[gemini-1.5-pro-latest调用不了 配置的是vercel的代理地址 但是使用LobeChat可以调用 看了控制台好像是key传递的方式不一样

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

Gemini无法用的bug咋还不修复�，急的我又部署了lobe🐱

我怀疑他们没有对gemini的api进行测试....出过几次异常主维护者都自己测不出来

[Issues-translate-bot]

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

---

📦 Deployment method

Docker

📌 Software version

v2.15.3

💻 System environment

Other Linux

📌 System version

Debian 12

🌐 Browser

Chrome

📌 Browser version

129.0.6668.59

🐛 Problem description

[gemini-1.5-pro-latest cannot call the configured vercel proxy address, but it can be called using LobeChat. Looking at the console, it seems that the key transfer method is different! [Snipaste_2024-09-26_15-59-04](https ://private-user-images.githubusercontent.com/88436533/371041262-53c6e762-81b2-4050-9e33-d561dec6b5e7.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..SwiLeqoWr_D_0 LksJb5OA8AaiH4iTo0v4abALw4Zqgk) 

📷 Steps to reproduce

No response

🚦 Expected results

No response

📝 Supplementary information

No response

The bug that Gemini cannot be used has not been fixed yet. I was anxious and deployed lobe again🐱

I suspect they didn't test gemini's api... There were several exceptions and the main maintainer couldn't detect it himself.

[dupl]

#5541 这个pr应该已经处理了google的api发送api key的方式。已经合并到main分支，只是没有发新版。
如果使用vercel部署，可以直接更新。
docker版本，需要等发新版的时候才会有新的docker镜像

用的最新commit版，vercel部署，依然无法使用Gemini😭

[Issues-translate-bot]

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

---

#5541 This PR should have dealt with the way Google's API sends API keys. It has been merged into the main branch, but a new version has not been released.
If you use vercel deployment, you can update directly.
Docker version, you need to wait until a new version is released before there will be a new docker image

I used the latest commit version and deployed it with vercel, but I still can’t use Gemini😭

[lloydzhou]

我怀疑他们没有对gemini的api进行测试....出过几次异常主维护者都自己测不出来

1. 刚刚在app.nextchat.dev这个线上环境测试了，gemini-1.5-pro-latest正常工作

2. 刚刚使用yidadaa/chatgpt-next-web:v2.15.3本地启动一个新的容器测试了，gemini-1.5-pro-latest正常工作

3. 刚才使用最新的main分支测试了一下，确实有问题，在hotfix for x-goog-api-key #5562 进行修复：
   a. 修复传递头的名称 x-google-api-key --> x-goog-api-key
   b. 修复传递alt=sse参数导致可能出现404错误

[Issues-translate-bot]

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

---

I suspect they didn’t test gemini’s api.... There have been several exceptions and the main maintainer couldn’t detect it himself.

1. Just tested it in the online environment of app.nextchat.dev, gemini-1.5-pro-latest works normally

2. I just used yidadaa/chatgpt-next-web:v2.15.3 to start a new container locally for testing. gemini-1.5-pro-latest works normally.

3. I just tested it using the latest main branch. There is indeed a problem. It will be fixed in hotfix for x-goog-api-key #5562:
   a. Fix the name of the passed header x-google-api-key --> x-goog-api-key
   b. Fix the possible 404 error caused by passing the alt=sse parameter

[dupl]

喜大普奔，终于修复了🙂

[Issues-translate-bot]

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

---

Hi, it’s finally fixed 🙂