Vane #2354

Activity

1. MickLesk

   added

   task

   Ready For Testing

   and removed

   task

   on Oct 3, 2026
2. github-actions commented on Oct 4, 2026

   

   github-actionsBot

   on Oct 4, 2026 – with GitHub Actions

   Contributor

   More actions

   The Vane script is ready for testing. Run it in the Proxmox VE shell (or on an Incus host) to create a container:

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

   No AI provider is configured. The first visit to port 3000 opens the setup screen: add Ollama, OpenAI, Anthropic, Gemini, Groq or any OpenAI-compatible server there and pick a chat and an embedding model. Ollama on another host must listen on 0.0.0.0 and be entered as http://:11434.
   Vane has no login. Anyone who reaches port 3000 can use it, read the chat history and see the provider API keys in the settings, so keep it on a trusted network or behind an authenticating reverse proxy.
   The bundled SearXNG only listens on 127.0.0.1:8888 and is configured in /etc/searxng/settings.yml (restart with systemctl restart searxng). To use your own instance instead, enable the json format there and change the SearXNG URL in Vane's settings.
   Settings and API keys (config.json), the chat history (db.sqlite) and uploaded files live in /opt/vane_data, which updates leave untouched.
   Install and every update build Vane from source, which takes about 10 minutes on 2 cores and needs the 4 GB of RAM and 12 GB of disk. Vane and SearXNG together idle at about 500 MB, so the RAM can be lowered after the install and raised again before an update.

   Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

   Discord testing thread: https://discord.com/channels/1302816934508630047/1556239960070168686
3. Corsage commented on Oct 4, 2026

   

   Corsage

   on Oct 4, 2026

   Last edited by Corsage

   More actions

   I tested it out, since I've been looking for something similar to Perplexity for home use. I had one issue for it. I had AI summarize it below, let me know if that's fine / helpful.

   Issue

   SIGABRT crash on Node.js 24: Assertion failed: (env) != nullptr in better-sqlite3 Statement destructor

   Description

   When running Vane on Node.js 24 (e.g. v24.21.0), the server process intermittently crashes with SIGABRT (exit code status=6/ABRT) during or after handling search requests and chat completions.

   This is caused by better-sqlite3@11.10.0's destructor attempting to invoke Node's RemoveEnvironmentCleanupHook after the worker environment context has already been torn down.

   Environment

   • Vane Version: 1.12.2 (via Proxmox Community Script / standalone Next.js build)
   • Node.js Version: v24.21.0 (NodeSource 24.x)
   • OS: Debian 13 (Trixie) / Proxmox LXC (Linux 6.17.4-2-pve)

   Package: better-sqlite3@11.10.0

   Stacktrace

   next-server (v16.2.2)[9073]: void node::RemoveEnvironmentCleanupHook(v8::Isolate*, CleanupHook, void*) at ../src/api/hooks.cc:142
   Assertion failed: (env) != nullptr
   ----- Native stack trace -----
    1: 0x931db0  [next-server (v16.2.2)]
    2: 0x932498 node::Assert(node::AssertionInfo const&) [next-server (v16.2.2)]
    3: 0x81169b node::RemoveEnvironmentCleanupHook(v8::Isolate*, void (*)(void*), void*) [next-server (v16.2.2)]
    4: 0x7678701bf5f9 Statement::~Statement() [/opt/vane/.next/standalone/node_modules/better-sqlite3/build/Release/better_sqlite3.node]
    5: 0x7678701bf701 Statement::~Statement() [/opt/vane/.next/standalone/node_modules/better-sqlite3/build/Release/better_sqlite3.node]
   vane.service: Main process exited, code=killed, status=6/ABRT
   vane.service: Failed with result 'signal'.
   

   Workarounds

   Downgrading the host runtime to Node.js 22 LTS (v22.23.3) eliminates the crash completely.

   OR

   Upgrade better-sqlite3 to ^13.0.0+ (which migrated away from node::ObjectWrap / RemoveEnvironmentCleanupHook to node-addon-api / N-API prebuilds and fully supports Node 24)
4. MickLesk commented on Oct 5, 2026

   

   MickLesk

   on Oct 5, 2026

   MemberAuthor

   More actions

   host runtime downgrade? 😃 what does the host have to do with an OOM inside your LXC?
5. Corsage commented on Oct 5, 2026

   

   Corsage

   on Oct 5, 2026

   Last edited by Corsage

   More actions

   The Vane script has

   NODE_VERSION="24" NODE_MODULE="yarn" setup_nodejs
   

   However, seems like numtide/llm-agents.nix#8217 is a relevant issue for better-sqlite3@11.10.0 .