智普的嵌入模型一直秘钥错误

[webwww123]

📦 Platform

Vercel

📦 Deploymenet mode

client db (lobe-chat image)

📌 Version

最新

💻 Operating System

Windows

🌐 Browser

Chrome, Edge

🐛 Bug Description

新增了vercel的环境变量DEFAULT_FILES_CONFIG=embedding_model=zhipu/embedding-3,reranker_model=zhipu/rerank,query_mode=full_text
还有一个ZHIPU_API_KEY
一直报错apikey不对

{
endpoint: 'https://open.bigmodel.cn/api/paas/v4',
error: Error: 401 令牌已过期或验证不正确！
at tH.generate (.next/server/chunks/50850.js:5:59351)
at sa.makeStatusError (.next/server/chunks/50850.js:5:73758)
at sa.makeRequest (.next/server/chunks/50850.js:5:74702)
at async Object.embeddings (.next/server/chunks/75502.js:1:9078)
at async (.next/server/chunks/38964.js:1:32514)
at async a.middlewares (.next/server/chunks/54015.js:1:13112)
at async f (.next/server/chunks/54015.js:4:68)
at async f (.next/server/chunks/54015.js:4:68)
at async f (.next/server/chunks/54015.js:4:68) {
status: 401,
headers: {
connection: 'keep-alive',
'content-length': '73',
'content-type': 'application/json',
date: 'Thu, 27 Mar 2025 03:33:00 GMT',
server: 'ZenZGA/2.4',
'strict-transport-security': 'max-age=31536000; includeSubDomains',
vary: 'Origin, Access-Control-Request-Method, Access-Control-Request-Headers',
'x-log-id': '20250327113300021b615f89174f53'
},
request_id: undefined,
error: { code: '401', message: '令牌已过期或验证不正确！' },
code: '401',
param: undefined,
type: undefined
},
errorType: 'InvalidProviderAPIKey',
provider: 'zhipu'
}

还有一个报错：

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

[lobehubbot]

👀 @webwww123

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

[webwww123]

还有一个
Error [TRPCError]: InvalidProviderAPIKey at <unknown> (.next/server/chunks/38964.js:1:33107) at async a.middlewares (.next/server/chunks/54015.js:1:13112) at async f (.next/server/chunks/54015.js:4:68) at async f (.next/server/chunks/54015.js:4:68) at async f (.next/server/chunks/54015.js:4:68) at async f (.next/server/chunks/54015.js:4:68) at async f (.next/server/chunks/54015.js:4:68) at async r (.next/server/chunks/54015.js:1:13344) at async (.next/server/chunks/62304.js:1:18574) { cause: undefined, code: 'INTERNAL_SERVER_ERROR' }

[dosubot]

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

To resolve the "InvalidProviderAPIKey" error with the ZHIPU_API_KEY on Vercel, ensure that the API key is valid and has not expired. Here are some steps you can take:

1. Verify API Key: Double-check that the ZHIPU_API_KEY is correctly set in your environment configuration. Ensure that it is up-to-date and has the necessary permissions for embedding models.

2. Environment Configuration: Make sure that the DEFAULT_FILES_CONFIG is correctly configured in your environment variables. It should specify the correct embedding model and reranker model.

3. Remove Conflicting Configurations: Ensure there are no conflicting API keys or configurations for other providers like OpenAI that might interfere with the Zhipu settings.

4. Check Logs: If the problem persists, check the logs for more detailed error messages that might provide additional insights.

These steps should help resolve the issue with the Zhipu embedding model on Vercel ^[1][2].

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}