Palaver-Server zu einem Host hinzufügen
zuletzt geändert
- Hauptserver plus beliebig viele weitere Server auf einem Host
- mit dem Hauptserver geteilt: Programme (
/opt/palaver/bin), Web-Client (/opt/palaver/web), LiveKit - Hauptserver per apt oder aus den Release-Dateien installiert
- Updates: Update-Anleitung (apt), Update-Anleitung ohne Paketquelle (Release-Dateien)
Für jeden weiteren Server:
| Bestandteil | Wert |
|---|---|
| Name | <server> |
| Domain | <domain> |
| Systembenutzer, Datenbankrolle | palaver-<server> |
| Datenbank | palaver_<server> |
| Konfiguration | /opt/palaver/instances/<server>/palaverd.env |
| systemd-Unit | palaverd@<server> |
| Port | <port> (Schritt 3) |
| LiveKit-Raumpräfix | <server>- (PALAVER_LIVEKIT_ROOM_PREFIX) |
| LiveKit-Schlüssel | eigener Schlüssel in /opt/palaver/etc/livekit.yaml |
| nginx | Site palaver-<server>, Web-Client aus dem Snippet palaver-web.conf |
| nginx-Logs | /var/log/nginx/palaver/<server>.access.log, <server>.error.log |
Platzhalter in den Befehlen:
| Platzhalter | Ersetzen durch |
|---|---|
<server> |
den Namen des Servers (Schritt 2), in jedem Namen der Tabelle oben; ein - im Namen wird im Datenbanknamen zu _ (z. B. my-server → palaver_my_server) |
<domain> |
die Domain des Servers |
<port> |
den Port des Servers (Schritt 3) |
palaver.social |
in /etc/letsencrypt/live/palaver.social/: den Namen des Zertifikats (eigenes Zertifikat: die Domain des Servers); sonst: die Domain des Hauptservers |
you@example.org |
E-Mail-Adresse für Let's Encrypt; nur eigenes Zertifikat |
<livekit-key>, <livekit-secret> |
Ausgabe aus Schritt 6, „Erzeuge … für die LiveKit-API“ |
'<title>', '<subtitle>' |
Name und Untertitel des Servers in der App (Schritt 11); kein Untertitel: '' |
2026-10-11 |
das heutige Datum (Namen der Sicherungsdateien) |
vi |
Editor deiner Wahl |
1. Voraussetzungen
- Hauptserver nach Palavers
INSTALL.md(apt) oder PalaversINSTALL-TARBALL.md(Release-Dateien): Snippetpalaver-web.conf, Benutzer und Datenbankpalaver,/opt/palaver/etc, LiveKit, Port 8090 - Shell-Zugang mit
sudo - keine weiteren Ports: 443 und die LiveKit-Ports des Hauptservers
Prüfe, ob der Hauptserver da ist.
sudo ls /opt/palaver/etc/palaverd.env /opt/palaver/etc/livekit.yaml /etc/nginx/snippets/palaver-web.conf
Prüfe, ob die Unit-Vorlage da ist; apt: immer (Paket palaver-server).
systemctl cat palaverd@.service
Fehlt sie (Release-Dateien): Öffne /etc/systemd/system/palaverd@.service in einem Editor.
sudo vi /etc/systemd/system/palaverd@.service
Inhalt:
[Unit]
Description=Palaver app server %i
After=network-online.target postgresql.service
Wants=network-online.target
[Service]
User=palaver-%i
Group=palaver-%i
EnvironmentFile=/opt/palaver/instances/%i/palaverd.env
ExecStart=/opt/palaver/bin/palaverd serve
Restart=on-failure
RestartSec=2
LogNamespace=palaver
NoNewPrivileges=yes
ProtectSystem=strict
ProtectHome=yes
PrivateTmp=yes
PrivateDevices=yes
ProtectKernelTunables=yes
ProtectKernelModules=yes
ProtectControlGroups=yes
RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6
LockPersonality=yes
MemoryDenyWriteExecute=yes
[Install]
WantedBy=multi-user.target
Lade sie.
sudo systemctl daemon-reload
2. Name und Domain
- Name:
a-z,0-9,-(nicht als erstes oder letztes Zeichen), höchstens 24 Zeichen - reserviert:
palaver,www,account,konto,support,api,admin,dogan,livekit,mail,status - Domain: Hostname, kleingeschrieben
- Zertifikat: das Wildcard-Zertifikat
palaver.socialoder ein eigenes (Schritt 8) - Name und Untertitel in der App: je bis zu 64 Zeichen
- eine Bestellung über account.palaver.social zeigt diese Werte zum Kopieren
Prüfe, ob der Name frei ist; erwartet: beide Befehle schlagen fehl.
ls -d /opt/palaver/instances/<server>
id palaver-<server>
3. Port
- ein localhost-Port je Server; Hauptserver: 8090
- neuer Server: höchster belegter Port + 1 (erster weiterer Server: 8091)
Zeige die belegten Ports; nimm den höchsten + 1.
sudo sh -c 'grep -H "^PALAVER_LISTEN=" /opt/palaver/etc/palaverd.env /opt/palaver/instances/*/palaverd.env 2>/dev/null'
Prüfe, dass dort nichts lauscht; erwartet: keine Ausgabe.
ss -Htln 'sport = :<port>'
4. Benutzer und Verzeichnis
Lege das Verzeichnis für alle weiteren Server an.
sudo install -d -o root -g root -m 755 /opt/palaver/instances
Lege den Systembenutzer an.
sudo useradd --system --home-dir /opt/palaver/instances/<server> --no-create-home --shell /usr/sbin/nologin palaver-<server>
Lege das Konfigurationsverzeichnis an.
sudo install -d -o palaver-<server> -g palaver-<server> -m 700 /opt/palaver/instances/<server>
5. PostgreSQL
Lege die Datenbankrolle und die Datenbank an.
sudo -u postgres createuser palaver-<server>
sudo -u postgres createdb -O palaver-<server> palaver_<server>
6. LiveKit-Schlüssel
Erzeuge den Schlüssel für die LiveKit-API (<livekit-key>).
openssl rand -hex 8 | sed 's/^/API/'
Erzeuge das Geheimnis für die LiveKit-API (<livekit-secret>).
openssl rand -base64 36 | tr -d '/+='
Öffne /opt/palaver/etc/livekit.yaml in einem Editor.
sudo vi /opt/palaver/etc/livekit.yaml
Füge unter keys: eine Zeile hinzu, um zwei Leerzeichen eingerückt:
<livekit-key>: <livekit-secret>
Prüfe die Schlüssel; erwartet: eine Zeile je Server.
sudo sed -n '/^keys:/,/^[a-z]/p' /opt/palaver/etc/livekit.yaml
Starte LiveKit neu; Gespräche auf allen Servern brechen ab.
sudo systemctl restart livekit
- LiveKit-Schlüssel sind nicht auf Räume begrenzt: die Konfiguration eines Servers gibt Zugriff auf die Gespräche aller Server
7. palaverd
Öffne /opt/palaver/instances/<server>/palaverd.env in einem Editor.
sudo vi /opt/palaver/instances/<server>/palaverd.env
Inhalt:
PALAVER_DATABASE_URL=postgres:///palaver_<server>?host=/var/run/postgresql
PALAVER_LISTEN=127.0.0.1:<port>
PALAVER_PUBLIC_URL=https://<domain>
PALAVER_LIVEKIT_URL=wss://<domain>/livekit
PALAVER_LIVEKIT_API_URL=http://127.0.0.1:7880
PALAVER_LIVEKIT_API_KEY=<livekit-key>
PALAVER_LIVEKIT_API_SECRET=<livekit-secret>
PALAVER_LIVEKIT_ROOM_PREFIX=<server>-
PALAVER_OPEN_REGISTRATION=false
PALAVER_CTL="sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env"
PALAVER_UNIT=palaverd@<server>
PALAVER_ENV_FILE=/opt/palaver/instances/<server>/palaverd.env
Mach sie nur für palaver-<server> lesbar.
sudo chown palaver-<server>:palaver-<server> /opt/palaver/instances/<server>/palaverd.env
sudo chmod 600 /opt/palaver/instances/<server>/palaverd.env
- weitere Einstellungen: Palavers
INSTALL.md, Konfigurationsreferenz
8. Zertifikat
Unter einem Wildcard-Zertifikat
Prüfe, ob es die Domain abdeckt; erwartet: DNS:*.palaver.social.
sudo openssl x509 -noout -ext subjectAltName -in /etc/letsencrypt/live/palaver.social/fullchain.pem
Weiter: Schritt 9.
Eigenes Zertifikat
Öffne /etc/nginx/sites-available/palaver-<server> in einem Editor.
sudo vi /etc/nginx/sites-available/palaver-<server>
Inhalt:
server {
listen 80;
listen [::]:80;
server_name <domain>;
location /.well-known/acme-challenge/ { root /var/www/html; }
location / { return 404; }
}
Aktiviere die Site, prüfe und lade sie.
sudo ln -sf /etc/nginx/sites-available/palaver-<server> /etc/nginx/sites-enabled/palaver-<server>
sudo nginx -t && sudo systemctl reload nginx
Hole das Zertifikat.
sudo certbot certonly --webroot -w /var/www/html -d <domain> -m you@example.org \
--agree-tos --no-eff-email --non-interactive \
--deploy-hook "systemctl reload nginx"
- Site in Schritt 9:
/etc/letsencrypt/live/<domain>/statt/etc/letsencrypt/live/palaver.social/
9. nginx
Öffne /etc/nginx/sites-available/palaver-<server> in einem Editor.
sudo vi /etc/nginx/sites-available/palaver-<server>
Inhalt:
server {
listen 80;
listen [::]:80;
server_name <domain>;
access_log /var/log/nginx/palaver/<server>.access.log;
error_log /var/log/nginx/palaver/<server>.error.log;
location /.well-known/acme-challenge/ {
root /var/www/html;
}
location / {
return 301 https://$host$request_uri;
}
}
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name <domain>;
ssl_certificate /etc/letsencrypt/live/palaver.social/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/palaver.social/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
access_log /var/log/nginx/palaver/<server>.access.log;
error_log /var/log/nginx/palaver/<server>.error.log;
# largest default body: a minutes update, 1 MiB
client_max_body_size 2m;
# server push, one WebSocket per client
location = /api/events {
proxy_pass http://127.0.0.1:<port>;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 1h;
proxy_send_timeout 1h;
}
# profile pictures, server icon: 5 MiB
location ~ ^/api/(me/avatar|server/icon)$ {
client_max_body_size 5m;
proxy_pass http://127.0.0.1:<port>;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
# attachments: 25 MiB
location ~ ^/api/channels/[0-9]+/attachments$ {
client_max_body_size 25m;
proxy_pass http://127.0.0.1:<port>;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
location /api/ {
proxy_pass http://127.0.0.1:<port>;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
# LiveKit signalling, shared; the trailing slash strips /livekit
location /livekit/ {
proxy_pass http://127.0.0.1:7880/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_read_timeout 1h;
proxy_send_timeout 1h;
}
include snippets/palaver-web.conf;
}
Aktiviere, prüfe und lade sie.
sudo ln -sf /etc/nginx/sites-available/palaver-<server> /etc/nginx/sites-enabled/palaver-<server>
sudo nginx -t && sudo systemctl reload nginx
10. Starten
Starte den Server.
sudo systemctl enable --now palaverd@<server>
Prüfe, ob er antwortet; erwartet: JSON.
curl -fsS http://127.0.0.1:<port>/api/registration
11. Erster Admin
Setze Name und Untertitel des Servers.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env profile -name '<title>' -subtitle '<subtitle>'
Erzeuge einen Einladungscode für den ersten Admin; einmal nutzbar, 7 Tage gültig.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env invite -role Admin -valid 168h
- registrieren: Palaver-App → Server
https://<domain>→ Registrieren → Code - erster Admin = Eigentümer des Servers
- Konto ohne Admin registriert (Code ohne
-role Admin): Rolle nachträglich vergeben
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env grant <username> Admin
12. Prüfen
Führe doctor aus; erwartet: ok in jeder Zeile.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env doctor
Prüfe, ob der Hauptserver weiter antwortet.
sudo -u palaver /opt/palaver/bin/palaverd -env /opt/palaver/etc/palaverd.env doctor
Server auflisten
Namen der weiteren Server.
ls /opt/palaver/instances/
Domain und Port jedes Servers.
sudo sh -c 'grep -H -E "^PALAVER_(PUBLIC_URL|LISTEN)=" /opt/palaver/etc/palaverd.env /opt/palaver/instances/*/palaverd.env'
Name und Untertitel eines Servers.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env profile
Zustand jedes Servers.
systemctl list-units --all 'palaverd*'
Sicherung
- Datenbank: alle Daten des Servers
/opt/palaver/instances/<server>: Konfiguration, LiveKit-Schlüssel
Sichere die Datenbank.
sudo -u palaver-<server> pg_dump -Fc palaver_<server> > palaver-<server>-2026-10-11.dump
Sichere die Konfiguration.
sudo tar -czf palaver-<server>-etc-2026-10-11.tar.gz -C /opt/palaver/instances <server>
Wiederherstellen
Voraussetzung: Server mit demselben Namen und derselben Domain, Schritte 1–11.
Halte ihn an.
sudo systemctl stop palaverd@<server>
Destruktiv: Lösche die Datenbank des neuen Servers (palaver_<server>, alle seine Konten und Nachrichten).
sudo -u postgres dropdb palaver_<server>
Lege sie neu an und lade die Sicherung.
sudo -u postgres createdb -O palaver-<server> palaver_<server>
sudo -u palaver-<server> pg_restore -d palaver_<server> palaver-<server>-2026-10-11.dump
Starte ihn.
sudo systemctl start palaverd@<server>
Server entfernen
Zeige die Domain und den LiveKit-Schlüssel (<livekit-key>).
sudo grep -E '^PALAVER_(PUBLIC_URL|LIVEKIT_API_KEY)=' /opt/palaver/instances/<server>/palaverd.env
Zeige das Zertifikat der Site; eigenes Zertifikat: Name <domain>.
grep ssl_certificate /etc/nginx/sites-available/palaver-<server>
Vorher sichern: Sicherung.
Halte den Dienst an und deaktiviere ihn.
sudo systemctl disable --now palaverd@<server>
Entferne die nginx-Site und lade nginx neu.
sudo rm /etc/nginx/sites-enabled/palaver-<server> /etc/nginx/sites-available/palaver-<server>
sudo nginx -t && sudo systemctl reload nginx
Destruktiv: Lösche die Datenbank palaver_<server> (alle Konten, Nachrichten, Anhänge) und ihre Rolle palaver-<server>.
sudo -u postgres dropdb palaver_<server>
sudo -u postgres dropuser palaver-<server>
Destruktiv: Lösche den LiveKit-Schlüssel des Servers; öffne /opt/palaver/etc/livekit.yaml in einem Editor.
sudo vi /opt/palaver/etc/livekit.yaml
Entferne:
- unter
keys:die Zeile<livekit-key>: …
Starte LiveKit neu; Gespräche auf den anderen Servern brechen kurz ab.
sudo systemctl restart livekit
Destruktiv: Lösche die Konfiguration /opt/palaver/instances/<server> und den Benutzer palaver-<server>.
sudo rm -r /opt/palaver/instances/<server>
sudo userdel palaver-<server>
Destruktiv: Lösche das Zertifikat; nur ein eigenes (<domain>), nie das Wildcard-Zertifikat.
sudo certbot delete --cert-name <domain>
Destruktiv: Lösche die nginx-Logs des Servers (/var/log/nginx/palaver/<server>.*).
sudo sh -c 'rm /var/log/nginx/palaver/<server>.access.log* /var/log/nginx/palaver/<server>.error.log*'
Nach dem letzten weiteren Server
Entferne das leere Verzeichnis.
sudo rmdir /opt/palaver/instances
- vor dem Deinstallieren des Hauptservers (Palavers
INSTALL.md, Deinstallieren; Release-Dateien: PalaversINSTALL-TARBALL.md, Deinstallieren): alle weiteren Server entfernen
Optional: unbekannte Namen zum Hauptserver
- für: Wildcard-DNS-Eintrag und -Zertifikat für die Domain des Hauptservers
- unbekannte Namen (Tippfehler): Umleitung zum Hauptserver statt zu nginx' erster Site
Prüfe, ob das Zertifikat *.palaver.social abdeckt.
sudo openssl x509 -noout -ext subjectAltName -in /etc/letsencrypt/live/palaver.social/fullchain.pem
Prüfe, ob die Platzhalter-Site der Distribution default_server beansprucht.
grep default_server /etc/nginx/sites-enabled/default
Falls ja: deaktiviere sie.
sudo rm /etc/nginx/sites-enabled/default
Öffne /etc/nginx/sites-available/palaver-catch-all in einem Editor.
sudo vi /etc/nginx/sites-available/palaver-catch-all
Inhalt:
server {
listen 80 default_server;
listen [::]:80 default_server;
server_name _;
location /.well-known/acme-challenge/ { root /var/www/html; }
location / { return 301 https://palaver.social/; }
}
server {
listen 443 ssl default_server;
listen [::]:443 ssl default_server;
server_name _;
ssl_certificate /etc/letsencrypt/live/palaver.social/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/palaver.social/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
return 301 https://palaver.social/;
}
Aktiviere, prüfe und lade sie.
sudo ln -sf /etc/nginx/sites-available/palaver-catch-all /etc/nginx/sites-enabled/palaver-catch-all
sudo nginx -t && sudo systemctl reload nginx
Optional: Wildcard-Zertifikat
- ein Zertifikat für die Hauptdomain und jeden Namen darunter (
palaver.social,*.palaver.social) - certbot-DNS-Prüfung
- palaver.social: certbot-Snap, Plugin
certbot-dns-hetzner-cloud, Zugangsdaten/root/.secrets/hetzner.ini, Deploy-Hooksystemctl reload nginx - nur ein certbot je Host
Liste die Zertifikate und die Namen auf, die sie abdecken.
sudo certbot certificates
Prüfe den Deploy-Hook des Wildcard-Zertifikats.
sudo grep -E 'authenticator|renew_hook|deploy_hook' /etc/letsencrypt/renewal/palaver.social.conf
Dateien
| Pfad | Inhalt |
|---|---|
/usr/lib/systemd/system/palaverd@.service |
Unit-Vorlage (Paket palaver-server); Release-Dateien: /etc/systemd/system/ |
/opt/palaver/instances/<server>/palaverd.env |
Konfiguration (nur Benutzer palaver-<server>) |
/opt/palaver/etc/livekit.yaml |
ein Schlüssel je Server unter keys: |
/etc/nginx/sites-available/palaver-<server> |
nginx-Site |
/etc/nginx/snippets/palaver-web.conf |
Web-Client, CSP für den eigenen Namen der Site (Hauptserver) |
/etc/nginx/sites-available/palaver-catch-all |
unbekannte Namen (optional) |
/var/log/nginx/palaver/<server>.access.log, <server>.error.log |
nginx-Logs (rotiert von Palavers /etc/logrotate.d/palaver) |
Fehlersuche
doctor eines Servers.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env doctor
Was palaverd meldet.
sudo journalctl --namespace=palaver -u palaverd@<server> -n 100
Was nginx meldet.
sudo tail -n 50 /var/log/nginx/palaver/<server>.error.log
| Symptom | Ursache |
|---|---|
useradd: invalid user name |
Name zu lang (höchstens 24 Zeichen) |
| Sprache geht nur auf diesem Server nicht | Schlüssel fehlt in livekit.yaml oder LiveKit nach Schritt 6 nicht neu gestartet |
| Sprache geht auf keinem Server | livekit.yaml durch eine Änderung kaputt: sudo journalctl --namespace=palaver -u livekit -n 50 |
| die Site eines anderen Servers antwortet | server_name oder der Symlink in sites-enabled fehlt |
| Web-Client im Browser ohne Sprache | PALAVER_LIVEKIT_URL nicht unter der eigenen Domain des Servers (doctor meldet es) |
Add Palaver servers to a host
last changed
- main server plus any number of further servers on one host
- shared with the main server: programs (
/opt/palaver/bin), web client (/opt/palaver/web), LiveKit - main server installed with apt or from the release files
- updates: the update guide for several servers (apt), the update guide for several servers (release files) (release files)
For each further server:
| Part | Value |
|---|---|
| name | <server> |
| domain | <domain> |
| system user, database role | palaver-<server> |
| database | palaver_<server> |
| configuration | /opt/palaver/instances/<server>/palaverd.env |
| systemd unit | palaverd@<server> |
| port | <port> (step 3) |
| LiveKit room prefix | <server>- (PALAVER_LIVEKIT_ROOM_PREFIX) |
| LiveKit key | own key in /opt/palaver/etc/livekit.yaml |
| nginx | site palaver-<server>, web client from the snippet palaver-web.conf |
| nginx logs | /var/log/nginx/palaver/<server>.access.log, <server>.error.log |
Placeholders in the commands:
| Placeholder | Replace with |
|---|---|
<server> |
the server's name (step 2), in every name of the table above; a - in the name becomes _ in the database name (e.g. my-server → palaver_my_server) |
<domain> |
the server's domain |
<port> |
the server's port (step 3) |
palaver.social |
in /etc/letsencrypt/live/palaver.social/: the certificate's name (own certificate: the server's domain); elsewhere: the main server's domain |
you@example.org |
e-mail address for Let's Encrypt; own certificate only |
<livekit-key>, <livekit-secret> |
output of step 6, "Generate the LiveKit API …" |
'<title>', '<subtitle>' |
the server's name and subtitle in the app (step 11); no subtitle: '' |
2026-10-11 |
today's date (backup file names) |
vi |
editor of your choice |
1. Requirements
- main server per Palaver's
INSTALL.md(apt) or Palaver'sINSTALL-TARBALL.md(release files): snippetpalaver-web.conf, user and databasepalaver,/opt/palaver/etc, LiveKit, port 8090 - shell access with
sudo - no further ports: 443 and the main server's LiveKit ports
Check that the main server is there.
sudo ls /opt/palaver/etc/palaverd.env /opt/palaver/etc/livekit.yaml /etc/nginx/snippets/palaver-web.conf
Check whether the unit template is there; apt: always (package palaver-server).
systemctl cat palaverd@.service
Missing (release files): open /etc/systemd/system/palaverd@.service in an editor.
sudo vi /etc/systemd/system/palaverd@.service
Content:
[Unit]
Description=Palaver app server %i
After=network-online.target postgresql.service
Wants=network-online.target
[Service]
User=palaver-%i
Group=palaver-%i
EnvironmentFile=/opt/palaver/instances/%i/palaverd.env
ExecStart=/opt/palaver/bin/palaverd serve
Restart=on-failure
RestartSec=2
LogNamespace=palaver
NoNewPrivileges=yes
ProtectSystem=strict
ProtectHome=yes
PrivateTmp=yes
PrivateDevices=yes
ProtectKernelTunables=yes
ProtectKernelModules=yes
ProtectControlGroups=yes
RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6
LockPersonality=yes
MemoryDenyWriteExecute=yes
[Install]
WantedBy=multi-user.target
Load it.
sudo systemctl daemon-reload
2. Name and domain
- name:
a-z,0-9,-(not first or last), at most 24 characters - reserved:
palaver,www,account,konto,support,api,admin,dogan,livekit,mail,status - domain: host name, lower case
- certificate: the wildcard certificate
palaver.social, or an own one (step 8) - name and subtitle in the app: up to 64 characters each
- an order from account.palaver.social shows these values ready to copy
Check that the name is free; expected: both commands fail.
ls -d /opt/palaver/instances/<server>
id palaver-<server>
3. Port
- one localhost port per server; main server: 8090
- new server: highest port in use + 1 (first further server: 8091)
Show the ports in use; take the highest + 1.
sudo sh -c 'grep -H "^PALAVER_LISTEN=" /opt/palaver/etc/palaverd.env /opt/palaver/instances/*/palaverd.env 2>/dev/null'
Check that nothing listens on it; expected: no output.
ss -Htln 'sport = :<port>'
4. User and directory
Create the directory for all further servers.
sudo install -d -o root -g root -m 755 /opt/palaver/instances
Create the system user.
sudo useradd --system --home-dir /opt/palaver/instances/<server> --no-create-home --shell /usr/sbin/nologin palaver-<server>
Create the configuration directory.
sudo install -d -o palaver-<server> -g palaver-<server> -m 700 /opt/palaver/instances/<server>
5. PostgreSQL
Create the database role and the database.
sudo -u postgres createuser palaver-<server>
sudo -u postgres createdb -O palaver-<server> palaver_<server>
6. LiveKit key
Generate the LiveKit API key (<livekit-key>).
openssl rand -hex 8 | sed 's/^/API/'
Generate the LiveKit API secret (<livekit-secret>).
openssl rand -base64 36 | tr -d '/+='
Open /opt/palaver/etc/livekit.yaml in an editor.
sudo vi /opt/palaver/etc/livekit.yaml
Add a line under keys:, indented by two spaces:
<livekit-key>: <livekit-secret>
Check the keys; expected: one line per server.
sudo sed -n '/^keys:/,/^[a-z]/p' /opt/palaver/etc/livekit.yaml
Restart LiveKit; calls on every server drop.
sudo systemctl restart livekit
- LiveKit keys are not limited to rooms: one server's configuration gives access to all servers' calls
7. palaverd
Open /opt/palaver/instances/<server>/palaverd.env in an editor.
sudo vi /opt/palaver/instances/<server>/palaverd.env
Content:
PALAVER_DATABASE_URL=postgres:///palaver_<server>?host=/var/run/postgresql
PALAVER_LISTEN=127.0.0.1:<port>
PALAVER_PUBLIC_URL=https://<domain>
PALAVER_LIVEKIT_URL=wss://<domain>/livekit
PALAVER_LIVEKIT_API_URL=http://127.0.0.1:7880
PALAVER_LIVEKIT_API_KEY=<livekit-key>
PALAVER_LIVEKIT_API_SECRET=<livekit-secret>
PALAVER_LIVEKIT_ROOM_PREFIX=<server>-
PALAVER_OPEN_REGISTRATION=false
PALAVER_CTL="sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env"
PALAVER_UNIT=palaverd@<server>
PALAVER_ENV_FILE=/opt/palaver/instances/<server>/palaverd.env
Make it readable by palaver-<server> only.
sudo chown palaver-<server>:palaver-<server> /opt/palaver/instances/<server>/palaverd.env
sudo chmod 600 /opt/palaver/instances/<server>/palaverd.env
- other settings: Palaver's
INSTALL.md, Configuration reference
8. Certificate
Under a wildcard certificate
Check that it covers the domain; expected: DNS:*.palaver.social.
sudo openssl x509 -noout -ext subjectAltName -in /etc/letsencrypt/live/palaver.social/fullchain.pem
Next: step 9.
Own certificate
Open /etc/nginx/sites-available/palaver-<server> in an editor.
sudo vi /etc/nginx/sites-available/palaver-<server>
Content:
server {
listen 80;
listen [::]:80;
server_name <domain>;
location /.well-known/acme-challenge/ { root /var/www/html; }
location / { return 404; }
}
Enable the site, check and load it.
sudo ln -sf /etc/nginx/sites-available/palaver-<server> /etc/nginx/sites-enabled/palaver-<server>
sudo nginx -t && sudo systemctl reload nginx
Get the certificate.
sudo certbot certonly --webroot -w /var/www/html -d <domain> -m you@example.org \
--agree-tos --no-eff-email --non-interactive \
--deploy-hook "systemctl reload nginx"
- step 9's site:
/etc/letsencrypt/live/<domain>/instead of/etc/letsencrypt/live/palaver.social/
9. nginx
Open /etc/nginx/sites-available/palaver-<server> in an editor.
sudo vi /etc/nginx/sites-available/palaver-<server>
Content:
server {
listen 80;
listen [::]:80;
server_name <domain>;
access_log /var/log/nginx/palaver/<server>.access.log;
error_log /var/log/nginx/palaver/<server>.error.log;
location /.well-known/acme-challenge/ {
root /var/www/html;
}
location / {
return 301 https://$host$request_uri;
}
}
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name <domain>;
ssl_certificate /etc/letsencrypt/live/palaver.social/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/palaver.social/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
access_log /var/log/nginx/palaver/<server>.access.log;
error_log /var/log/nginx/palaver/<server>.error.log;
# largest default body: a minutes update, 1 MiB
client_max_body_size 2m;
# server push, one WebSocket per client
location = /api/events {
proxy_pass http://127.0.0.1:<port>;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 1h;
proxy_send_timeout 1h;
}
# profile pictures, server icon: 5 MiB
location ~ ^/api/(me/avatar|server/icon)$ {
client_max_body_size 5m;
proxy_pass http://127.0.0.1:<port>;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
# attachments: 25 MiB
location ~ ^/api/channels/[0-9]+/attachments$ {
client_max_body_size 25m;
proxy_pass http://127.0.0.1:<port>;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
location /api/ {
proxy_pass http://127.0.0.1:<port>;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
# LiveKit signalling, shared; the trailing slash strips /livekit
location /livekit/ {
proxy_pass http://127.0.0.1:7880/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_read_timeout 1h;
proxy_send_timeout 1h;
}
include snippets/palaver-web.conf;
}
Enable, check and load it.
sudo ln -sf /etc/nginx/sites-available/palaver-<server> /etc/nginx/sites-enabled/palaver-<server>
sudo nginx -t && sudo systemctl reload nginx
10. Start
Start the server.
sudo systemctl enable --now palaverd@<server>
Check that it answers; expected: JSON.
curl -fsS http://127.0.0.1:<port>/api/registration
11. First admin
Set the server's name and subtitle.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env profile -name '<title>' -subtitle '<subtitle>'
Create an invite code for the first admin; single use, valid 7 days.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env invite -role Admin -valid 168h
- register: Palaver app → server
https://<domain>→ Register → code - first admin = server owner
- account registered without admin (code without
-role Admin): give it the role
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env grant <username> Admin
12. Check
Run doctor; expected: ok on every line.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env doctor
Check that the main server still answers.
sudo -u palaver /opt/palaver/bin/palaverd -env /opt/palaver/etc/palaverd.env doctor
List servers
Names of the further servers.
ls /opt/palaver/instances/
Domain and port of every server.
sudo sh -c 'grep -H -E "^PALAVER_(PUBLIC_URL|LISTEN)=" /opt/palaver/etc/palaverd.env /opt/palaver/instances/*/palaverd.env'
Name and subtitle of one server.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env profile
State of every server.
systemctl list-units --all 'palaverd*'
Backup
- database: all data of the server
/opt/palaver/instances/<server>: configuration, LiveKit key
Dump the database.
sudo -u palaver-<server> pg_dump -Fc palaver_<server> > palaver-<server>-2026-10-11.dump
Save the configuration.
sudo tar -czf palaver-<server>-etc-2026-10-11.tar.gz -C /opt/palaver/instances <server>
Restore
Prerequisite: server with the same name and domain, steps 1–11.
Stop it.
sudo systemctl stop palaverd@<server>
Destructive: delete the database of the new server (palaver_<server>, all its accounts and messages).
sudo -u postgres dropdb palaver_<server>
Create it again and load the dump.
sudo -u postgres createdb -O palaver-<server> palaver_<server>
sudo -u palaver-<server> pg_restore -d palaver_<server> palaver-<server>-2026-10-11.dump
Start it.
sudo systemctl start palaverd@<server>
Remove a server
Show the domain and the LiveKit key (<livekit-key>).
sudo grep -E '^PALAVER_(PUBLIC_URL|LIVEKIT_API_KEY)=' /opt/palaver/instances/<server>/palaverd.env
Show the site's certificate; own certificate: name <domain>.
grep ssl_certificate /etc/nginx/sites-available/palaver-<server>
Back up first: Backup.
Stop and disable the service.
sudo systemctl disable --now palaverd@<server>
Remove the nginx site and reload nginx.
sudo rm /etc/nginx/sites-enabled/palaver-<server> /etc/nginx/sites-available/palaver-<server>
sudo nginx -t && sudo systemctl reload nginx
Destructive: delete the database palaver_<server> (all accounts, messages, attachments) and its role palaver-<server>.
sudo -u postgres dropdb palaver_<server>
sudo -u postgres dropuser palaver-<server>
Destructive: delete the server's LiveKit key; open /opt/palaver/etc/livekit.yaml in an editor.
sudo vi /opt/palaver/etc/livekit.yaml
Remove:
- under
keys:the line<livekit-key>: …
Restart LiveKit; calls on the other servers drop briefly.
sudo systemctl restart livekit
Destructive: delete the configuration /opt/palaver/instances/<server> and the user palaver-<server>.
sudo rm -r /opt/palaver/instances/<server>
sudo userdel palaver-<server>
Destructive: delete the certificate; only an own one (<domain>), never the wildcard certificate.
sudo certbot delete --cert-name <domain>
Destructive: delete nginx's logs of the server (/var/log/nginx/palaver/<server>.*).
sudo sh -c 'rm /var/log/nginx/palaver/<server>.access.log* /var/log/nginx/palaver/<server>.error.log*'
After the last further server
Remove the empty directory.
sudo rmdir /opt/palaver/instances
- before uninstalling the main server (Palaver's
INSTALL.md, Uninstall; release files: Palaver'sINSTALL-TARBALL.md, Uninstall): remove every further server
Optional: unknown names to the main server
- for: wildcard DNS record and certificate for the main server's domain
- unknown names (typos): redirect to the main server instead of nginx's first site
Check that the certificate covers *.palaver.social.
sudo openssl x509 -noout -ext subjectAltName -in /etc/letsencrypt/live/palaver.social/fullchain.pem
Check whether the distribution's placeholder site claims default_server.
grep default_server /etc/nginx/sites-enabled/default
If so: disable it.
sudo rm /etc/nginx/sites-enabled/default
Open /etc/nginx/sites-available/palaver-catch-all in an editor.
sudo vi /etc/nginx/sites-available/palaver-catch-all
Content:
server {
listen 80 default_server;
listen [::]:80 default_server;
server_name _;
location /.well-known/acme-challenge/ { root /var/www/html; }
location / { return 301 https://palaver.social/; }
}
server {
listen 443 ssl default_server;
listen [::]:443 ssl default_server;
server_name _;
ssl_certificate /etc/letsencrypt/live/palaver.social/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/palaver.social/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
return 301 https://palaver.social/;
}
Enable, check and load it.
sudo ln -sf /etc/nginx/sites-available/palaver-catch-all /etc/nginx/sites-enabled/palaver-catch-all
sudo nginx -t && sudo systemctl reload nginx
Optional: wildcard certificate
- one certificate for the main domain and every name under it (
palaver.social,*.palaver.social) - certbot DNS challenge
- palaver.social: certbot snap, plugin
certbot-dns-hetzner-cloud, credentials/root/.secrets/hetzner.ini, deploy hooksystemctl reload nginx - one certbot per host only
List the certificates and the names they cover.
sudo certbot certificates
Check the deploy hook of the wildcard certificate.
sudo grep -E 'authenticator|renew_hook|deploy_hook' /etc/letsencrypt/renewal/palaver.social.conf
Files
| Path | Content |
|---|---|
/usr/lib/systemd/system/palaverd@.service |
unit template (package palaver-server); release files: /etc/systemd/system/ |
/opt/palaver/instances/<server>/palaverd.env |
configuration (user palaver-<server> only) |
/opt/palaver/etc/livekit.yaml |
one key per server under keys: |
/etc/nginx/sites-available/palaver-<server> |
nginx site |
/etc/nginx/snippets/palaver-web.conf |
web client, CSP for the site's own name (main server) |
/etc/nginx/sites-available/palaver-catch-all |
unknown names (optional) |
/var/log/nginx/palaver/<server>.access.log, <server>.error.log |
nginx logs (rotated by Palaver's /etc/logrotate.d/palaver) |
Troubleshooting
Doctor of one server.
sudo -u palaver-<server> /opt/palaver/bin/palaverd -env /opt/palaver/instances/<server>/palaverd.env doctor
What palaverd says.
sudo journalctl --namespace=palaver -u palaverd@<server> -n 100
What nginx says.
sudo tail -n 50 /var/log/nginx/palaver/<server>.error.log
| Symptom | Cause |
|---|---|
useradd: invalid user name |
name too long (at most 24 characters) |
| voice fails on this server only | key missing in livekit.yaml or LiveKit not restarted after step 6 |
| voice fails on every server | livekit.yaml broken by an edit: sudo journalctl --namespace=palaver -u livekit -n 50 |
| another server's site answers | server_name or the symlink in sites-enabled missing |
| web client without voice in the browser | PALAVER_LIVEKIT_URL not on the server's own domain (doctor reports it) |