Services not working after hard reset

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.