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
I'm currently using the webapp and I keep getting 500: DDG detected an anomaly in the request, you are likely making requests too quickly. while using the Official "Web-search" plugin. I tried with and without an assistant activated and had "Web Reader" and "Web Search" activated. Small prompt and gave it 15 minutes tried again and was still getting the error.
Some plug-ins use DuckDuckGo services. It is known that DuckDuckGo will limit the flow of IP traffic, and the rules of IP flow control are not known yet. If you have opened a proxy, you can try to close the proxy or change the proxy IP.
The Web Reader plug-in can be used independently and is not affected by the DDG service.
Hello, my deployment to the Vercel container is complete, but why can't I use the plugin? Every time I try, it shows a 500 error. However, it works fine on your GitHub site.
Hello, my deployment to the Vercel container is complete, but why can't I use the plugin? Every time I try, it shows a 500 error. However, it works fine on your GitHub site.
I will try to fix it, but in the short term the service will be affected by the ip throttling of the DDG service.
Bug Description
I'm currently using the webapp and I keep getting 500: DDG detected an anomaly in the request, you are likely making requests too quickly. while using the Official "Web-search" plugin. I tried with and without an assistant activated and had "Web Reader" and "Web Search" activated. Small prompt and gave it 15 minutes tried again and was still getting the error.
Steps to Reproduce
Expected Behavior
I expected to see the web search sources and have the return of the details.
Screenshots
No response
Deployment Method
Desktop OS
Windows 10
Desktop Browser
Microsoft Edge
Desktop Browser Version
Latest
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response
The text was updated successfully, but these errors were encountered: