The following engines have been added: Pixabay: Royalty-free media repository. OpenAlex: Repository of scientific papers, authors, and institutions. In addition, the following defunct and unsupported engines have been removed: Yummly Searchcode Additional notes: The Wordnik engine, which was previously a dictionary, has been converted to an answerer.
I figured out the problem with my Docker setup and fixed it in a way that should let it work on newer containers. I will resume updating the container.
Google does not currently yield any results on SearXNG. This is an upstream issue that I can't do anything about on my end. You can read more about the issue here: https://github.com/searxng/searxng/issues/5286 Until it is resolved, I recommend enabling more engines. Startpage
An update to the SearXNG Docker container has caused the container to consistently crash when starting it with Docker Compose. I will keep this instance on an older version of the container until this is fixed. Update 10-13-25 4:39 PM: I was able to run the Docker container without
Search queries were taking an average of three times as long to perform on the Springfield server, so I reverted the migration and went back to the setup on the Tampa server. I will optimize the Docker setup on that end soon. I'm not sure why that is.
The migration to the Springfield server is complete. I also took the opportunity to clean up my configuration and implement a proper docker compose file instead of the janky Bash script I'd been using.
To reduce the load on the Tampa server, I am migrating the SearXNG Docker container to the Springfield server.
The upstream change was that the codebase was migrated to TypeScript, which broke the custom base.html I'd been using. I have migrated it to TypeScript, so everything should work now.
Something changed upstream that broke the frontend of my instance. I'm working on fixing it.
When SearXNG adds a new engine upstream, you have to manually add it to settings.yml. And it turns out I haven't done that in quite some time. So today, KE0ONU SearXNG now supports almost 50 new engines! When adding them from upstream, I omitted those that caused
KE0ONU SearXNG now uses HTTPS Strict Transport Security (HSTS). This ensures that your browser can only interact with the server using HTTPS connections, preventing man-in-the-middle and protocol downgrade attacks.
The Hostnames plugin now replaces the unsupported minecraft.fandom.com wiki with minecraft.wiki.