We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Version of SearXNG, commit number if you are using on master branch and stipulate if you forked SearXNG
2024.6.17+accc1c103 (9f4de22) in https://searx.tiekoetter.com
How did you install SearXNG? I don't own the instance.
What happened? A search for something with one result (EXAMPLE) bring up 10 pages at the bottom, 9 of them are empty
How To Reproduce
Expected behavior Find one link or none at all
Screenshots & Logs
No access to logs
The text was updated successfully, but these errors were encountered:
This seems to be a problem affecting all SearXNG instances. Please report it here: https://github.com/searxng/searxng/issues
Sorry, something went wrong.
Thanks! Do I have to close this issue here?
You can keep it open until it is either fixed upstream or I will take a look at it.
It's already closed upstream.
No branches or pull requests
Version of SearXNG, commit number if you are using on master branch and stipulate if you forked SearXNG
2024.6.17+accc1c103 (9f4de22)
in https://searx.tiekoetter.com
How did you install SearXNG?
I don't own the instance.
What happened?
A search for something with one result (EXAMPLE) bring up 10 pages at the bottom, 9 of them are empty
How To Reproduce
Expected behavior
Find one link or none at all
Screenshots & Logs
![error](https://private-user-images.githubusercontent.com/170770027/341224264-217f10b7-ba98-4a89-8e33-9909ae09ed41.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE5MDU1MTgsIm5iZiI6MTcyMTkwNTIxOCwicGF0aCI6Ii8xNzA3NzAwMjcvMzQxMjI0MjY0LTIxN2YxMGI3LWJhOTgtNGE4OS04ZTMzLTk5MDlhZTA5ZWQ0MS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzI1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcyNVQxMTAwMThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mMWNhNTdkMGZkYmY3N2YwZWQ4YWQwMmFkZTBjZTA2YTg5ZDdmYTlhMGNhZTMwMjIxNjg4M2RmOTVhODJjNGE4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.l_u5TtwEJaC5bA6QtaAZvqjuz6AhCjD__gaH5EsMA7Y)
No access to logs
The text was updated successfully, but these errors were encountered: