After installing with script nothing running at http://127.0.0.1:8888 #6455

mat1gom · 2026-07-26T17:13:28Z

mat1gom
Jul 26, 2026

I tried to install with the script method on kubuntu 26.04. Had a trouble similar to this at the fist try #1669 and solved it with "chmod o+x /home/user" as suggested. Then the scrip was run completely without errors. After that i tried to open the app on the browser (i had to search outside the installation guide what was the address) and only see "can't connect" messages no matter the browser i use.
Edit: I just noticed this link https://docs.searxng.org/admin/update-searxng.html#inspect-searxng then run the "sudo -H ./utils/searxng.sh instance inspect" command and got all this on console:

$ sudo -H ./utils/searxng.sh instance inspect
[sudo: authenticate] Password:

Inspect SearXNG instance
========================

INFO:  wrapper:  utils/searxng.sh instance _call _searxng.instance.inspect
uWSGI:
  SEARXNG_UWSGI_SOCKET : /usr/local/searxng/run/socket
environment:
  GIT_URL              : https://github.com/searxng/searxng
  GIT_BRANCH           : master
  SEARXNG_URL          : http://computeri/searxng
  SEARXNG_PORT         : 8888
  SEARXNG_BIND_ADDRESS : 127.0.0.1
INFO:  uWSGI socket is located at: /usr/local/searxng/run/socket
ERROR: Public service at http://mati-mini/searxng is not available!
[CTRL-C] to stop or [KEY] to continue

Enable SearXNG debug mode? [NO/yes] Y
WARN:  Do not enable debug in a production environment!
INFO:  try to enable debug mode ...
cd /usr/local/searxng/searxng-src
sed -i -e "s/debug: false/debug: true/g" "/etc/searxng/settings.yml"
INFO:  restart uWSGI service

● uwsgi.service - LSB: Start/stop uWSGI server instance(s)
     Loaded: loaded (/etc/init.d/uwsgi; generated)
     Active: active (running) since Sun 2026-07-26 19:26:13 CEST; 23ms ago
 Invocation: 888f89c4ac9c4ca4aa45dba30d87183e
       Docs: man:systemd-sysv-generator(8)
    Process: 14153 ExecStart=/etc/init.d/uwsgi start (code=exited, status=0/SUCCESS)
      Tasks: 273 (limit: 34100)
     Memory: 82.6M (peak: 82.8M)
        CPU: 518ms
     CGroup: /system.slice/uwsgi.service
             ├─14255 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14263 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14264 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14269 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14283 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14300 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14316 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14350 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14371 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14392 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14407 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14423 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14442 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14460 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14476 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             ├─14494 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log
             └─14506 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searxng.ini --daemonize /var/log/uwsgi/app/searxng.log

jul 26 19:26:13 mati-mini systemd[1]: Starting uwsgi.service - LSB: Start/stop uWSGI server instance(s)...
jul 26 19:26:13 mati-mini uwsgi[14153]:  * Starting app server(s) uwsgi
jul 26 19:26:13 mati-mini uwsgi[14153]:    ...done.
jul 26 19:26:13 mati-mini systemd[1]: Started uwsgi.service - LSB: Start/stop uWSGI server instance(s).
// use CTRL-C to stop monitoring the log

    return self.patch_response(response, do_raise_for_httperror)
           ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/searxng/searxng-src/searx/network/network.py", line 256, in patch_response
    raise_for_httperror(response)
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/local/searxng/searxng-src/searx/network/raise_for_httperror.py", line 76, in raise_for_httperror
    raise SearxEngineAccessDeniedException(message='HTTP error ' + str(resp.status_code))
searx.exceptions.SearxEngineAccessDeniedException: HTTP error 403 (suspended_time=180)
ERROR   searx.searx.search.processor  : (PID 14442) wikidata: engine init was not successful
ERROR   searx.search.processors       : (PID 14442) wikidata: can't register engines processor (init engine failed)

Answered by mat1gom

Jul 27, 2026

Ok after some research i figured out that the script doesn't configure searxng to work properly so i had to take 3 steps:

sudo nano /etc/uwsgi/apps-enabled/searxng.ini
Comment this line: socket = /usr/local/searxng/run/socket and substitute it with http = 127.0.0.1:8888
sudo systemctl restart uwsgi

and now it works.
Can somebody please explain me why that file isn't configured that way by default?

View full answer

mat1gom · 2026-07-27T02:16:38Z

mat1gom
Jul 27, 2026
Author

Ok after some research i figured out that the script doesn't configure searxng to work properly so i had to take 3 steps:

sudo nano /etc/uwsgi/apps-enabled/searxng.ini
Comment this line: socket = /usr/local/searxng/run/socket and substitute it with http = 127.0.0.1:8888
sudo systemctl restart uwsgi

and now it works.
Can somebody please explain me why that file isn't configured that way by default?

5 replies

return42 Jul 28, 2026
Maintainer

Because it uses sockets by default.

mat1gom Jul 28, 2026
Author

Because it uses sockets by default.

I know now but that doesn't fully answer my question. What vast majority of users expect after installing an app is that app to just work, not to have to make tweaks to have it working. I mean the default behavior should be that the app is ready for users. If network admins want to set up this as a local service on one machine THAT should be the optional tweaking, don't you agree?
Even worst than that, the tweak necessary to make the app work after running the script isn't even mentioned in the documentation, i had to research it and figured it out by myself.

return42 Jul 29, 2026
Maintainer

Even worst than that, the tweak necessary to make the app work after running the script isn't even mentioned in the documentation, i had to research it and figured it out by myself.

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

One single page and you haven't read to the end?

mat1gom Jul 30, 2026
Author

Of course i did read that, but perhaps you didn't read MY message. The text you quoted say "you can add SearXNG to your HTTP server" but if i'm a user, not a network admin then i DON'T have an http server, i don't want one and, you know what? i don't need one because the app could just work for normal USERS just by changing a line in searxng.ini
Are you making a tool for all users or just for network admins?
Are you aware most of the people that want to use SearXNG are not network admins?
In any case you could make the tool for both if the default behavior is that the tool just work for users after installing and the tweak for network admins is documented. Right now the situation is the tool is configured by default for network admins and documented for them. The users who want to simply use the tool in their computers WITHOUT an unnecessary web server don't have any clue on how to do it in the whole documentation.
I can't understand this situation unless somebody have some strange interest in people installing unnecessary web servers in their computers.

return42 Jul 30, 2026
Maintainer

Are you aware most of the people that want to use SearXNG are not network admins?

Installation of SearXNG is a complex task, not for end users!

https://searx.space/

Navigation Menu

Repository navigation

After installing with script nothing running at http://127.0.0.1:8888 #6455

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 5 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

After installing with script nothing running at http://127.0.0.1:8888 #6455

Uh oh!

Uh oh!

mat1gom Jul 26, 2026

Replies: 1 comment · 5 replies

Uh oh!

mat1gom Jul 27, 2026 Author

Uh oh!

return42 Jul 28, 2026 Maintainer

Uh oh!

mat1gom Jul 28, 2026 Author

Uh oh!

return42 Jul 29, 2026 Maintainer

Uh oh!

Uh oh!

mat1gom Jul 30, 2026 Author

Uh oh!

return42 Jul 30, 2026 Maintainer

mat1gom
Jul 26, 2026

Replies: 1 comment 5 replies

mat1gom
Jul 27, 2026
Author

return42 Jul 28, 2026
Maintainer

mat1gom Jul 28, 2026
Author

return42 Jul 29, 2026
Maintainer

mat1gom Jul 30, 2026
Author

return42 Jul 30, 2026
Maintainer