this post was submitted on 17 May 2023
8 points (100.0% liked)

Privacy

31876 readers
1 users here now

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

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
k_o_t@lemmy.ml
tmpod@lemmy.pt
Yayannick@lemmy.ml
ranok@sopuli.xyz
8
is searx having problems (no matter the instance)? (lemmy.ml)
submitted 2 years ago* (last edited 2 years ago) by kixik@lemmy.ml to c/privacy@lemmy.ml
9 comments fedilink hide all child comments
 

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 !

top 8 comments
sorted by: hot top controversial new old
[–] Krusty@feddit.it 3 points 2 years ago (1 children)

Switch to SearXNG

[–] kixik@lemmy.ml 3 points 2 years 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...

[–] unsaid0415@szmer.info 1 points 2 years ago (1 children)

Qwant has a tendency to respond with an error response for no reason from time to time

[–] kixik@lemmy.ml 1 points 2 years ago

BTW, Today at least https://searx.sp-codes.de is working. It might be Google aggressively rate limited several instances, and for some time. And it relaxed those limits after some time.

Thanks !

[–] loki@lemmy.ml 1 points 2 years ago (1 children)

the instance i'm using is working fine with google. the instances you were using are probably rate limited by the search engines.

[–] kixik@lemmy.ml 1 points 2 years ago

I tried 3 other ones, *.ru, *.snopyta, *.xyz, *.win (a couple I don't remember are even no longer reachable). I'll see later. I've be using 1st *.info, then *.snopyta and now more often *.sp-codes.de, and so far so good, until now...

[–] shreddy_scientist@lemmy.ml 0 points 2 years ago (1 children)

https://searx.thegpm.org is working on my end. So at least this instance is working. I'd assume it's those instances or possibly a browser issue

[–] kixik@lemmy.ml 2 points 2 years ago* (last edited 2 years ago)

see my prior reply

I'll try other instances as well as the one you pointed out... Thanks !

load more comments
view more: next ›