🔴 P0 | SearXNG NOT FUNCTIONING — 3+ Instances Return No Results — Recommand version UPGRADE before trouble isolation #1

Closed
opened 2026-08-08 19:48:08 +00:00 by yonks · 2 comments
Owner

🆘 Summary

SearXNG is NOT FUNCTIONING — providing no results on confirmed instances. This is a 🔴 P0 infrastructure incident affecting #ResponsibleAgenticAI #WebSearch across the federation.

Affected Instances (confirmed)

# Instance URL
1 INT-P05 PRO.WeOwn.Tools
2 INT-B001 WeOwnLLM.BurnedOut.xyz
3 INT-P08 Dev.WeOwn.Tools

Confirmed: This is NOT an issue with the AnythingLLM instances — it is a SearXNG functionality issue.

Timeline

Time (MDT) Event
15:05 · 07 Aug @GTM broadcast: @SHD discovered SearXNG not providing results on INT-P05 + INT-B001
21:30 · 07 Aug @SHD: "Create my user on both instances. I'll diagnose why this is happening."
~13:24 · 08 Aug @GTM confirmed problem also on INT-P08 (Dev.WeOwn.Tools)
~13:25 · 08 Aug @GTM: recommended version UPGRADE before trouble isolation
~13:29 · 08 Aug @GTM: confirmed FAILOVER to Tavily.com resolved #WebSearch on INT-B001

Root-Cause Direction (observed)

  • SearXNG-family endpoints returned nulls and HTML/JSON parse errors on repeated test queries (W32 D5-D6)
  • Example failure: baresearch.org returned <!doctype html> — not JSON — breaking the search tool parser
  • Pattern suggests version/endpoint degradation, not query-specific failure

Recommended Course (per @GTM)

  1. VERSION UPGRADE first — before spending effort on trouble isolation
  2. Then diagnose remaining issues on upgraded version
  3. Interim: Tavily.com failover confirmed working on INT-B001

Interim Mitigation

  • Tavily.com — FAILOVER #ResponsibleAgenticAI #WebSearch — confirmed working on INT-B001

Labels

  • P0 · bug · infrastructure · searxng · responsibleagenticai

Assignee

  • @SHD (Shahid) — diagnosis requested

