>>106109892
works on my machine, some public searxng instances are just broken due to how searx works
searx is a search engine aggregator, it basically searches a ton of normie search engines, filters out garbage depending on how you configured it, gets rid of ads or aislop, hides sites like r*ddit (or redirects r*ddit links to some freetard frontend that doesn't IP ban you randomly by default) if you configure that, and then shows you all of those results.
this means that proprietary search engines like google, duckduckgo, and especially yandex love to rate limit the IP of the server this searx instance is running on, or just bombard it with captchas (which the admin would have to solve manually or bypass somehow)
solution: pick another searx instance, sometimes instance X works, sometimes it doesnt, cycle through them
or ideally, host your own instance and you dont have to deal with this problem so much anymore
here is a list of public instances:
https://searx.space
here are the ones i frequently use:
https://searx.bndkt.io/
https://search.nerdvpn.de/
https://cia.govt.hu/searxng/
https://searxng.ru/