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
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 !
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.96K Posts
- 74.6K Comments
- Modlog
Switch to SearXNG
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…