I’d like to know what can be done about the SearXNG service. It stopped working a couple of days ago—both via Tor and locally.
The service loads fine, but when I try to start a search, all that appears is “•search error” in a red box.
Restarting both the Server One and the service (app) on its own didn’t help. Uninstalling and reinstalling it also failed to resolve the issue, though it did generate new links to call it.
I’m still running version 0.3.5~1.
Is anyone else experiencing this, or is there any advice on how to get this app working properly again?
This situation—linked to the update announced and launched in beta several months ago—strikes me as somewhat inappropriate. Fortunately, it has not affected the Bitcoin Knots/Bitcoin Core services or its associated services.
According to reports, the update to version StartOS 0.4.0 will become available “at some point” via the system’s main interface—a far more suitable and lower-risk path for the average user. Why? Because careful reading reveals the beta version requires not only complex steps beyond most users’ comfort zone but also unacceptable risks few are willing to take.
Let’s hope this resolves soon.
Meanwhile, for the SearXNG service affected “out of the blue”: Until the promised main-interface update appears, I’ve successfully downloaded it as an extension and deployed it directly in the root directory for Mozilla builds, where it’s functioning normally.
No one, much less Start9, has done anything to SearXNG to break it just for the fun of it. Wikidata has implemented a change in their systems to block SearXNG and stop it from accessing results, and has done so in such a way that it crashes SearXNG.
For their part SearXNG seems to have gotten around this change in later versions, since later versions of their software do work.
Why you’d think an issue with a search result provide in SearXNG would affect either Bitcoin or a Start9 server is not something I can comprehend.
Anyone who migrates from StartOS 0351 to 040 will need to perform the same steps, minus the creation of a USB installer. It is a whole new operating system. I’d be happy to help anyone go through this process.
No one, much less Start9, has done anything to SearXNG to break it just for the fun of it. Wikidata has implemented a change in their systems to block SearXNG and stop it from accessing results, and has done so in such a way that it crashes SearXNG.
Crucially absent: Any claim that “Start9 messed up SearXNG for amusement.”
For their part SearXNG seems to have gotten around this change in later versions, since later versions of their software do work.
Yet this feels inappropriate given the update remains in Beta, with explicitly documented bugs and risks on its description page—risks few users accept.
Why you’d think an issue with a search result provide in SearXNG would affect either Bitcoin or a Start9 server is not something I can comprehend.
Anyone who migrates from StartOS 0351 to 040 will need to perform the same steps, minus the creation of a USB installer. It is a whole new operating system. I’d be happy to help anyone go through this process.
I see no connection between:
A beta update deprecating services like SearXNG (making them “obsolete”),
And potential impacts on Bitcoin Knots/Bitcoin Core or version 0.3.5~1 ecosystems. If deprecation is the cause? Entirely plausible.
If anyone is unwilling to update StartOS to v040 at this time, but intend to continue using SearXNG:
With SearXNG running, in the SearXNG UI, go to Peferences, then uncheck Wikidata, and then click save. SearXNG will continue to work until you’re able to move to StartOS v040.
