LobeHub

Application Name
Lobe Chat

Website
https://github.com/lobehub/lobe-chat

Description
🤯 Lobe Chat - an open-source, modern-design AI chat framework. Supports Multi AI Providers( OpenAI / Claude 3 / Gemini / Ollama / Azure / DeepSeek), Knowledge Base (file upload / knowledge management / RAG ), Multi-Modals (Vision/TTS) and plugin system. One-click FREE deployment of your private ChatGPT/ Claude application.
Adding it to proxmox scripts provide a useful chat interface to all AI model in a private env

The lobe-chat script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/lobehub.sh)"
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.

paradedb repo is currently down...

The lobehub script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/lobehub.sh)"
Configure your AI provider API keys in /opt/lobehub/.env (e.g. OPENAI_API_KEY).
Building from source requires significant resources and may take 10+ minutes.
Update APP_URL in /opt/lobehub/.env if accessing from a different hostname.

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.

Hello Mick,

Build is not working. I got this error:

--- Last 20 lines of log ---
<--- Last few GCs --->
en[9476:0x10c7e000] 87304 ms: Mark-Compact 5934.8 (6259.8) -> 5832.9 (6182.5) MB, pooled: 21 MB, 40.26 / 0.00 ms (+ 1255.2 ms in 309 steps since start of marking, biggest step 8.8 ms, walltime since start of marking 1382 ms) (average mu = 0.259, current[9476:0x10c7e000] 88969 ms: Mark-Compact 5937.2 (6267.8) -> 5785.7 (6132.5) MB, pooled: 25 MB, 49.97 / 0.00 ms (+ 1263.6 ms in 254 steps since start of marking, biggest step 6.8 ms, walltime since start of marking 1401 ms) (average mu = 0.237, current
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0x735eec node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
2: 0xbafbd0 [node]
3: 0xbafcbf [node]
4: 0xe49875 [node]
5: 0xe498a2 [node]
6: 0xe49b9a [node]
7: 0xe5a89a [node]
8: 0xe5ec40 [node]
9: 0x18f3681 [node]
Aborted
ELIFECYCLE Command failed with exit code 134.
ELIFECYCLE Command failed with exit code 134.
ELIFECYCLE Command failed with exit code 134.
[2026-04-04 10:13:49] [ERROR] in line 53: exit code 134 (Process aborted (SIGABRT - possibly Node.js heap overflow))
[2026-04-04 10:13:49] pnpm run build:docker

Any idea about this? I'm using the default build settings

Heap Space. Your system is to slow. Modify RAM to use more

Hi Mick,

Also with 64GB ram is the build not working. How much ram do i need?

What ? :D maybe more CPU? Ive build it now with 4 core 10gb, with 6 core its faster.

Haha, i build it with 16 cores and 64gb but same error......

This is really strange; I give up. Unfortunately, it just doesn't work, not even with 16 cores and 64GB of RAM also shutdown all my containers and vm's gives the same error. Thanks for your help.

I try it also at another proxmox server from an friend and the get the same error.

I found also this lobehub/lobehub#6539

Install and Web UI work flawlessly, update function also working as expected.

that is as far as i have tested though as not an app use.

It also works at my proxmox setup

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using, or where do you have Problems?

Lobehub

📝 Provide a clear and concise description of the issue.

The LobeHub install script fails during PostgreSQL extension creation. The pg_search extension (from ParadeDB) requires being loaded via shared_preload_libraries in postgresql.conf before CREATE EXTENSION pg_search can succeed. The current install script installs the ParadeDB .deb package and immediately calls setup_postgresql_db with PG_DB_EXTENSIONS="vector,pg_search" without configuring shared_preload_libraries, causing a hard failure.

This is a regression introduced by a recent ParadeDB release. Earlier testers (issue #1625, comments dated April 14) reported successful installs, but the latest ParadeDB build (fetched dynamically via api.github.com/repos/paradedb/paradedb/releases/latest) now enforces the preload requirement.

Suggested fix in install/lobehub-install.sh, between the ParadeDB .deb install and setup_postgresql_db:
PG_CONF="/etc/postgresql/17/main/postgresql.conf"
if ! grep -q "shared_preload_libraries.*pg_search" "$PG_CONF"; then
  echo "shared_preload_libraries = 'pg_search'" >> "$PG_CONF"
fi
systemctl restart postgresql
🔄 Steps to reproduce the issue.

On a Proxmox VE 9.1.9 host (kernel 7.0.0-3-pve), run the LobeHub helper script:

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

Accept default settings (Debian 13 LXC, unprivileged, 6 cores, 10240 MiB RAM, 15 GB disk).

Wait until the script reaches the step Setting up PostgreSQL Database.

Installation aborts with exit code 1 immediately after CREATE EXTENSION for pg_search.

❌ Paste the full error output (if available).

Get:1 https://apt.postgresql.org/pub/repos/apt trixie-pgdg/main amd64 postgresql-17-pgvector amd64 0.8.2-1.pgdg13+1 [263 kB] Fetched 263 kB in 0s (1409 kB/s) Selecting previously unselected package postgresql-17-pgvector. (Reading database ... 30857 files and directories currently installed.) Preparing to unpack .../postgresql-17-pgvector_0.8.2-1.pgdg13+1_amd64.deb ... Unpacking postgresql-17-pgvector (0.8.2-1.pgdg13+1) ... Setting up postgresql-17-pgvector (0.8.2-1.pgdg13+1) ... Processing triggers for postgresql-common (290.pgdg13+1) ... Building PostgreSQL dictionaries from installed myspell/hunspell packages... Removing obsolete dictionary files: [2026-05-04 15:04:27] [INFO] Installing pg_search from ParadeDB [2026-05-04 15:04:32] [OK] Installed pg_search from ParadeDB [2026-05-04 15:04:32] [INFO] Setting up PostgreSQL Database CREATE ROLE CREATE DATABASE CREATE EXTENSION ERROR: pg_search must be loaded via shared_preload_libraries. Add 'pg_search' to shared_preload_libraries in postgresql.conf and restart Postgres. [2026-05-04 15:04:33] [ERROR] in line 7171: exit code 1 (General error / Operation not permitted) [2026-05-04 15:04:33] sudo -u postgres psql -d lobehub -c CREATE EXTENSION IF NOT EXISTS pg_search;

📋 Full log: /root/.install-5f316076.log

✖️ Installation failed in container 141 (exit code: 1)

🖼️ Additional context (optional).

Proxmox VE: 9.1.9

Host kernel: 7.0.0-3-pve

LXC: Debian 13 (trixie), unprivileged, default helper-script settings (6 vCPU, 10 GB RAM, 15 GB disk)

PostgreSQL: 17 (apt.postgresql.org trixie-pgdg)

pgvector: 0.8.2-1.pgdg13+1

pg_search: latest ParadeDB release fetched dynamically by the script at install time

Reproduced consistently on a fresh container.

Related: issue LobeHub #1625 (LobeHub tracking issue, "Ready For Testing"). Earlier successful tests (comments dated April 14, 2026) predate the ParadeDB release that enforces shared_preload_libraries.

The first CREATE EXTENSION line that succeeds corresponds to vector; the failure is on pg_search only.

Sadly i can confirm this one now fails with following error:

fixed

Installation without any noticeable errors in console. But when trying to connect to console of the new LXC through the Proxmox webui I get an error:

TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/114 --perm VM.Console --vncticket-endpoint --verify-port --ticket-fd 6 -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole114 -r winch -z lxc-console -n 114 -e -1' failed: exit code 1

SSH access works

Navigation Menu

Repository navigation

LobeHub #1625

6 remaining items

✅ Have you read and understood the above guidelines?

📜 What is the name of the script you are using, or where do you have Problems?

📝 Provide a clear and concise description of the issue.

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

LobeHub #1625

Description

Activity

github-actions commented on Mar 27, 2026

MickLesk commented on Mar 27, 2026

github-actions commented on Apr 2, 2026

N1V4K commented on Apr 4, 2026

MickLesk commented on Apr 4, 2026

N1V4K commented on Apr 4, 2026

MickLesk commented on Apr 4, 2026

N1V4K commented on Apr 4, 2026

6 remaining items

N1V4K commented on Apr 5, 2026

N1V4K commented on Apr 5, 2026

CerberusStyle commented on Apr 14, 2026

N1V4K commented on Apr 14, 2026

MickLesk commented on May 4, 2026

✅ Have you read and understood the above guidelines?

📜 What is the name of the script you are using, or where do you have Problems?

📝 Provide a clear and concise description of the issue.

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

CerberusStyle commented on May 4, 2026

MickLesk commented on May 6, 2026

Post79 commented on May 9, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions