Google always gives "Too many requests" #321
Replies: 2 comments 1 reply
-
OK, I figured out what's happening. I'm running this on my NAS and it automatically routes through my VPN. If I try hitting Google locally with my VPN enabled I get: If I run SearXNG on my dev machine with VPN disabled, I do get Google results: I tried switching my VPN to a different server and then Google loaded, so it might be just that the server closest to me has a tainted reputation...? Perhaps a silly question and I know this is not really a SearXNG issue, but any suggestions on what to do here? Is my only option to use a different VPN server (or disable VPN altogether, which I won't do)? |
Beta Was this translation helpful? Give feedback.
-
The vast majority of my VPN's servers are marked as malicious by Google 😢 but I found a couple that are not. I switched my NAS to use that server (even though it's got quite the latency) and now the Google engine works as expected: I'm honestly wondering if I should switch VPN providers at this point, but perhaps this is a common problem across all providers . . . if anyone has any thoughts, I'm eager to hear them. |
Beta Was this translation helpful? Give feedback.
-
Hi,
Every search I perform against my local instance results in "too many requests" for the Google engine:
Relevant logs:
Interestingly, the URL in the log looks like a redirect URL rather than the original - not sure if that's a bug or not. If I copy the URL as-is into my browser I get the expected:
If I try only the first part of the URL shown in the "sorry" page, it works (trying the whole thing succeeds but downloads a text file in a format I don't understand):
What might be wrong here? I've tried turning the limiter off just in case, but I get the same behavior.
Beta Was this translation helpful? Give feedback.
All reactions