Hi there, not sure if this is an issue with SearX or with the Disroot configuration of the instance, but it appears that some of the engines silently fail. You can see screenshots of the problem here:
These are the engines I always enable:
Thanks a lot for the help and for running your instance of SearX!
Thanks I see someone already confirmed it to be issue on his instance too, so I will bookmark/follow that thread on github. Thanks for reporting.
Great, thanks a ton for looking into it!