[Freedombox-discuss] Problems with searx

A. F. Cano afc54 at comcast.net
Sat Dec 28 00:00:53 GMT 2019


>From multiple internal machines:

Once the searx screen is displayed and I put something in the search
field, after hitting <CR> quite ofben I get:

Sorry! we didn't find any results.  Please use another query or search
in more categories.

If I try again and again, eventually I get the search results page to
display, but it sometimes takes 5, 6 ot 7 tries.

>From a brand new installation of Debian stable, totally up to date:

Using Konqueror, if I use the back button after a results page has been
displayed, instead of displaying the searx search field, with the
previosly entered search, as happens in firefox, I only get a blank
page.  The only way to get bach the searx home page is to reload, but
this causes the search text to be wiped out so I have to re-type it.
Highly inconvenient.  In Firefox, this works as expected: I see the
searx home page with the previously entered search text that I can then

Using Firefox, accessing searx works fine if I have Firefox set to no
proxy.  If I set it to manually configured proxy pointing to the
freedombox (port 8118) I get an error page that says:

Mmm. We're having trouble finding that site. We can't connect to the
server at fbx.  If that address is correct, here are three other things
you can try:

o Try again later.
o Check your network connection.
o If you are connected but behind a firewall, check that Firefox has
  permission to access the web.

Fbx is the name of the freedombox in the local network, all static
addresses specified in /etc/hosts.  I connect to https://fbx/searx.

After searching for possible solutions found the obscure Firefox

network.dns. disableIPv6

but changing those don't fix the problem (false by default)

Clearing the whole history doesn't help either.

Are these problems fixable in FreedomBox? Are there any workarounds?
Has anyone else encountered these issues?



More information about the Freedombox-discuss mailing list