SearXNG doesn't start after update is run #1399

Closed
opened 2026-02-05 00:37:41 +03:00 by OVERLORD · 5 comments
Owner

Originally created by @RonV42 on GitHub (Aug 5, 2025).

Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

SearXNG

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/searxng.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Running the update command in the LXC you can see it pulling the latest from github. After the update if you restart the LXC SearXNG no longer starts.

🔄 Steps to reproduce the issue.

Step 1:
open console on LXC container

Step 2:
run "update"

Step 3:
htop shows both the redis and python services running

Step 4:
reboot the LXC and only the redis service shows running

Paste the full error output (if available).

This is the output from the update command running verbose:

  _____                _  __ _   ________
  / ___/___  ____ _____| |/ // | / / ____/
  \__ \/ _ \/ __ `/ ___/   //  |/ / / __  
 ___/ /  __/ /_/ / /  /   |/ /|  / /_/ /  
/____/\___/\__,_/_/  /_/|_/_/ |_/\____/   
                                          

remote: Enumerating objects: 4464, done.
remote: Counting objects: 100% (1119/1119), done.
remote: Compressing objects: 100% (348/348), done.
remote: Total 4464 (delta 1049), reused 771 (delta 771), pack-reused 3345 (from 5)
Receiving objects: 100% (4464/4464), 10.95 MiB | 4.34 MiB/s, done.
Resolving deltas: 100% (1825/1825), completed with 166 local objects.
From https://github.com/searxng/searxng
   37d851fb2..2e62eb5d6  master       -> origin/master
 * [new branch]          dependabot/npm_and_yarn/client/simple/master/minor-70e2c4d971 -> origin/dependabot/npm_and_yarn/client/simple/master/minor-70e2c4d971
 + 0b9f0864b...52b072931 gh-pages     -> origin/gh-pages  (forced update)
   0f55f2438..17e9fcd68  translations -> origin/translations

🖼️ Additional context (optional).

No response

Originally created by @RonV42 on GitHub (Aug 5, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? SearXNG ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/searxng.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Running the update command in the LXC you can see it pulling the latest from github. After the update if you restart the LXC SearXNG no longer starts. ### 🔄 Steps to reproduce the issue. Step 1: open console on LXC container Step 2: run "update" Step 3: htop shows both the redis and python services running Step 4: reboot the LXC and only the redis service shows running ### ❌ Paste the full error output (if available). ``` This is the output from the update command running verbose: _____ _ __ _ ________ / ___/___ ____ _____| |/ // | / / ____/ \__ \/ _ \/ __ `/ ___/ // |/ / / __ ___/ / __/ /_/ / / / |/ /| / /_/ / /____/\___/\__,_/_/ /_/|_/_/ |_/\____/ remote: Enumerating objects: 4464, done. remote: Counting objects: 100% (1119/1119), done. remote: Compressing objects: 100% (348/348), done. remote: Total 4464 (delta 1049), reused 771 (delta 771), pack-reused 3345 (from 5) Receiving objects: 100% (4464/4464), 10.95 MiB | 4.34 MiB/s, done. Resolving deltas: 100% (1825/1825), completed with 166 local objects. From https://github.com/searxng/searxng 37d851fb2..2e62eb5d6 master -> origin/master * [new branch] dependabot/npm_and_yarn/client/simple/master/minor-70e2c4d971 -> origin/dependabot/npm_and_yarn/client/simple/master/minor-70e2c4d971 + 0b9f0864b...52b072931 gh-pages -> origin/gh-pages (forced update) 0f55f2438..17e9fcd68 translations -> origin/translations ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 00:37:41 +03:00
Author
Owner

@MickLesk commented on GitHub (Aug 5, 2025):

use your backup. Searxng is broken, we currently remove it

@MickLesk commented on GitHub (Aug 5, 2025): use your backup. Searxng is broken, we currently remove it
Author
Owner

@RonV42 commented on GitHub (Aug 5, 2025):

Thanks I will use my backup.

@RonV42 commented on GitHub (Aug 5, 2025): Thanks I will use my backup.
Author
Owner

@elvito commented on GitHub (Aug 13, 2025):

Hi, I also switched back to backup after a failed update. Is Searxng broken (redis--> valkey???) or does the HS installscript just need a fix/rewrite?

@elvito commented on GitHub (Aug 13, 2025): Hi, I also switched back to backup after a failed update. Is Searxng broken (redis--> valkey???) or does the HS installscript just need a fix/rewrite?
Author
Owner

@MickLesk commented on GitHub (Aug 13, 2025):

Broken and Needs a rewrite... at some point

@MickLesk commented on GitHub (Aug 13, 2025): Broken and Needs a rewrite... at some point
Author
Owner

@elvito commented on GitHub (Aug 13, 2025):

Ok, I really need searxng I'll try a rewrite. Thanks for this very quick answer ;)

@elvito commented on GitHub (Aug 13, 2025): Ok, I really need searxng I'll try a rewrite. Thanks for this very quick answer ;)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1399