You mean the one in dockerfiles/? I don't use docker, just a regular installation. The documentation mentions /etc/uwsgi.ini but there is no file there. Is there any other place I should look into?

That there isn't a uwsgi.ini file suggests the problem: There needs to be one for uwsgi to know what to do.

Here's what mine looks like:

[uwsgi]
workers = 12
single-interpreter = true
master = true
plugin = python
lazy-apps = true
enable-threads = true
module = searx.webapp
virtualenv = /home/virtadpt/searxng/env/
pythonpath = /home/virtadpt/searxng/
chdir = /home/virtadpt/searxng/searx/
http = 127.0.0.1:8888
disable-logging = true
route-run = fixpathinfo:
cache2 = name=searxcache,items=2000,blocks=2000,blocksize=4096,bitmap=1

In a shell script (because I use a venv with SearxNG and systemd) I have the command `uwsgi --ini searxng.ini to start it up.

It sounds like you hit a deficiency in the docs. I set this up so long ago I don't remember the specifics, but I do recall building the .ini file out little by little until I had something that works.

Hello, I installed SearXNG after wiping out my old installation. I used the installation script.

By default, the script installs uWSGI which listens on a socket ..

INFO:  uWSGI socket is located at: /usr/local/searxng/run/socket

Here's the curl --location --verbose --head --insecure 127.0.0.1:8888 output:

Since it is listen on socket, this won't work ..

INFO:  got 301 from http://user/searxng

This URL does not exists .. you need to setup a HTTP server to proxy to the socket.

https://docs.searxng.org/admin/installation-scripts.html

If you prefer NGINX use ..

the script from above will install the proxy:

In your network, the SearXNG instance should be available under:

http://<hostname>/searxng

Thanks but the documentation says:

When all services are installed and running fine, you can add SearXNG to your HTTP server.

How do I check if they are running fine then? There is no information about it in the documentation. Furthermore, if I get 301, they are obviously not running fine, are they? That part of the documentation is just badly written then.

Just below that it says:

We use caddy in our docker image and we have implemented installation procedures for

Correct me if I'm wrong but if someone uses the installation script, it's obvious they are not using a docker image, is it? What's the point of that information then? To me it implies that the installation procedures are for docker images, not for me.

Correct me if I'm wrong but if someone uses the installation script, it's obvious they are not using a docker image, is it? What's the point of that information then? To me it implies that the installation procedures are for docker images, not for me.

Hm, now when you say it I realized it .. yes, sorry it is misleading .. fixes are welcome.

How do I check if they are running fine then?

Your "SearXNG checks" does not report an issue .. so everything seems fine so far.

Furthermore, if I get 301, they are obviously not running fine, are they?

INFO:  uWSGI socket is located at: /usr/local/searxng/run/socket
INFO:  got 301 from http://user/searxng

Understand the 301 as a request that HTTP must be installed.

It might be a bit confusing at this point of the installation procedure that http is tested before installed .. everything can be improved .. fixes are welcome.