mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #1274] [BUG] 429 Too Many Requests/Temporarily down #749
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#749
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 @blackletum on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1274
Describe the bug
Past few days I've been unable to get any results at all. I either get the message "429 Too Many Requests" or "Temporarily down". VERY occasionally, I will get a search that slips through, but 95%+ of the time, I get these errors instead.
To Reproduce
Steps to reproduce the behavior:
Deployment Method
runexecutableVersion of Whoogle Search
Desktop (please complete the following information):
@hugo-telecoop commented on GitHub (Nov 10, 2025):
Sadly Mullvad VPN is shutting down their search proxy Leta ; these troubles are Leta related ; they are happening directly using https://leta.mullvad.net ; so it's a dead end apparently ;-/
@Don-Swanson commented on GitHub (Nov 10, 2025):
It is likely that it's an issue with Mulvad, but I'm unable to replicate to say for certain. Which version # are you using?
@blackletum commented on GitHub (Nov 10, 2025):
v1.1.0
Today it hasn't happened to me, strangely, but maybe it has to do with that hugo was saying?
Today was actually the first day it's been working fine for me (so far).
@blackletum commented on GitHub (Nov 10, 2025):
6:25 PM EST, it's doing it now to me.
@Don-Swanson commented on GitHub (Nov 11, 2025):
If you go to Leta when it’s happening, do you get the error searching directly? Is this a shared instance or do you do a lot of searches where their protections might kick in for your IP?
@Don-Swanson commented on GitHub (Nov 11, 2025):
Either way, we won’t spend too much time on this because Leta will be discontinued at the end of the month, and I’m still trying to find a better way to get back to the Google results
@blackletum commented on GitHub (Nov 11, 2025):
I just self host only for myself, I use it a couple times a day at most.
I did test with leta directly when I was having the issue just now and it worked fine, so I'm really not sure what's going on here with it.
@Don-Swanson commented on GitHub (Nov 11, 2025):
Do you self host on the same public IP as where you as a user are coming from?
@blackletum commented on GitHub (Nov 11, 2025):
I self host it at home and it's not exposed to anything public, but yes it's on the same IP
@freQniK commented on GitHub (Nov 13, 2025):
Jesus. Poor Whoogle devs keep running into dead ends. Very frustrating I can imagine.
@skaboy71 commented on GitHub (Nov 14, 2025):
Been having same myself running self-hosted in a Docker. Damn greedy search companies! They don't like it when we don't give them all our data. ;-)
@Don-Swanson commented on GitHub (Nov 20, 2025):
I experienced it for the first time yesterday. It traced back to Leta. Since Leta is on its last leg I will close this out as Will Not Fix.