Harden a public SearXNG instance
Open SearXNG to other people safely: bind to localhost, align forwarded IP headers with trusted proxies, enable the limiter, and lock down the JSON API.
Filtering by topic #searxng · clear
Open SearXNG to other people safely: bind to localhost, align forwarded IP headers with trusted proxies, enable the limiter, and lock down the JSON API.
Send SearXNG outgoing engine requests through a proxy or Tor: the outgoing settings.yml block, per engine networks, timeouts, and when it makes results worse.
Which SearXNG engines survive a datacenter IP and which get CAPTCHAs, plus the settings.yml keys (disabled, timeout, weight, suspended_times) that act on it.
Your SearXNG instance can be the search backend for an AI agent. JSON API setup, the trust boundaries, and the prompt injection surface it opens.
What each private search engine does with your query: index source, where it runs, what its privacy page says, and what breaks when you run SearXNG yourself.
Your SearXNG instance can feed web search to Open WebUI. Enable the JSON format, then hand the other container a URL it can actually reach.
SearXNG swaps your IP for your server's IP at the search engines. Who really sees your queries on a public instance and on your own VPS, and where it stops.
Ollama does not browse on its own. Give a local model search through Ollama's web search API, Open WebUI with SearXNG, or a short Python tool loop you control.
The SearXNG limiter keeps its per IP counters in Valkey. Set up limiter.toml in a container or a source install, and see which sections actually matter.
How to read searx.space before you pick a public SearXNG instance: what each grade measures, and the one thing about the operator no grade can show you.
SearXNG 429 errors come from your own limiter. Engines that block your server IP drop results without a 429. Read the log, fix the right one, stop guessing.
Searx has taken no code commit since 2023 and SearXNG carries the project now. Check the status yourself, then see what changed for a new instance.
Running SearXNG and eyeing Degoog 1.1.0? Compare maturity, engines, rate limits and the extension risk, and find out if the SearXNG API shim really works.
SearXNG engines answer a VPS with CAPTCHA pages more often than a home connection. Read the real error, then pick a fix that survives a restart.
Read the SearXNG service log and /stats to tell a timeout from a suspended engine or a crash like KeyError, then fix each one in settings.yml.
Run SearXNG on your own VPS with Docker Compose: settings.yml, the limiter, nginx with TLS, and a JSON search API your own scripts can call.
Yes, through Docker Desktop and WSL2. Install the SearXNG container, bind it to localhost, set a secret key, and learn where a Windows PC stops being enough.