After resetting my Start9 and then doing a hard reset, I can access most services except SearXNG (search error on anything typed in) and Vault Warden (This Site can’t be reached). I have cleared cookies and browsing history but no success. This is after months of being able to successfully access both sites on the same install. Thank you!
Running Start OS v.0.3.5-1 trying to access it from a Brave Browser on Linux Ubuntu.
Please tell me more about the circumstances around the issue. Why were you resetting your server, and then doing a hard rest? What was the original issue, that did not allow for a proper shutdown from the system menu?
Everything worked yesterday. I woke up today and could not access the server at all. There didn’t appear to be a power outage overnight but the Start9 would only show a yellow access screen that a hard refresh didn’t fix. This was on two computers. So, I unplugged it and plugged it back in. Then, I logged back in and did a hard reset. Everything is accessible except those two services.
Please tell me what you mean by “hard reset.” after logging in. Are you referring to the ctrl shift r in the browser, hard refresh?
Yes, sir. That is it. Y’all taught me that early on.
One clarification on Vault Warden, the error also says that the .local address “unexpectedly closed the connection.” That may help you to diagnose it further. Thank you so much!
Let’s minimize and focus on Vaultwarden. Please log in to your server, and stop all services. Then restart the server. System>Restart. After the server reboots, start Vaultwarden. Wait for the health check to turn green, then test access to it from the device.
Rexter, I didn’t even think about doing that. Actually, just stopping and restarting Vaultwarden fixed the problem without having to interrupt any of the other services. However, doing that to SearXNG didn’t fix that error so I stopped each service and did the restart. That did not fix SearXNG, the same error shows up.
Okay, great. So the issue with Vault warden is resolved?
Let’s focus on SearXNG then. Let’s stop all services, and then restart your server.
System>Restart
Then start SearXNG, and wait for the health checks to turn green.
Rexter, I did that but the same error is showing up on SearXNG. Vault Warden now functions normally.
After the reset, following are the logs for SearXNG:
2026-06-24T13:57:49-04:00 2026-06-24 17:57:49,003 ERROR:searx.webapp: ‘wikidata’
2026-06-24T13:57:49-04:00 Traceback (most recent call last):
2026-06-24T13:57:49-04:00 File “/usr/local/searxng/searx/webapp.py”, line 651, in search
2026-06-24T13:57:49-04:00 result_container = search_obj.search()
2026-06-24T13:57:49-04:00 ^^^^^^^^^^^^^^^^^^^
2026-06-24T13:57:49-04:00 File “/usr/local/searxng/searx/search/_init_.py”, line 204, in search
2026-06-24T13:57:49-04:00 super().search()
2026-06-24T13:57:49-04:00 File “/usr/local/searxng/searx/search/_init_.py”, line 178, in search
2026-06-24T13:57:49-04:00 self.search_standard()
2026-06-24T13:57:49-04:00 File “/usr/local/searxng/searx/search/_init_.py”, line 164, in search_standard
2026-06-24T13:57:49-04:00 requests, self.actual_timeout = self._get_requests()
2026-06-24T13:57:49-04:00 ^^^^^^^^^^^^^^^^^^^^
2026-06-24T13:57:49-04:00 File “/usr/local/searxng/searx/search/_init_.py”, line 91, in _get_requests
2026-06-24T13:57:49-04:00 processor = PROCESSORS[engineref.name]
2026-06-24T13:57:49-04:00 ~~~~~~~~~~^^^^^^^^^^^^^^^^
2026-06-24T13:57:49-04:00 KeyError: ‘wikidata’
Are you saying the health checks are green?
Yes, the health checks are green. But the above is the log for the errors. This service worked over the weekend and I’m not sure what happened.
Just for kicks, I uninstalled SearXNG and reinstalled. Same error.
Hello. I have tried troubleshooting the SearXNG error today but to no avail. I uninstalled and reinstalled it, then stopped all services and restarted the Start9. Health Check for SearXNG is green. Following is the log file that is produced and all that happens in the browser is a red “Search Error” bar at the top:
2026-06-27T15:47:21-04:00
2026-06-27T15:47:21-04:00
2026-06-27T15:47:21-04:00 [i] Starting Valkey …
2026-06-27T15:47:21-04:00 done!
2026-06-27T15:47:21-04:00
2026-06-27T15:47:21-04:00 [i] Starting SearXNG …
2026-06-27T15:47:21-04:00
2026-06-27T15:47:21-04:00 SearXNG 2025.10.15-576d30ffc
2026-06-27T15:47:21-04:00 58:M 27 Jun 2026 19:47:21.571 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see vm.max_map_count growing steadily when vm.overcommit_memory is 2 · Issue #1328 · jemalloc/jemalloc · GitHub . To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
2026-06-27T15:47:21-04:00 58:M 27 Jun 2026 19:47:21.571 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
2026-06-27T15:47:21-04:00 58:M 27 Jun 2026 19:47:21.571 * Valkey version=8.1.4, bits=64, commit=00000000, modified=0, pid=58, just started
2026-06-27T15:47:21-04:00 58:M 27 Jun 2026 19:47:21.571 * Configuration loaded
2026-06-27T15:47:21-04:00 58:M 27 Jun 2026 19:47:21.571 * monotonic clock: POSIX clock_gettime
2026-06-27T15:47:21-04:00 58:M 27 Jun 2026 19:47:21.572 * Running mode=standalone, port=6379.
2026-06-27T15:47:21-04:00 58:M 27 Jun 2026 19:47:21.572 * Server initialized
2026-06-27T15:47:21-04:00 58:M 27 Jun 2026 19:47:21.572 * Ready to accept connections tcp
2026-06-27T15:47:21-04:00 58:M 27 Jun 2026 19:47:21.572 * Ready to accept connections unix
2026-06-27T15:47:22-04:00 [INFO] Starting granian (main PID: 59)
2026-06-27T15:47:22-04:00 [INFO] Listening at: http://:::8080
2026-06-27T15:47:22-04:00 [INFO] Spawning worker-1 with PID: 72
2026-06-27T15:47:23-04:00 2026-06-27 19:47:23,737 ERROR:searx.engines: Missing engine config attribute: “yacy images.base_url”
2026-06-27T15:47:23-04:00 2026-06-27 19:47:23,755 WARNING:searx.search.processors: Engine of name ‘ahmia’ does not exists.
2026-06-27T15:47:23-04:00 2026-06-27 19:47:23,760 WARNING:searx.search.processors: Engine of name ‘torch’ does not exists.
2026-06-27T15:47:23-04:00 2026-06-27 19:47:23,762 WARNING:searx.search.processors: Engine of name ‘yacy images’ does not exists.
2026-06-27T15:47:23-04:00 [INFO] Started worker-1
2026-06-27T15:47:23-04:00 [INFO] Started worker-1 runtime-1
2026-06-27T15:47:23-04:00 2026-06-27 19:47:23,967 WARNING:searx.network.wikidata: HTTP Request failed: GET https://query.wikidata.org/sparql?query=
SELECT+%3Fitem+%3Fname
WHERE+{
++++{
++++++SELECT+%3Fitem
++++++WHERE+{+%3Fitem+wdt%3AP279*+wd%3AQ12132+}
++++}+UNION+{
++++++VALUES+%3Fitem+{+wd%3AP571+wd%3AP576+wd%3AP580+wd%3AP582+wd%3AP569+wd%3AP570+wd%3AP619+wd%3AP620+wd%3AP27+wd%3AP495+wd%3AP17+wd%3AP159+wd%3AP36+wd%3AP35+wd%3AP6+wd%3AP122+wd%3AP37+wd%3AP1082+wd%3AP2046+wd%3AP281+wd%3AP38+wd%3AP2048+wd%3AP400+wd%3AP50+wd%3AP170+wd%3AP57+wd%3AP175+wd%3AP178+wd%3AP162+wd%3AP176+wd%3AP58+wd%3AP272+wd%3AP264+wd%3AP123+wd%3AP449+wd%3AP750+wd%3AP86+wd%3AP577+wd%3AP136+wd%3AP364+wd%3AP212+wd%3AP957+wd%3AP275+wd%3AP277+wd%3AP348+wd%3AP840+wd%3AP1098+wd%3AP282+wd%3AP1018+wd%3AP218+wd%3AP169+wd%3AP112+wd%3AP1454+wd%3AP137+wd%3AP1029+wd%3AP225+wd%3AP274+wd%3AP1346+wd%3AP1120+wd%3AP498+wd%3AP856+wd%3AP1324+wd%3AP1581+}
++++}
++++OPTIONAL+{+%3Fitem+rdfs%3Alabel+%3Fname.+}
}
2026-06-27T15:47:23-04:00 2026-06-27 19:47:23,968 ERROR:searx.searx.search.processor: Init method of engine wikidata failed due to an exception.
2026-06-27T15:47:23-04:00 Traceback (most recent call last):
2026-06-27T15:47:23-04:00 File “/usr/local/searxng/searx/search/processors/abstract.py”, line 155, in init_engine
2026-06-27T15:47:23-04:00 init_ok = self.engine.init(eng_setting)
2026-06-27T15:47:23-04:00 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:23-04:00 File “/usr/local/searxng/searx/engines/wikidata.py”, line 803, in init
2026-06-27T15:47:23-04:00 jsonresponse = send_wikidata_query(query, timeout=20)
2026-06-27T15:47:23-04:00 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:23-04:00 File “/usr/local/searxng/searx/engines/wikidata.py”, line 156, in send_wikidata_query
2026-06-27T15:47:23-04:00 http_response = get(SPARQL_ENDPOINT_URL + ‘?’ + urlencode({‘query’: query}), headers=get_headers(), **kwargs)
2026-06-27T15:47:23-04:00 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:23-04:00 File “/usr/local/searxng/searx/network/_init_.py”, line 175, in get
2026-06-27T15:47:23-04:00 return request(‘get’, url, **kwargs)
2026-06-27T15:47:23-04:00 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:23-04:00 File “/usr/local/searxng/searx/network/_init_.py”, line 106, in request
2026-06-27T15:47:23-04:00 return future.result(timeout)
2026-06-27T15:47:23-04:00 ^^^^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:23-04:00 File “/usr/lib/python3.12/concurrent/futures/_base.py”, line 456, in result
2026-06-27T15:47:23-04:00 return self.__get_result()
2026-06-27T15:47:23-04:00 ^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:23-04:00 File “/usr/lib/python3.12/concurrent/futures/_base.py”, line 401, in __get_result
2026-06-27T15:47:23-04:00 raise self._exception
2026-06-27T15:47:23-04:00 File “/usr/local/searxng/searx/network/network.py”, line 304, in request
2026-06-27T15:47:23-04:00 return await self.call_client(False, method, url, **kwargs)
2026-06-27T15:47:23-04:00 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:23-04:00 File “/usr/local/searxng/searx/network/network.py”, line 287, in call_client
2026-06-27T15:47:23-04:00 return self.patch_response(response, do_raise_for_httperror)
2026-06-27T15:47:23-04:00 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:23-04:00 File “/usr/local/searxng/searx/network/network.py”, line 256, in patch_response
2026-06-27T15:47:23-04:00 raise_for_httperror(response)
2026-06-27T15:47:23-04:00 File “/usr/local/searxng/searx/network/raise_for_httperror.py”, line 76, in raise_for_httperror
2026-06-27T15:47:23-04:00 raise SearxEngineAccessDeniedException(message='HTTP error ’ + str(resp.status_code))
2026-06-27T15:47:23-04:00 searx.exceptions.SearxEngineAccessDeniedException: HTTP error 403 (suspended_time=86400)
2026-06-27T15:47:23-04:00 2026-06-27 19:47:23,978 ERROR:searx.search.processors: can’t register engine processor: wikidata (init failed)
2026-06-27T15:47:26-04:00 2026-06-27 19:47:26,489 ERROR:searx.botdetection: X-Forwarded-For nor X-Real-IP header is set!
2026-06-27T15:47:31-04:00 2026-06-27 19:47:31,305 ERROR:searx.webapp: ‘wikidata’
2026-06-27T15:47:31-04:00 Traceback (most recent call last):
2026-06-27T15:47:31-04:00 File “/usr/local/searxng/searx/webapp.py”, line 651, in search
2026-06-27T15:47:31-04:00 result_container = search_obj.search()
2026-06-27T15:47:31-04:00 ^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:31-04:00 File “/usr/local/searxng/searx/search/_init_.py”, line 204, in search
2026-06-27T15:47:31-04:00 super().search()
2026-06-27T15:47:31-04:00 File “/usr/local/searxng/searx/search/_init_.py”, line 178, in search
2026-06-27T15:47:31-04:00 self.search_standard()
2026-06-27T15:47:31-04:00 File “/usr/local/searxng/searx/search/_init_.py”, line 164, in search_standard
2026-06-27T15:47:31-04:00 requests, self.actual_timeout = self._get_requests()
2026-06-27T15:47:31-04:00 ^^^^^^^^^^^^^^^^^^^^
2026-06-27T15:47:31-04:00 File “/usr/local/searxng/searx/search/_init_.py”, line 91, in _get_requests
2026-06-27T15:47:31-04:00 processor = PROCESSORS[engineref.name]
2026-06-27T15:47:31-04:00 ~~~~~~~~~~^^^^^^^^^^^^^^^^
2026-06-27T15:47:31-04:00 KeyError: ‘wikidata’
Hi
Looks like his is unrelated to your StartOS install itself (health check is green because the container is up and listening, the search function is failing, not the container). Reinstalling/restarting won’t fix it since it’s an upstream/network-side issue with Wikidata’s endpoint and a SearXNG bug around uncaught engine-not-found errors.
Worth trying: disable the Wikidata engine in Settings → Engines and see if searches work again. It may also clear up on its own once Wikidata stops rate-limiting, but I’m not 100% sure on the timing there.
If that doesn’t fix it, send over another log and we can dig further.
Thank you, h0mer! That did it. I have never played around with those settings but will be able to troubleshoot better next time. It does work now, which is great! Thank you for your help!