GITEA ISSUE draft generated + repo VERIFIED via real API call (WeOwnAI/searxng exists, issues enabled, open_issues_count: 0 → this becomes issue #1). Title + full paste-ready body covering affected instances (INT-P05, INT-B001, INT-P08), timeline, root-cause direction, version-upgrade recommendation, and Tavily failover. I cannot POST via tools — it's ready for @GTM:ADMIN to paste. 🫡🔥

#FlowsBros #FedArch #WeOwnSeason004 #Gitea #Issue #SearXNG #P0 #ResponsibleAgenticAI #WebSearch #Tavily #Failover #SHD #Diagnosis #VersionUpgrade #W32D6

♾️ WeOwnNet 🌐 🏡 Real Estate and 🤝 cooperative ownership for everyone ● An 🤗 inclusive community, by 👥 invitation only.

## 🆘 Summary SearXNG is **NOT FUNCTIONING** — providing no results on confirmed instances. This is a 🔴 P0 infrastructure incident affecting #ResponsibleAgenticAI #WebSearch across the federation. ## Affected Instances (confirmed) | # | Instance | URL | |:-:|:---------|:----| | 1 | INT-P05 | PRO.WeOwn.Tools | | 2 | INT-B001 | WeOwnLLM.BurnedOut.xyz | | 3 | INT-P08 | Dev.WeOwn.Tools | > Confirmed: This is **NOT an issue with the AnythingLLM instances** — it is a **SearXNG functionality issue**. ## Timeline | Time (MDT) | Event | |:-----------|:------| | 15:05 · 07 Aug | @GTM broadcast: @SHD discovered SearXNG not providing results on INT-P05 + INT-B001 | | 21:30 · 07 Aug | @SHD: "Create my user on both instances. I'll diagnose why this is happening." | | ~13:24 · 08 Aug | @GTM confirmed problem also on INT-P08 (Dev.WeOwn.Tools) | | ~13:25 · 08 Aug | @GTM: recommended **version UPGRADE** before trouble isolation | | ~13:29 · 08 Aug | @GTM: confirmed **FAILOVER** to Tavily.com resolved #WebSearch on INT-B001 | ## Root-Cause Direction (observed) - SearXNG-family endpoints returned **nulls** and **HTML/JSON parse errors** on repeated test queries (W32 D5-D6) - Example failure: `baresearch.org` returned `<!doctype html>` — not JSON — breaking the search tool parser - Pattern suggests **version/endpoint degradation**, not query-specific failure ## ✅ Recommended Course (per @GTM) 1. **VERSION UPGRADE first** — before spending effort on trouble isolation 2. Then diagnose remaining issues on upgraded version 3. Interim: Tavily.com failover confirmed working on INT-B001 ## Interim Mitigation - **Tavily.com** — FAILOVER #ResponsibleAgenticAI #WebSearch — ✅ confirmed working on INT-B001 ## Labels - `P0` · `bug` · `infrastructure` · `searxng` · `responsibleagenticai` ## Assignee - @SHD (Shahid) — diagnosis requested --- **GITEA ISSUE draft generated ✅ + repo VERIFIED via real API call** (`WeOwnAI/searxng` exists, issues enabled, open_issues_count: 0 → this becomes issue #1). Title + full paste-ready body covering affected instances (INT-P05, INT-B001, INT-P08), timeline, root-cause direction, version-upgrade recommendation, and Tavily failover. **I cannot POST via tools — it's ready for @GTM:ADMIN to paste.** 🫡🔥 #FlowsBros #FedArch #WeOwnSeason004 #Gitea #Issue #SearXNG #P0 #ResponsibleAgenticAI #WebSearch #Tavily #Failover #SHD #Diagnosis #VersionUpgrade #W32D6 ♾️ WeOwnNet 🌐 🏡 Real Estate and 🤝 cooperative ownership for everyone ● An 🤗 inclusive community, by 👥 invitation only.
shd was assigned by yonks 2026-08-11 14:28:56 +00:00
yonks added the
Priority
Critical
1
Kind/Bug
labels 2026-08-11 14:29:34 +00:00
Author
Owner

Confirmed working via #MetaAgentSage on INT-P05 after reverting to SearXNG:URL:('https://searxng.weown.tools')

Attached 3 screenshots

  1. screenshot_WeOwnChat_INT-P05_issue_1-1_2026-08-11.png
  2. screenshot_WeOwnChat_INT-P05_issue_1-2_2026-08-11.png
  3. screenshot_WeOwnChat_INT-P05_issue_1-3_2026-08-11.png
Confirmed working via #MetaAgentSage on INT-P05 after reverting to SearXNG:URL:('https://searxng.weown.tools') ## Attached 3 screenshots 1. screenshot_WeOwnChat_INT-P05_issue_1-1_2026-08-11.png 2. screenshot_WeOwnChat_INT-P05_issue_1-2_2026-08-11.png 3. screenshot_WeOwnChat_INT-P05_issue_1-3_2026-08-11.png
Member

@yonks, it has been fixed and is now operational. I also updated it to the latest version. Please remember that we have migrated it to 'searxng.weown.tools,' so you need to check it in integration with AnythingLLM.

Issue 'CLOSD'.

@yonks, it has been fixed and is now operational. I also updated it to the latest version. Please remember that we have migrated it to 'searxng.weown.tools,' so you need to check it in integration with AnythingLLM. Issue 'CLOSD'.
shd closed this issue 2026-08-11 16:12:36 +00:00
Sign in to join this conversation.