kasmtech
new install of ubuntu 22.0.4 and get cert error
my server is ubuntu 22.0.4 and just did a fresh install and got this error while I choose the desktop environment to run which I choose gnome /etc/ssl/private/ssl-cert-snakeoil.key: certificate file doesn't exist or isn't a file
By default we use the OS snakeoil cert. Either the ssl-cert package is not installed on the system, you did not make your user a member of the ssl-cert group (per the install instructions), or you did not disconnect and reconnect to the server to ensure the group membership change is applied to your current session.
You don't have to use the snakeoil certs, but that is generally the easiest way. You may alternatively use openssl to generate your own SSL certs, or obtain a proper cert signed by a public CA, then configure Kasm to use those certs instead.
To do that add the appropriate settings in /etc/kasmvnc/kasmvnc.yaml
See the docs under network.ssl https://github.com/kasmtech/KasmVNC#configuration
I don't know why but this worked
sudo gpasswd -a myusername ssl-cert
sudo chown root:ssl-cert /etc/ssl/private/ssl-cert-snakeoil.key
sudo chmod 740 /etc/ssl/private/ssl-cert-snakeoil.key
even though I had already ran
# addgroup myusername ssl-cert
Adding user `myusername' to group `ssl-cert' ...
Adding user myusername to group ssl-cert
Done.
For what it's worth, I had a persistent version of the issue in the OP and it was because I had defined a "new" user when kasm asked; I should have just put in my current user's credentials.
The fix was to use vncpasswd -u kasmuser -d to delete the non-existent kasmuser from its registry, and then to add my normal user credentials when kasm vnc asks for them.
It's possible that some combination of sudo apt remove kasmvncserver and sudo apt autoremove also helped clear some persistent broken cached variables.
