r/kasmweb

Hello. I accidentally emptied RDP Private Key and RDP Private Signing Key settings in Kasm when I was trying to learn how to configure signed RDP connection to Kasm workspaces.

Now I don't know how to restore them. In frustration I also deleted RDP Public certificate and RDP Public signing certificate settings.

Am I done? Maybe there's a way to restore them? I have previous filesystem state made with rsync, before almost any changes (did mess up some passthrough.yml when tried to fix used ones, but it didn't help nevertheless).

Trying to do a multi server setup with a stand-alone remote DB - when attempting to initialise the remote DB the connection works fine at first: the `kasm` DB and `kasmapp` user both get created on my postgres instance. After this connectivity is lost, shell output below:

kasm_release/install.sh --accept-eula --role init_remote_db --db-hostname 172.17.0.1 --db-password $DATABASE_KASMAPP_USER_PASSWORD --db-master-password $DATABASE_SUPERUSER_PASSWORD --no-check-ports --no-db-ssl --use-static-images

Setting Role as init_remote_db
Setting Database Hostname as 172.17.0.1
Setting Default Database Password from stdin -Q
Using Database Master Password from stdin -G
Setting Database SSL to false
Checking if docker and docker compose are installed.
Docker is installed
29.7.0 is a supported version of docker.
Docker compose is installed
2.40.2 is a supported version of docker compose
Commands docker and docker compose detected, skipping Docker installation.
Dependency Installation Complete
Creating self-signed certificate at /opt/kasm/1.19.0/certs/kasm_nginx.*
Initializing Remote database
Docker network kasm_default_network already exists. Will not create
Initializing Database
Setting Seed file as /opt/kasm/1.19.0/conf/database/seed_data/default_properties.yaml
Using Database Master User
Using Database Master Password from stdin -G

WARNING!!!
__________________________

Contents of the existing database will be removed. This is irreversible!

Continue? (y/n) y
drop database if exists kasm;
DROP DATABASE
CREATE DATABASE
CREATE EXTENSION
time="2026-08-07T17:22:28Z" level=warning msg="/opt/kasm/1.19.0/docker/.conf/docker-compose-api.yaml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
2026-08-07 17:22:32,156 [INFO] root: Performing Database Connectivity Test
2026-08-07 17:23:17,187 [ERROR] root: Unable to initialize database connection.
[...]
2026-08-07 17:23:22,188 [ERROR] root: Max Connection Attempts Exceeded. Exiting

pg_hba.conf should allow the following relevant connections if I'm correct:

host all postgres 172.17.0.0/16 md5
host all postgres 172.18.0.0/16 md5
host kasm kasmapp 172.17.0.0/16 md5
host kasm kasmapp 172.18.0.0/16 md5

The interesting bit is that the 1.18.1 version works without any issues on the same server with the same remote DB out of the box. ( same install command )

Has anyone come across something similar? I looked through the changelog for 1.19.0, but couldn't see an obvious change that would cause this. I'm sure I'm missing an obvious bit somewhere...

I have a proxmox ve with kasm installed in a Debian LXC
Can I install wine in kasm to run an old game that works in windows 3.11/95/98?