[Bug] 无法使用DuckDuckGo(在https://nextchat.dev/上）

[jimchen2]

📦 部署方式

Other

📌 软件版本

网页版

💻 系统环境

Other Linux, Other

📌 系统版本

Fedora 40

🌐 浏览器

Chrome

📌 浏览器版本

129.0.6668.70

🐛 问题描述

用DuckDuckGo插件搜索，被captcha了

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: [Bug] Unable to use search function (on https://nextchat.dev/)

[lloydzhou]

这里应该是因为，在网页版本使用插件的时候，会使用当前的服务器做代理避免调用插件出现跨域错误。

大家都在一个地方使用的时候，这个插件会走相同的服务器出去，就有可能出现被服务提供商屏蔽的问题。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

This should be because when using the plug-in in the web version, the current server will be used as a proxy to avoid cross-domain errors when calling the plug-in.

When everyone uses it in the same place, the plug-in will go out through the same server, and there may be a problem of being blocked by the service provider.

[mountainguan]

这里应该是因为，在网页版本使用插件的时候，会使用当前的服务器做代理避免调用插件出现跨域错误。

大家都在一个地方使用的时候，这个插件会走相同的服务器出去，就有可能出现被服务提供商屏蔽的问题。

那怎么解决，感觉只要部署到 vercel 就有这个问题

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

This should be because when using the plug-in in the web version, the current server will be used as a proxy to avoid cross-domain errors when calling the plug-in.

When everyone uses it in the same place, the plug-in will go out through the same server, and there may be a problem of being blocked by the service provider.

How to solve it? It feels like this problem will occur as long as it is deployed to vercel.

[jimchen2]

这里应该是因为，在网页版本使用插件的时候，会使用当前的服务器做代理避免调用插件出现跨域错误。 大家都在一个地方使用的时候，这个插件会走相同的服务器出去，就有可能出现被服务提供商屏蔽的问题。

那怎么解决，感觉只要部署到 vercel 就有这个问题

可以选择个人申请一个api key，然后放入网页版？比如这个https://serpapi.com/duckduckgo-search-api/

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

This should be because when using the plug-in in the web version, the current server will be used as a proxy to avoid cross-domain errors when calling the plug-in. When everyone uses it in one place, the plug-in will go out through the same server, and there may be a problem of being blocked by the service provider.

How to solve it? I feel like this problem will occur as long as it is deployed to vercel.

Can I choose to apply for an api key personally and then put this in? For example, this https://serpapi.com/duckduckgo-search-api/