[Bug] 点击“连通性检查”，导致 api key、api url 丢失

[cloverzrg]

📦 部署环境

Docker

📦 部署模式

服务端模式(lobe-chat-database 镜像)

📌 软件版本

v1.62.4

💻 系统环境

macOS

🌐 浏览器

Chrome

🐛 问题描述

在 AI 服务商里，对于本来已经填写了 API key 和 base url 的服务商，点击“连通性检查”后，显示 Key 不正确或为空，请检查后重试，然后刷新页面，API key 和 base url 都变为空白了

📷 复现步骤

1. 配置好服务商的key 和 base url （能正常使用）
2. 在该服务商的编辑页，修改“连通性检查”的模型，然后点击“连通性检查”
3. 如果失败了，刷新页面，配置会丢失

🚦 期望结果

No response

📝 补充信息

No response

[lobehubbot]

👀 @cloverzrg

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

📦 Deployment environment

Docker

📦 Deployment Mode

Server-side mode (lobe-chat-database mirror)

📌 Software version

v1.62.4

💻 System environment

macOS

🌐 Browser

Chrome

🐛 Question description

Occasionally, I have appeared twice, but the impact is great: in AI service providers, for service providers that have already filled in API key and base url, click "Connectivity Check" and the key is incorrect or empty. Please After checking, try again, and refresh the page, the API key and base url have both become blank

📷 Reproduction steps

My situation is:

1. In the old version (API key and base url were configured in the previous few weeks), configure the service provider's key and base url (can be used normally)
2. In the recent version, click "Connectivity Check" on the AI ​​service provider

🚦 Expected results

No response

📝 Supplementary information

No response

[dosubot]

@cloverzrg 你好！我是Dosu，一个能帮你解决bug、回答问题，并成为贡献者的机器人。我会在等待人类维护者的期间帮助你解决问题。

This issue seems to be related to a bug where clicking the "连通性检查" (connectivity check) causes the API key and base URL to be lost or reset. This has been reported in version v1.62.4 of the lobe-chat application. A similar issue was previously identified in version 1.47.21, where configured API keys and proxy URLs would not display correctly in the settings UI, although they remained functional. This was fixed in version 1.47.22 ^[1].

To address this issue, you might want to check if there are any updates or patches available for your current version that address this specific problem. Additionally, reviewing the changelog or recent commits might provide insights into any fixes or workarounds that have been implemented.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[cloverzrg]

补充一下复现步骤：需要先修改“连通性检查”的模型，然后再点击“连通性检查”

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Add to the reproduction steps: you need to modify the model of "Connectivity Check" first, and then click "Connectivity Check"

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

This "connectivity check" is also very unreliable. It succeeds and fails one after another. If the detection fails, it is very likely that the key and url will be empty. It is best to copy the key and url and refresh the page. If it is lost, You can fill in

[qinguoluo]

确实是这样。不仅如此，切换模型检查连通性往往会失败，一旦失败，保存的key和url也会丢失。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

That's true. Not only that, switching the model to check connectivity often fails, and once it fails, the saved keys and urls will also be lost.

[Cheukfung]

部署在vercel+neon的psql数据库的时候几乎每次都这样，输入API key马上点检查连通性一定失败，然后api key清空。

个人猜测：

可能是网络/数据库性能原因，在输入api key之后还没成功保存到数据库，连通性检查的请求就已经发出了，这时候api key还没保存到后段，连通性检查失败之后前端把已经输入的api key清空。不触发此bug的方式：输入api key后等待一段时间，再点连通性检查。

这个问题在阿里云的docker镜像基本没出现过。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

This is almost the case when deploying the psql database of vercel+neon. Enter the API key and click to check the connectivity immediately, and then the API key will be cleared.

Personal guess:

It may be because of the network/database performance. After entering the API key, the request for connectivity check has been issued. At this time, the API key has not been saved to the later section. After the connectivity check fails, the front-end input has been entered. clear api key. How to not trigger this bug: enter the API key and wait for a while, and then click connectivity check.

This problem has basically never appeared in Alibaba Cloud's docker image.

[cloverzrg]

部署在vercel+neon的psql数据库的时候几乎每次都这样，输入API key马上点检查连通性一定失败，然后api key清空。

个人猜测：

可能是网络/数据库性能原因，在输入api key之后还没成功保存到数据库，连通性检查的请求就已经发出了，这时候api key还没保存到后段，连通性检查失败之后前端把已经输入的api key清空。不触发此bug的方式：输入api key后等待一段时间，再点连通性检查。

这个问题在阿里云的docker镜像基本没出现过。

我的 lobechat 使用 lobe-chat-database 部署在香港性能比较差的机器上，偶尔会出现奇怪的问题，明明设置已经保存成功了但是后来不知道为什么又回到设置前的样子

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

This is almost always the case when deploying the psql database of vercel+neon. Enter the API key and click to check the connectivity immediately. Then the API key will be cleared.

Personal guess:

It may be because of the network/database performance. After entering the API key, the request for connectivity check has been issued. At this time, the API key has not been saved to the later section. After the connectivity check fails, the front-end has already Clear the entered api key. How to not trigger this bug: enter the API key and wait for a while, and then click connectivity check.

This problem has basically never appeared in Alibaba Cloud's docker image.

My lobechat is deployed on a machine with poor performance in Hong Kong using lobe-chat-database. Occasionally, strange problems occur. The settings have been saved successfully, but later I don’t know why I went back to the previous settings.

[cloverzrg]

确实是这样。不仅如此，切换模型检查连通性往往会失败，一旦失败，保存的key和url也会丢失。

@arvinxx 麻烦关注下这个 bug，目前还存在

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

It's true. Not only that, switching the model to check connectivity often fails, and once it fails, the saved keys and urls will also be lost.

@arvinxx Please pay attention to this bug, it still exists