Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] kilrah/searxng

Featured Replies

It seems lots of changes breaking this container on the regular with every reboot.

I ended up setting the repository to a known good for now:
searxng/searxng:2026.6.13-a29cda858

I also kept losing my Flask session signing key for cookies from my settings.yml file so I added the environment variable (type Variable)
Name SEARXNG_SECRET
Key SEARXNG_SECRET
Value Paste in my ultrasecretkey from settings.yml

Click Apply.

Hopefully this will prevent future config merges from breaking startup and resetting my key.

  • 3 weeks later...
  • Replies 54
  • Views 26.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • plantsandbinary
    plantsandbinary

    Alright seeing as I have to do everything myself to get this container working properly and without any error spam etc.   I've done the following and until the maintainer of this container d

  • @Kilrah   BINGO!   That fixed it. Running on port 80!   Thx very much for the tip!

  • I'm not sure what was wrong, I couldn't get this to work all day yesterday, woke up this morning and now it works. Thank you again.

Posted Images

Upgraded to UnRAID 7.3.1, and it no longer starts. Any ideas?

TypeError: Unexpected keyword argument 'requires_api_key'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):

File "/usr/lib/python3.14/multiprocessing/process.py", line 320, in _bootstrap

self.run()

~~~~~~~~^^

File "/usr/lib/python3.14/multiprocessing/process.py", line 108, in run

self._target(*self._args, **self._kwargs)

~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/searxng/.venv/lib/python3.14/site-packages/granian/server/mp.py", line 90, in wrapped

callback = callback_loader()

File "/usr/local/searxng/.venv/lib/python3.14/site-packages/granian/_internal.py", line 65, in load_target

module = load_module(path)

File "/usr/local/searxng/.venv/lib/python3.14/site-packages/granian/_internal.py", line 47, in load_module

import(module_name)

~~~~~~~~~~^^^^^^^^^^^^^

File "/usr/local/searxng/searx/webapp.py", line 1407, in <module>

init()

~~~~^^

File "/usr/local/searxng/searx/webapp.py", line 1379, in init

searx.search.initialize(check_network=True, enable_metrics=metrics)

~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/searxng/searx/search/__init__.py", line 39, in initialize

load_engines(settings_engines)

~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^

File "/usr/local/searxng/searx/engines/__init__.py", line 321, in load_engines

engine = load_engine(engine_data)

File "/usr/local/searxng/searx/engines/__init__.py", line 141, in load_engine

update_engine_attributes(engine, engine_data)

~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/searxng/searx/engines/__init__.py", line 200, in update_engine_attributes

raise TypeError(

f"engine '{engine_data['name']}' ({engine_data['engine']}) - in the about section --> {exc}"

) from exc

TypeError: engine 'gpodder' (json_engine) - in the about section --> Unexpected keyword argument 'requires_api_key'

[ERROR] Unexpected exit from worker-1

[INFO] Shutting down granian

[INFO] Stopped worker-1

[INFO] Granian shutdown completed, see ya!

  • Author

See the last few posts, searxng has recently changed stuff that requires adapting your config files.

I can also Confirm with @House Of Cards Receiving same error during docker start. Thank you @Kilrah for your work maintaining docker container!

Recently my instance of SearXNG stopped working. Every time it does a search, it changes the user to 977:977, which makes it impossible for SearXNG to access the files in the appdata folder. When I change it back to 99:100 I can do exactly one succesful search before it changes itself back to 977:977 again and it's unable to search.

Someone suggested adding --user 977:977 to extra parameters of the docker container. I did, and now my docker container has disappeared. I can't even find it with Portainer.

What is going on? How do I get my container back? And how can I make it function again without constantly switching users to 977?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.