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
Qwant gibberish results #2563
Comments
Sure you installed SearXNG and not searx? |
@return42 it says "Powered by searxng - 1.0.0 - ..." |
👍
Sorry, I do not have experience with nixos .. package search shows me: In the nixos package repo I see commit da7c302 is used for the package build .. not sure how instance updates do work in nixos but SearXNG is a rolling release .. the deployment tool is git / git needs to be installed on the target host (I don't see a git requirement in the SearXNG package definitions of nixos). To summarize: with nixos I can't help, but may be @SuperSandro2000, @999eagle or @nagy can help. Additional I'm confused by this ...
In a SearXNG docker installation you see version 1.0.0? May be should focus on one installation method / we from SearXNG team prefer to use one of the official installation methods. |
Before jumping on nixos I used searxng in docker, and had it running in docker HOLD ON |
@return42 Packages on NixOS should be reproducible, so we build SearXNG from a specific commit (da7c302 currently for the unstable branch as you've already seen yourself). Automatic upgrades to newer commits can't happen as packages, once built, are immutable. |
@999eagle thanks for clarify 👍
with the hint from @999eagle and the hint that the results in docker are not better either, I suspect that the problem is outside the SearXNG installation.
SearXNG uses the qwant's api: searxng/searx/engines/qwant.py Line 70 in a446dea
searxng/searx/engines/qwant.py Lines 99 to 100 in a446dea
When you send a API request from the IP of the SearXNG instance, do you get reasonable results for: |
We are just missing a step and the fallback version here is used https://github.com/searxng/searxng/blob/master/searx/version.py#L11-L16 The file is generated from Line 119 in a446dea
@999eagle could you do a PR to include version and some dummy information for the git things? That would be awesome. |
@SuperSandro2000 @999eagle : from #229 ... It is possible to call It is useful when the code is install outside git (distro package, docker, etc...) |
|
@xxxcrow Yeah, seems gibberish what you got from qwant ..
just wondering that qwant responses gibberish on requests from Vietnam (14.177.55.154 / Ha Noi) The only solution I see is to proxy the outgoing request or get an IP that is not located in a region qwant (for whatever reasons) dislike. Related:
|
I've opened NixOS/nixpkgs#244473 to include the frozen version and update to current master. |
@999eagle: Thanks 👍 I placed a comment NixOS/nixpkgs#244473 .. the nixos discussion should be continued in your PR. @xxxcrow: the issue you have is related to the qwant service itself .. see my comment from above #2563 (comment) --> I'm going to close this github issue. |
Version of SearXNG, commit number if you are using on master branch and stipulate if you forked SearXNG
I'm using nixos, and not sure how to get the version
At the bottom of the page it says 1.0.0
How did you install SearXNG?
Nixos, but the problem persisted in docker too
What happened?
Qwant search results are complete gibberish that lead to nonexistent websites
How To Reproduce
Search for anything
Expected behavior
Qwant gives English results
Screenshots & Logs
And it's not just one result, it's many of them
Even more if you search for something less searchable
The text was updated successfully, but these errors were encountered: