mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 04:05:57 +03:00
[GH-ISSUE #707] [BUG] Instance has been ratelimited #454
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#454
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 @eddydc on GitHub (Apr 1, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/707
Describe the bug
Getting
Error
Instance has been ratelimited
Continue your search with Farside
Whoogle:
https://farside.link/whoogle/search?q=dit is een test&lang_interface=lang_en&country=BE&theme=system
Searx:
https://farside.link/searx/search?q=dit is een test
Return Home
To Reproduce
Just do a search with Whoogle
Deployment Method
Version of Whoogle Search
lastest
Desktop (please complete the following information):
Win 10, latest FF
@T3chHunt3r commented on GitHub (Apr 28, 2022):
I too have this issue on version 0.7.0
update: This issue seems to be resolved for me, I re-composed the docker container as well as changed locations for my VPN. I'm not sure which of the two fixed the issue however. It's more likely that it was a VPN issue as I was also blocked from certain sites due to the IP that I was under at the time.
@ShlomiD83 commented on GitHub (May 9, 2022):
same issue for me.
can't resolve the issue no matter what I do.
@sysoppl commented on GitHub (May 28, 2022):
Same for me, just deployed and it's not working at all.
@ironboy1 commented on GitHub (May 31, 2022):
Same on my side for version 0.7.1 and 0.7.2
@bruvv commented on GitHub (Jun 5, 2022):
This has been answered already: https://github.com/benbusby/whoogle-search/issues/211
@pieslinger commented on GitHub (Jun 6, 2022):
I am having rate limiting issues occasionally and I am the only user of whoogle running in a container. I do not see how #211 has answered this already. I would install this for more people in my life as well if this issue goes away. Is there just something I need to modify in the setup?
@pieslinger commented on GitHub (Jun 6, 2022):
I also only noticed it in 0.7.1 and 0.7.2 - although 0.7 was my first time using this. Just installed 0.7.3 tonight.
update: I use Pihole as well
@aw-jansen commented on GitHub (Jun 10, 2022):
Same here, currently on 0.7.3. Getting the rate limiting message when connected via a NordVPN container. Would it still be a possibility to implement a workaround? On a different topic someone mentioned changing the query: https://github.com/searxng/searxng/issues/159
@aindriu80 commented on GitHub (Jun 10, 2022):
I'm having the same error, only making a few requests and get this error, I'm using Pi-Hole and wonder has that anything to do with it?
@ghost commented on GitHub (Jun 28, 2022):
Same here on 0.7.4 using a public IP with password. Getting limited for average one or two days. Restarting the docker can fix it, but the problem always appears again.
@jojolll commented on GitHub (Jul 8, 2022):
I use my own Whoogle instance (alone). Almost every day I reach the ratelimit after 10 to 15 searches during the day.
I have the chance with my LiveBox to be able with a simple click in the interface to renew my IP, that solves the problem for 1-2 days.
It's still very annoying and makes the solution of a personal Whoogle server very unviable.
@Albonycal commented on GitHub (Oct 22, 2022):
there isn't much you can do about this issue, google blocks the requests it thinks are suspicious. If your IP is dynamic, try rebooting or change your VPS's IP.
@dr460nf1r3 commented on GitHub (Oct 23, 2022):
This might in fact also be caused by bots crawling the instances. At least I noticed that the rate limits became less after blocking most known bots via Cloudflare WAF (12k events over 24h) 🤔
@CptanPanic commented on GitHub (Dec 13, 2022):
I am having this issue today also. I am not sure what #211 has to do with this, is there any debug to look at to see what is causing the issue?
@bruvv commented on GitHub (Dec 14, 2022):
For me. A restart of the docket container fixes this.
@ghost commented on GitHub (Dec 14, 2022):
I moved my VPS form Linode to Amazon Lightsail 5 months ago and never have the issue again.
@ForceConstant commented on GitHub (Dec 19, 2022):
It is not clear from the error message, but looking at the code, the ratelimit is external to whoogle, and it is coming from a service that whoogle is querying. And if it gets a captcha, then it reports this. So I couldn't imaging how @bruvv restarting your container would affect this.
@0xspade commented on GitHub (Jan 11, 2023):
Doesn't work on my side.
@CptanPanic commented on GitHub (Jan 11, 2023):
For me, it turns out it was the proxy I was using. I guess there was too
many people at that IP address.
On Wed, Jan 11, 2023 at 4:45 AM 0xspade @.***> wrote:
@Paulie420 commented on GitHub (Jan 16, 2023):
So... I get this with both whoogle-search and googler - only when connected to my Private Internet Access VPN on some of their locations. Canada being one of them.... I'd bet a lot of folks seeing this issue are simply behind a VPN that Google is blocking - if this describes your setup, try disconnecting from your VPN and running whoogle-search again; viola, fixed.
@Snake16547 commented on GitHub (Mar 24, 2023):
Same issue here after 2 months of whoogle usage.
Tried to restart docker container - still rate limit exceeded
So basically moving to different machine would solve the problem? Any recommendations?
@dr460nf1r3 commented on GitHub (Mar 24, 2023):
From my understanding it's the IP getting rate-limited, so using another one should work.
@Snake16547 commented on GitHub (Mar 26, 2023):
Easy to say to change the IP when you have a VPS
@brokoler commented on GitHub (Apr 7, 2023):
Since the last 2 days all of the public Whoogle instances are affected by this, most times only one of them works and yesterday it happened that even with Farside all instances were rate limited.
To me it seems like Google is going against Whoogle, but I still hope it's just a bug in the latest Whoogle software that can be fixed.
@benbusby do you have a clue what is happening right now?
@Snake16547 commented on GitHub (Apr 7, 2023):
I switched to the Oracle free tier and until now I'm free of any ratelimit messages.
@benbusby commented on GitHub (Apr 7, 2023):
@brokoler public instances go through waves of all being rate limited, and then being clear again. It looks like some are available now. There's no simple fix to get around it unfortunately, but it isn't a bug in Whoogle. I always recommend using your own Whoogle instance, or running it locally on your machine (behind a VPN if you want) if rate limiting becomes too much of a problem.
@MaverickTN commented on GitHub (Apr 17, 2023):
I just had this issue for the first time after updating to 0.8.2. I last used it 3 days ago, and it's rate-limited on all queries. Restarted the container, no change.
Private instance, closed network, docker container.
@Johnnii360 commented on GitHub (May 9, 2023):
I'm joining this issue. Same problem on my instance. Maybe it could be a workaround to use an API key in the developer console but it has to be implemented by @benbusby . It's a common thing that Google shows an CAPTCHA request if there too many search request of one and the same IP. I think it's their "DDoS protection".
Edit 1:
Another solution could be the usage of Tor service. But there must be an function that every new visitor is bind to a new Tor connection. If Whoogle needs also one and the same Tor connection it will also end in this issue. Otherwise the Tor service or connection has to be refreshed every day or hour or whatever. I will give it a try.
Edit 2:
Okay, bad idea. :D
Edit 3:
Uhm... I just changed the country now to my country (German) and also the search language. Now it works again. But the question ist: How long? :)
@robertpartridge commented on GitHub (Jun 26, 2023):
I've run into this problem today with my deployment of version 0.8.2. My instance is behind basic HTTP auth with a fairly strong unique password so that it's not open to just anyone to use. Any advice?
Edit - reading through more of the responses and wondering if the problem might be related to the instance being deployed on Oracle's Cloud. Will investigate.
@seirdotexe commented on GitHub (Jul 4, 2023):
Getting this too now on my own IP address, locally hosted. Already restarted the container and even reinstalled it.
@akovia commented on GitHub (Jul 16, 2023):
Just installed whoogle 0.8.2-1 for the first time ever from Arch aur, so have no frame of reference of how it's supposed to even work.
Is there anything I can do to get this working?
I'm behind a VPN, so is that an actual issue to run a self hosted instance?
@Deviantgit commented on GitHub (Jul 17, 2023):
Have also started running into this--I would get it occasionally over the past year and a half I've been using Whoogle, but generally it'd go away after a few hours. For the past two weeks or so I have only been getting the rate limited message despite taking down my docker container and waiting over 24 hours, etc. This is with it both behind a VPN as well as a non-VPN IP. It's rather odd.
@imTHAI commented on GitHub (Nov 7, 2023):
Today I face the same problem. But I use it on an internal docker container, and I'm the only one who use it in the family. How is it possible that I have reached the rate limit of search requests for google, from a single home user ?! 🤔
EDIT: Even if I make the whoogle container goes out on internet through the internet connection of my parents (retired people using very little internet, living in a country other than me), I get this rate limit error.
@winhex commented on GitHub (Nov 7, 2023):
Same problem. I'm deploying the docker container with whoogle 0.8.4 at my own home server. No public access, only personal using. Instance has been rate limited after 20-30 min of using
@Drallas commented on GitHub (Nov 8, 2023):
I also have been rate limited, my Whoogle runs in a tteck LXC container. Updating the OS doesn't solve it!
@zidanpragata commented on GitHub (Nov 13, 2023):
whatever time, if direct search method is not changed to the brilliant idea of "yacy search", error message "rate is limited" will still occur frequently.. the easiest solution to overcome this is to change the IP..
failed :)
@aindriu80 commented on GitHub (Nov 15, 2023):
I tried changing IP and using VPN but still getting rate limited, very frustrating
@akovia commented on GitHub (Nov 15, 2023):
I bit the bullet and signed up for Kagi now that they made unlimited searches more affordable. I find it better than Google in so many ways and doubt I'll ever go back. I have no skin in the game, but they have a free trial if you want to check it out.
Either way I hope you get it figured out.
@Snake16547 commented on GitHub (Nov 15, 2023):
I had it running on Oracles free tier with zero problems. Several clients used my instance.
Now I switched to Hetzner Cloud and running smoothly as well.
@imTHAI commented on GitHub (Nov 15, 2023):
Could someone explain why a whoogle instance can be sometimes rate-limited when the other computers (behind the same public ip) aren't when using google ?
Are the requests from whoogle so special (and harmful?) that Google identifies them and limits them ?
@Drallas commented on GitHub (Nov 15, 2023):
Whoogle is nice, but the search results from Google feel manipulated and without still optimized to show payed results first. Would be better if Whoogle could include more search options. Kagi might be an alternative too!
@MuubNito commented on GitHub (Nov 16, 2023):
ALL instances i am trying or doesnt work or just straight up give me another issue... Ouch
@imTHAI commented on GitHub (Dec 14, 2023):
I don't know about you, but I can use my whoogle container again without any problems.
Maybe google changed something on his side ?
@seirdotexe commented on GitHub (Sep 7, 2024):
Since a week, my instance is getting rate limited constantly now, only after 20 searches. Makes it impossible to use Whoogle
@C8opmBM commented on GitHub (Sep 8, 2024):
happened to me as well 2 times today.
@EasternPA commented on GitHub (Oct 8, 2024):
I just got this for the first time ever. I am the sole user of a docker-compose stack on Oracle Free Tier. I recently lost SSH access due to rebuilding my PC, so I need to rebuild the cloud instance anyway. Perhaps a rebuild will clear it up.
@Zundrium commented on GitHub (Oct 18, 2024):
Same here, CHAPTA seems to be the issue
@byertsy commented on GitHub (Nov 18, 2024):
Same issue here. Downloaded today and was bust setting up a new CSS theme and got this issue.
@mlause commented on GitHub (Nov 22, 2024):
Same here. Is there anyway to passthrough the captcha?
@working-name commented on GitHub (Dec 23, 2024):
I run whoogle both behind a residential connection and datacenter (so I can switch between them when one gets rate limited).
There's no difference in getting rate limited based on IP or IP type (residential vs data center).
I'm the only one using both instances, checked logs.
I do aggressively google things though (still manual, not automated, so definitely not more than 1 search per second), sometimes with minor tweaks (like "sle crescentic" which later changed to "psgn crescentic") and that's when I notice a higher incidence of rate limiting.
Update: switching to searxng on the same rate limited residential IP gives me instant google results. No rate limiting. Worth checking this out, @benbusby : https://github.com/searxng/searxng/issues/1642
🙏 @unixfox
@jobsidi commented on GitHub (Dec 31, 2024):
Got this error. Logs: ERROR:app:503 (CAPTCHA)
searched last time via whoohle 6 monthes ago
@eyalzek commented on GitHub (Mar 11, 2025):
I'm seeing the same (
ERROR:app:503 (CAPTCHA)) on a newly deployed self-hosted instance after about 10 queries...Is there an obvious cause for that? Any way to "reset" it? Any configuration best avoided?
@boognish-rising commented on GitHub (May 17, 2025):
I just got rate limited on a local install (not hosted, available only via http://localhost:5000). I was completely caught off guard, as I've used whoogle locally for years without getting rate limited. Like @byertsy, I was checking out different CSS themes and submitted the same search of "test" maybe 10 times when it occured. I wonder if it was repeating the same search or perhaps doing so with a different css theme each time and thus, a different URL that triggered it?
Here's hoping it was an isolated incident
@martijnboers commented on GitHub (Jun 6, 2025):
I have a feeling adjusting settings seem to trigger this? I was querying yesterday all day fine but now after changing things like search language and country getting rate-limited..
@C8opmBM commented on GitHub (Jun 6, 2025):
I very rarely get ratelimited, this is when I querry too many searches in a short period.
Usually it gets back to normal relatively fast.
@martijnboers commented on GitHub (Jun 10, 2025):
Querying fine again for multiple days and not touching any of the settings.
@github-actions[bot] commented on GitHub (Sep 16, 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.
@github-actions[bot] commented on GitHub (Sep 23, 2025):
Closing this issue due to prolonged inactivity.