Package Details: searx 1.0.0-2

Git Clone URL: (read-only, click to copy)
Package Base: searx
Description: A privacy-respecting, hackable metasearch engine (python(3) based)
Upstream URL:
Licenses: AGPL
Conflicts: searx-git
Replaces: searx-py3
Submitter: Jake
Maintainer: Jake
Last Packager: Jake
Votes: 29
Popularity: 4.40
First Submitted: 2016-09-07 11:42
Last Updated: 2021-05-12 19:43

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Jake commented on 2021-05-12 19:43

@stef204: Yes, I get this too and have added the cache config now to searx.ini (pkgrel=2).

stef204 commented on 2021-05-12 16:05

@Jake. thanks for your helpful feedback. my mistake: i was running it via systemctl start emperor.uwsgi.service probably causing the warning.

i've now used systemctl start uwsgi@searx.service and am getting this now, namely:

ERROR:searx.shared:uwsgi.ini configuration error, add this line to your cache2 = name=searxcache,items=2000,blocks=2000,blocksize=4096,bitmap=1

Edit: if I add the whole line: cache2 = name=searxcache,items=2000,blocks=2000,blocksize=4096,bitmap=1 to /etc/uwsgi/emperor.ini the error/warning disappears.

Jake commented on 2021-05-12 15:01

@stef204: searx.ini contains uid = searx and gid = searx in both packages. In my testing this switches the user/group as expected. The journal then contains:

Mai 12 16:32:40 pc-arch uwsgi[144997]: setgid() to 982
Mai 12 16:32:40 pc-arch uwsgi[144997]: setuid() to 982

and no warnings. 982 is the ID of the searx user on my system. All 5 processes (1 master + 4 workers) run under searx not root.

Did you run it with systemctl start uwsgi@searx.service? Have you possibly edited searx.ini (removed the uid/gid lines)?

btw: The flask update issue is now solved by:

stef204 commented on 2021-05-12 14:27


curious to know what your take is on the comment I posted on the git version regarding upstream install instructions which applies to this package as well:

basically, this warning

Jake commented on 2021-05-10 12:05

@tbh: Depends on what you are doing with it. The log contains HTTP requests (like most webservers by default). There is no privacy impact if it is used only locally, as all requests come from localhost obviously.

If it runs directly as public instance then it makes sense to not log public IPs of the users. In this case the config should be adjusted anyway (setup TLS, more workers, etc), that is why the comments are there to help with the configuration. Also there would be most likely a reverse proxy, and logging configured/disabled just there:

tbh commented on 2021-05-10 09:19

I notice in searx.ini it has

# disable logging for privacy disable-logging = false

Should this be true or is the comment wrong?

gee commented on 2021-03-28 11:17

Thanks for the quick change, but you forgot to change it in the source as well. :)

gee commented on 2021-03-28 10:54


While the redirect works fine, I think it'd be clearer to switch the address to searx instead of asciimoo. Thanks!

laichiaheng commented on 2021-03-28 07:45

1.0.0 is released!

Jake commented on 2020-12-04 12:11

Hi @Malah, thanks for info, I have added it now. Should trigger a rebuild for py 3.9 anyway.

In addition I have added a patch to fix the google engine.