langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

is docker compose update for DuckDuckGo rate limit?? #6656

New Issue
Closed
opened 2026-02-21 18:16:43 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:16:43 -05:00
Owner
Copy Link
Copy Source

Originally created by @yichaosun on GitHub (Nov 10, 2024).

Self Checks

it seems the fix not available in docker compose ,pls, https://github.com/langgenius/dify/pull/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

image

it seems the fix not available in docker compose.

however, curl can work in terminal

image

Originally created by @yichaosun on GitHub (Nov 10, 2024). ### Self Checks it seems the **fix not available in docker compose** ,pls, https://github.com/langgenius/dify/pull/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 ![image](https://github.com/user-attachments/assets/a2088528-7b35-46a4-bd8c-748dae61d2ae) **it seems the fix not available in docker compose.** however, curl can work in terminal ![image](https://github.com/user-attachments/assets/0e818c41-9718-4003-b2e0-f0a0464dbafa)
yindo added the 🐞 bug label 2026-02-21 18:16:43 -05:00
yindo closed this issue 2026-02-21 18:16:43 -05:00
yindo commented 2026-02-21 18:16:43 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 10, 2024):

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.

@dosubot[bot] commented on GitHub (Nov 10, 2024): <!-- Greeting --> 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. <!-- Answer --> 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 <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/app/features/rate_limiting/rate_limit.py)</sup>. Additionally, there are no known issues or open discussions specifically addressing DuckDuckGo rate limits in the Dify documentation or GitHub repository <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/app/features/rate_limiting/rate_limit.py)</sup>. 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](https://github.com/langgenius/dify/discussions/8423) <sup>[[2]](https://github.com/langgenius/dify/discussions/8423)</sup>. 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 <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/app/features/rate_limiting/rate_limit.py)</sup>. These practices might help in addressing the rate limit issues you're encountering. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#6656
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?