[Bug] 讯飞星火 点击获取模型列表的时候报错

[lfffffy]

📦 部署环境

Docker

📌 软件版本

v1.36.43

💻 系统环境

Windows

🌐 浏览器

Chrome

🐛 问题描述

已经确定了APIKey是正常的，连通性检查是正常的。

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[lobehubbot]

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

---

📦 Deployment environment

Docker

📌 Software version

v1.36.43

💻 System environment

Windows

🌐 Browser

Chrome

🐛 Problem description

It has been determined that the APIKey is normal and the connectivity check is normal.

📷 Steps to reproduce

No response

🚦 Expected results

No response

📝 Supplementary information

No response

[lobehubbot]

👀 @lfffffy

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。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[lfffffy]

出错的API 端点是 /webapi/chat/models/spark

[lobehubbot]

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

---

The wrong API endpoint is /webapi/chat/models/spark

[dosubot]

The error you're encountering seems to involve a 404 status and an errorType 500 when trying to retrieve the model list from the 'spark' provider in the lobe-chat application. This issue is occurring in a Docker deployment environment on Windows, using Chrome as the browser.

Here are a few things to consider:

1. API Key and Connectivity: You've mentioned that the API key and connectivity are confirmed to be working. This rules out common issues related to authentication or network problems.

2. Error Handling: The lobe-chat application has specific error handling for errorType 500, which typically indicates an internal server error. However, there is no specific handling mentioned for a 404 status in the context provided ^[1].

3. Kong and Latency: The response is processed through Kong, which might be affecting the request routing or response handling. Ensure that Kong is correctly configured to route requests to the 'spark' provider.

4. Configuration Parameters: The request parameters include model: "lite", stream: true, and a message array. Verify that these parameters are correctly set and supported by the 'spark' provider's API ^[2].

5. Debugging: Enable debugging features to get more insights into the request flow. Set the DEBUG_SPARK_CHAT_COMPLETION environment variable to '1' to log detailed information about the requests to the 'spark' provider ^[3].

If the issue persists, consider checking the Docker setup and any network configurations that might affect the communication with the 'spark' provider.

To continue talking to Dosu, mention @dosu.

---

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