You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not allowed to leave the "API Key" empty for LLMs in the "Model Settings". In some local LLM setups, the API key can be empty (unspecified). MaxKB cannot connect to such LLMs.
shaohuzhang1
changed the title
[Bug] 链接独立部署的大语言模型时不能不提供API Key
[Bug] API Key is required when linking independent deployed large language models.
Feb 26, 2025
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Hello, API Key is indeed not required when connecting to local models, but this is required when connecting to online model services. If the required verification is not set, it will cause the experience of this part of users to be bad, so it is retained here Required verification. When connecting to the local model, you can fill in any character to avoid verification.
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Hello, API Key is indeed not required when connecting to local models, but this is required when connecting to online model services. If the required verification is not set, it will cause the experience of this part of users to be bad, so it is retained here Required verification. When connecting to the local model, you can fill in any character to avoid verification.
Contact Information
wx: viktorromansky
MaxKB Version
社区版 1.10.0-lts build 50f2c96
Problem Description
模型设置里添加本地部署的OpenAI协议模型接口时,不能把API Key置空(服务配置时没有指定API key)
建议增加允许留空的配置
It is not allowed to leave the "API Key" empty for LLMs in the "Model Settings". In some local LLM setups, the API key can be empty (unspecified). MaxKB cannot connect to such LLMs.
Steps to Reproduce
系统设置 - 模型设置 - 添加模型 - DeepSeek / OpenAI / vLLM等设置项中,API Key一项均不允许为空。
The expected correct result
允许API Key留空
Related log output
Additional Information
No response
The text was updated successfully, but these errors were encountered: