-
-
Notifications
You must be signed in to change notification settings - Fork 11.2k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] 插件使用bug #5459
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
The issue you're experiencing with the plugin using the If the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Gateway是实际后端发请求的接口。没有啥问题 |
Gateway is the interface through which the actual backend sends requests. No problem |
This issue is closed, If you have any questions, you can comment and reply. |
除了api-key和engine-id还有什么需要额外配置的吗 为什么会发送gateway |
In addition to api-key and engine-id, is there anything else that needs to be configured? Why is gateway sent? |
即使我在官方网站使用,在配置api-key和engine-id后仍然会gateway |
Even if I use it on the official website, the gateway will still appear after configuring the api-key and engine-id. |
gateway 是插件请求的统一网关,请求路径为: lobechat 前端 -> lobechat 后端插件网关 -> 插件服务端 通过后端对后端请求可以解决前端发请求的跨域问题,同时后端插件网关也承担了插件服务发现、插件请求入参校验等职能。 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
📦 Environment
Docker
📌 Version
1.45.7
💻 Operating System
Ubuntu
🌐 Browser
Chrome, Edge
🐛 Bug Description
联网搜索为什么会直接调用gateway,已经配置了api-key和engine-id,我看了相关的源码,认为是lobe-chat的问题
📷 Recurrence Steps
No response
🚦 Expected Behavior
No response
📝 Additional Information
No response
The text was updated successfully, but these errors were encountered: