SearxNG not starting until restarting the service #5267
nooby-in-trouble
started this conversation in
General
Replies: 2 comments
-
|
I don't know why this issue was converted to a discussion, I hope that if someone has the same problem as me can find the solution. The user searxng_bridged was ther first who gave me the idea of commenting the engine apart from disabling it with the setting. And that worked for me. So it seems like even if the engine is disabled, SearxNG does some work to load it (and then disables it) that in my case didn't work. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi, same issue here but I run the update script after a reboot, with 30 second delay, and that does it for me ;-) //Anders |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Version of SearXNG, commit number if you are using on master branch and stipulate if you forked SearXNG
Commit 3bf7024, 23 september of 2025
SO: Linux 6.1.0-40-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64 GNU/Linux
How did you install SearXNG?
I installed SearxNG a few years ago using the installation script from the official wiki.
What happened?
I my instance is private and for personal use only, so I don't update it frequently, I updated after some months to that version prevoiusly specified, and now SearxNG does not start properly.
When I turn on my computer, SearxNG starts, but it doesn't work. The error I get from the browser is error code 500, with the text from uWSGI:«Internal Server Error». If then I exec from the terminal:
sudo systemctl restart uwsgiAnd reload the page, then all goes well, the bug disappears.
How To Reproduce
Installing SearxNG from the installation script, and turning on the computer with SearxNG activated from start (which does it automatically, I think).
Expected behavior
No http error code if I don't manually restart the service.
Screenshots & Logs
Here I show some part of the log of uWSGI (located in /var/log/uwsgi/app/searxng.log) when the bug is produced:
I don't have anything like an SQL database installed, I don't use nor redis, nor valkey, nor morty. My instance is kept minimal for my personal use.
The surprising fact is that I have the currencies engine disabled in my config.yml, so it should not provoke any bug. That idea was suggested by the user searxng_bridged in the Libera chat a few days ago.
Additional context
Nothing more.
Beta Was this translation helpful? Give feedback.
All reactions