mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #1159] [BUG] Whoogle deployed in Render.com gives error/rate limited. #702
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#702
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @Taratect on GitHub (Jun 9, 2024).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1159
Describe the bug
I have waited a full week to see if this rate limit issue gets subsides. That means no searches on my instance for a week, still it's not resolved.
IDK if I'm the only facing this issue. But I have redeployed. Restarted service, install past commits as well the latest one. Even Tried on another render account. I keep facing the same rate limit error
To Reproduce
Steps to reproduce the behavior:
Deployment Method
runexecutableVersion of Whoogle Search
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
I have deployed whoogle temporarily to replit, it has no problem. Sadly replot has removed always on service on their free tier. So it's not a good solution for me. Other deployment methods require technical knowledge which I don't have
I'm not a coder
@maxdesalle commented on GitHub (Jun 9, 2024):
Getting the same problem on my end, with a manual Docker setup.
EDIT: worked a few hours later again on my end, haven't had any issues since then.
@github-actions[bot] commented on GitHub (Sep 15, 2025):
This issue has been automatically marked as stale due to inactivity. If it is still valid please comment within 7 days or it will be auto-closed.