I’ve been having errors like:

Error! Engines cannot retrieve results.

qwant (unexpected crash)

Please, try again later or find another searx instance. (Public instances)

Or:

Error! Engines cannot retrieve results.

brave (HTTP error)

Please, try again later or find another searx instance. (Public instances)

On both:

https://searx.sp-codes.de/search

https://searx.info/search

Not sure if it’s google blocking searx, or similar…

Edit: https://searx.sp-codes.de working right now, as well as some other instances… Thanks !

    • @kixik@lemmy.mlOP
      3•1 year ago

      Other than being different instances, does searxng have mechanism preventing actual search engines to rate limit them? AFAIK, besides translations, “more” user friendly UI, and introducing metrics (not so good for privacy), searxng is not that different from searx (except for the metrics collection).

      Or could it be there might be more searxng instances than searx ones now a days, which make it harder for actual search engines to identify them as big query makers?

      Just asking for the reasoning, not flame battles. Perhaps searxng introduced a feature which makes it more immune to actual search engines (aka Google), to start rate limiting the instances. But if it’s just a matter of time for the searxng instances to get rate limited as well, or not sure if even blocked, then I think that might be just a very shot term workaround.

      BTW, I found both, one searx instance and one searxng that are working. But I’m afraid that’s temporal…