Bug: google engine - rate limits #4429
-
|
Version of SearXNG, commit number if you are using on master branch and stipulate if you forked SearXNG They are ... How did you install SearXNG? The official wiki is used.What happened? Google block the search indicating too many search attempts, this is not a very heavyly used search proxy ... How To Reproduce Any search at the moment give a failed attempt from Google. Expected behavior An answer from Google ...Screenshots & Logs Additional context Technical report Error
|
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 3 replies
-
|
In addition to the above, Quant failed Suspended:CAPCHA requests, bing however says available no return. A number of public servers doing the same. If I query directly to SE no issues. Looked at DD. Seems to be a number of DDoS attacks going on today, not sure if related. But Azure minimum. |
Beta Was this translation helpful? Give feedback.
-
|
Seeing the same: 2025.3.2+8984d7ae0 running in a docker container. Restarting that didn't help. |
Beta Was this translation helpful? Give feedback.
-
|
Is your instance publicly accessible? |
Beta Was this translation helpful? Give feedback.
-
|
Nope, Lan only and I'm the only user, making this even more surprising. Direct access to Google from the same source IP still works. |
Beta Was this translation helpful? Give feedback.
-
|
My instance publicly accessible but run though CF and I have strict policies on it and also bot detection, geo restrictions, and rate limiting from the CDN. Have been running for years this just popped up today. I looked at my security console and didn't notice anything suspicious outside of the normal rejected activity. I added brave an DDG in the meantime. Bing working, qwant and google no. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, it's a public instance but I have server: ... in the Nginx config as well as [botdetection.ip_limit] ... in /etc/searxng/limiter.toml I also have a very strict DDoS policy in my firewall and no indication that there has been an excessive usage lately. Looking at searx.space none of us have any results in the "Google response time" column at the moment so this is probably a bigger issue. Using the same network as my server, hence same public IP, Google works just fine coming from the same public IP using a laptop running Firefox ... Have a nice day, |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue for a few hours. I deployed one instance on a VPS, one instance on my home network, and one instance on different VPNs. Using Docker. |
Beta Was this translation helpful? Give feedback.
-
|
Related: I will have a look about the issue today. |
Beta Was this translation helpful? Give feedback.
-
|
Any news on this. My instance has been down since Dec. I've shut the container down for several days, but as soon as it comes back online it is blocked. My SearXNG instance is using a GlutunVPN connection to a ProtonVPN IP. The searchXNG instance is local with only myself and my wife as users. I've tried to create a custom engine with an API Key but that doesn't even show up in the UI. I really don't understand the problem honestly. Why is google rate limiting my very low use instance, but I can go to a high volume public instance and it has no such issue. This means there is a configuration that works, but for some reason is not distributed to the average user. Any help would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Related:
I will have a look about the issue today.