Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No search results on searx.me and other instances #1780

Open
scroom opened this issue Dec 20, 2019 · 4 comments
Open

No search results on searx.me and other instances #1780

scroom opened this issue Dec 20, 2019 · 4 comments

Comments

@scroom
Copy link

@scroom scroom commented Dec 20, 2019

Hallo,
i run my own searx instance (searx.site) and was happy with it for a long time. However, for some time now I have not been getting any search results. I then checked if this is elsewhere and tested e.g. searx.me. But also here I get de facto no more search results displayed. Have the search engine operators changed their settings? (allowed number of requests, permanent blocking of IPs from which many requests come?)

@ParadiseStudios

This comment has been minimized.

Copy link

@ParadiseStudios ParadiseStudios commented Dec 21, 2019

Same problem for me. My private local instance is almost worthless now as you have to keep clicking Search until it finally returns results. When it does eventually work, the only search results that come back are from Bing. I tried searx.me and it was the same way. I don't know where the log file is on Debian 10, so I can't check it for errors. I get the feeling the search engines are changing things on the backend and a lot of code will have to be rewritten. Sad.

@unixfox

This comment has been minimized.

Copy link
Contributor

@unixfox unixfox commented Dec 21, 2019

Which engine do you guys use? If that's Google did you update to the latest version/commit of Searx because a big change was made in the code for that engine: #1628

@ParadiseStudios

This comment has been minimized.

Copy link

@ParadiseStudios ParadiseStudios commented Dec 21, 2019

I tried that fix (https://github.com/MarcAbonce/searx/blob/ccaf6ca02c5bdc63f78e01a66429afaa5fb3cb68/searx/engines/google.py) and also this one: https://github.com/asciimoo/searx/blob/8f51430f5c64e23dba0d518064d4972efec7fe83/searx/engines/google.py for Google but it didn't work so I turned Google off.

All the engines that kept timing out I have turned off, so only Bing is on now. Bing's results are lacking compared to the ones Google turned up. I used to use duckduckgo as a replacement for google results but duckduckgo is temporarily blocked at my ISP level it seems now, so I had to turn that one off too.

@unixfox

This comment has been minimized.

Copy link
Contributor

@unixfox unixfox commented Dec 21, 2019

After playing with the engine settings I came to the conclusion that bing, ddg and yandex are not working. Apart from that Google is working fine (if you aren't blocked by their captcha), yahoo too, startpage also and probably the other engines too.

I think these engines are blocking the requests because sometimes I get results from yandex , ddg and bing due to the fact that on searx.be the requests are rotated between multiple instances (5 in total).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.