wayvnc is broken due to a bug in one of the systemd service files.
The following script failed to call the second script due to some logic flaw.
The fix was to do manually what the second script does
/usr/lib/systemd/system/wayvnc-generate-keys.service
/usr/sbin/wayvnc-generate-keys.sh
Do this to fix it:
mkdir ~/temp
cd temp
ssh-keygen -m pem -f rsa_key.pem -t rsa -N ""
ls -al
total 16
drwxr-xr-x 2 jan jan 4096 Jan 23 22:43 .
drwx------ 24 jan jan 4096 Jan 23 22:42 ..
-rw------- 1 jan jan 2455 Jan 23 22:43 rsa_key.pem
-rw-r--r-- 1 jan jan 563 Jan 23 22:43 rsa_key.pem.pub
rm rsa_key.pem.pub
openssl req -x509 -newkey rsa:4096 -sha256 -days 3650 -nodes -keyout tls_key.pem -out tls_cert.pem -subj /CN=mypi5 -addext subjectAltName=DNS:localhost,DNS:mypi5,IP:<put your IP address here>
sudo chown root:vnc rsa_key.pem tls_key.pem tls_cert.pem
sudo chmod 640 rsa_key.pem tls_cert.pem tls_key.pem
ls -al
total 20
drwxr-xr-x 2 jan jan 4096 Jan 23 22:49 .
drwx------ 24 jan jan 4096 Jan 23 22:49 ..
-rw-r----- 1 root vnc 2455 Jan 23 22:43 rsa_key.pem
-rw-r----- 1 root vnc 1842 Jan 23 22:49 tls_cert.pem
-rw-r----- 1 root vnc 3272 Jan 23 22:49 tls_key.pem
sudo mv * /etc/wayvnc
sudo systemctl stop wayvnc.service
sudo systemctl enable wayvnc.service
sudo systemctl start wayvn.service
Now it can be reache from tigervnc from ubuntu 22.04
login complains about the server doesnt match but that can just be overridden. It is probably something in the key creation I did that was not quite ok. But it works flawlessly.
Somebody ought to fix that script. It is not rocket science.
The following script failed to call the second script due to some logic flaw.
The fix was to do manually what the second script does
/usr/lib/systemd/system/wayvnc-generate-keys.service
/usr/sbin/wayvnc-generate-keys.sh
Do this to fix it:
mkdir ~/temp
cd temp
ssh-keygen -m pem -f rsa_key.pem -t rsa -N ""
ls -al
total 16
drwxr-xr-x 2 jan jan 4096 Jan 23 22:43 .
drwx------ 24 jan jan 4096 Jan 23 22:42 ..
-rw------- 1 jan jan 2455 Jan 23 22:43 rsa_key.pem
-rw-r--r-- 1 jan jan 563 Jan 23 22:43 rsa_key.pem.pub
rm rsa_key.pem.pub
openssl req -x509 -newkey rsa:4096 -sha256 -days 3650 -nodes -keyout tls_key.pem -out tls_cert.pem -subj /CN=mypi5 -addext subjectAltName=DNS:localhost,DNS:mypi5,IP:<put your IP address here>
sudo chown root:vnc rsa_key.pem tls_key.pem tls_cert.pem
sudo chmod 640 rsa_key.pem tls_cert.pem tls_key.pem
ls -al
total 20
drwxr-xr-x 2 jan jan 4096 Jan 23 22:49 .
drwx------ 24 jan jan 4096 Jan 23 22:49 ..
-rw-r----- 1 root vnc 2455 Jan 23 22:43 rsa_key.pem
-rw-r----- 1 root vnc 1842 Jan 23 22:49 tls_cert.pem
-rw-r----- 1 root vnc 3272 Jan 23 22:49 tls_key.pem
sudo mv * /etc/wayvnc
sudo systemctl stop wayvnc.service
sudo systemctl enable wayvnc.service
sudo systemctl start wayvn.service
Now it can be reache from tigervnc from ubuntu 22.04
login complains about the server doesnt match but that can just be overridden. It is probably something in the key creation I did that was not quite ok. But it works flawlessly.
Somebody ought to fix that script. It is not rocket science.
Statistics: Posted by lupusmagnum — Tue Jan 23, 2024 11:02 pm