You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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).
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 : #211 (comment) ?
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
The text was updated successfully, but these errors were encountered: