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

All searx instances have been bust for weeks (it seems) #1584

Open
PFCS1976 opened this issue May 7, 2019 · 5 comments

Comments

Projects
None yet
4 participants
@PFCS1976
Copy link

commented May 7, 2019

No matter which searx instance I use, they respond to 90% of searches with "error...unexpected crash/captcha required"
This has been going on for 2-3 weeks and so far as I can tell no-one is making any effort to fix it

@SeymourHiney

This comment has been minimized.

Copy link

commented May 9, 2019

Have the same problem. It started out only happening some times and now Searx defaults to crash/captcha on every search so it is unusable as a search engine.

@x250

This comment has been minimized.

Copy link

commented May 12, 2019

You can try searching for Searx instances that aren't listed on the project's wiki. They should typically work without any issues.

@unixfox

This comment has been minimized.

Copy link

commented May 17, 2019

It's unfortunately because of abuse made by bots (see #543 and #729 for more details).
I had this same issue with Google on my instance (https://searx.be) but I found some ways to block most of the bots and now it's working fine my instance is not blocked by Google anymore.

@SeymourHiney

This comment has been minimized.

Copy link

commented May 17, 2019

Unixfox, would you mind elaborating how to do this....if your methods will work on Windows.

@unixfox

This comment has been minimized.

Copy link

commented May 17, 2019

@SeymourHiney You are asking me what I've done to my instance for you to replicate it on your Searx instance hosted on Windows?
If that's the case I pretty much only changed the search URL to a nontraditional URL and blocked every request made to the native/previous/classic search URL (POST request on the root / of the domain). By applying this trick I knew I would mostly only receive requests from a real browser.
But I'm working on a plugin for the web server Caddy (available on Windows too) that will block 99% of the bots with a simple trick, the plugin will be open sourced on GitHub when it's done.

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