[GH-ISSUE #652] [BUG] Rate limited after first install #415

New issue

Closed

opened 2026-02-25 20:35:42 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 20:35:42 +03:00

Owner

Originally created by @d4rklynk on GitHub (Feb 11, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/652

Describe the bug
I have rate limited right after I installed whoogle

Deployment Method
Whoogle on docker on a VPS, Cloudflare as DNS (proxied or not proxied, I have same issue)

Version of Whoogle Search
latest one (today at 11-02-2022)

Additional context
I use Whoogle with docker on a VPS, behind Nginx Proxy Manager, with Cloudflare as DNS server (but not proxied), every settings is default

Originally created by @d4rklynk on GitHub (Feb 11, 2022). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/652 **Describe the bug** I have rate limited right after I installed whoogle **Deployment Method** Whoogle on docker on a VPS, Cloudflare as DNS (proxied or not proxied, I have same issue) **Version of Whoogle Search** latest one (today at 11-02-2022) **Additional context** I use Whoogle with docker on a VPS, behind Nginx Proxy Manager, with Cloudflare as DNS server (but not proxied), every settings is default

kerem

2026-02-25 20:35:42 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:35:42 +03:00

Author

Owner

@benbusby commented on GitHub (Feb 14, 2022):

As much as I'd love to prevent this from happening to anyone, it's unfortunately mostly out of my control. It's a reality of using a service that Google doesn't want to be used and actively tries to block. I have this happen to me occasionally as well, and I typically just have to migrate to a different VPS when it does happen.

It's obviously not ideal, and seems to affect some people disproportionately more than others (with no clear reason why).

@benbusby commented on GitHub (Feb 14, 2022): As much as I'd love to prevent this from happening to anyone, it's unfortunately mostly out of my control. It's a reality of using a service that Google doesn't want to be used and actively tries to block. I have this happen to me occasionally as well, and I typically just have to migrate to a different VPS when it does happen. It's obviously not ideal, and seems to affect some people disproportionately more than others (with no clear reason why).

kerem commented

2026-02-25 20:35:42 +03:00

Author

Owner

@d4rklynk commented on GitHub (Feb 15, 2022):

Ok thank you for your reply !

@d4rklynk commented on GitHub (Feb 15, 2022): Ok thank you for your reply !

kerem commented

2026-02-25 20:35:42 +03:00

Author

Owner

@Goelant commented on GitHub (Apr 29, 2022):

I know this issue is closed, but as I'm having the same issue, I just bring the idea of maybe finding a turn-arround, maybe by setting up a new endpoint like this answer purpose : https://github.com/benbusby/whoogle-search/issues/211#issuecomment-898753235 ?

Have a great day 👋 !

@Goelant commented on GitHub (Apr 29, 2022): I know this issue is closed, but as I'm having the same issue, I just bring the idea of maybe finding a turn-arround, maybe by setting up a new endpoint like this answer purpose : https://github.com/benbusby/whoogle-search/issues/211#issuecomment-898753235 ? Have a great day 👋 !