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

Engines silently fail? #1883

Open
geckolinux opened this issue Mar 5, 2020 · 7 comments
Open

Engines silently fail? #1883

geckolinux opened this issue Mar 5, 2020 · 7 comments

Comments

@geckolinux
Copy link

@geckolinux geckolinux commented Mar 5, 2020

Hi there, it appears that many times certain engines silently fail? For example, I enable DuckDuckGo and Mojeek and Startpage in addition to Google, but on many instances it only returns Google results, even when the query is very easy. For example, on two different instances with the exact same engines enabled:

Screenshot_20200305_094613


Screenshot_20200305_094548

@unixfox

This comment has been minimized.

Copy link
Contributor

@unixfox unixfox commented Mar 5, 2020

I can replicate the same bug and this started only one/two months ago for a reason that I don't know. The error message is still displayed in the logs though.

@return42

This comment has been minimized.

Copy link
Collaborator

@return42 return42 commented Mar 5, 2020

I "feel" sometimes the same .. when I dig deeper, mostly it is about timeouts. But it was not really clear because the experiences a very divergent and mostly my time was limited. It is hard to dig, e.g. the bing_video was very buggy because the rotating user-agent signatures we use (#1882).

Do you have any more precise information that might clarify the dust a bit more for me?

The error message is still displayed in the logs though.

What error message?

@unixfox

This comment has been minimized.

Copy link
Contributor

@unixfox unixfox commented Mar 5, 2020

The error message is still displayed in the logs though.

What error message?

Depends on the engine, if it's Google then it's CAPTCHA error or if another instance like torrentz2 it's 503 error.

@return42

This comment has been minimized.

Copy link
Collaborator

@return42 return42 commented Mar 5, 2020

Please don't mix the CAPTCHA error with experience @geckolinux describes .. the solution for CAPTCHA is definitely filtron! Since I use filtron and after a short time of tare the filter rules I have no more google CAPTCHA error seen (since 2 month).

@unixfox

This comment has been minimized.

Copy link
Contributor

@unixfox unixfox commented Mar 5, 2020

I'm not talking about that specific CAPTCHA error... but about the error that should be displayed on the user screen rather than just in the logs of the owner of the searx instance.

@return42

This comment has been minimized.

Copy link
Collaborator

@return42 return42 commented Mar 5, 2020

if another instance like torrentz2 it's 503 error.

When I have no results for some engines I do not see any error message .. I guess that is also what @geckolinux addressed.

@return42 return42 closed this Mar 5, 2020
@return42 return42 reopened this Mar 5, 2020
@return42

This comment has been minimized.

Copy link
Collaborator

@return42 return42 commented Mar 5, 2020

but about the error that should be displayed on the user screen rather than just in the logs of the owner of the searx instance.

ah, ok, thanks for clarify .. and sorry that I hit the close button :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.