is docker compose update for DuckDuckGo rate limit??

[yichaosun]

Self Checks

it seems the fix not available in docker compose ,pls, #9047

or, maybe new question came out, because two days ago ,it worked!
however, I pull git for latest ,question still exist

Dify version

latest

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

DuckDuckGo Tool meet rate limit error

it seems the fix not available in docker compose.

however, curl can work in terminal

[dosubot[bot]]

Hello @yichaosun! I'm here to help you with bug reports, answer questions, and guide you on becoming a contributor. Let's work together to solve the issue you're facing.

I couldn't find any specific updates or patches in the Dify codebase related to handling rate limits for external APIs like DuckDuckGo in the Docker Compose setup ^[1]. Additionally, there are no known issues or open discussions specifically addressing DuckDuckGo rate limits in the Dify documentation or GitHub repository ^[1].

However, there is a similar unsolved discussion about issues with external HTTP requests after installing Dify with Docker Compose on Ubuntu, which might be related or provide some insights. You can check it out here ^[2].

For managing rate limits, Dify recommends setting a limit on the maximum number of active requests, using request expiration, regularly flushing the cache, handling errors appropriately, and managing request IDs ^[1]. These practices might help in addressing the rate limit issues you're encountering.

To continue talking to Dosu, mention @dosu.

[skywolf123]

Yes, I encountered the same situation as well, deploying with the same docker-compose and receiving the same duckduckgo error 202 Ratelimit