multivnc icon indicating copy to clipboard operation
multivnc copied to clipboard
verified publisher icon bk138

Does not connect to WayVNC default setup

Open bk138 opened this issue 7 months ago • 6 comments

... which also seems to be the standard way of doing VNC on Raspbi nowadays.

Tried to repro with sway and wayvnc

WLR_BACKENDS=headless WLR_LIBINPUT_NO_DEVICES=1 sway

and then following https://github.com/any1/wayvnc/blob/master/README.md#vencrypt-tls

(similar to https://www.raspberrypi.com/documentation/computers/remote-access.html#vnc )

We get:

04/05/2025 15:34:01 VNC server supports protocol version 3.8 (viewer 3.8)
04/05/2025 15:34:01 We have 1 security types to read
04/05/2025 15:34:01 0) Received security type 19
04/05/2025 15:34:01 Selecting security type 19 (0/1 in the list)
04/05/2025 15:34:01 Selected Security Scheme 19
04/05/2025 15:34:01 Got VeNCrypt version 0.2 from server.
04/05/2025 15:34:01 We have 1 security types to read
04/05/2025 15:34:01 0) Received security type 262
04/05/2025 15:34:01 Selecting security type 262
04/05/2025 15:34:01 GnuTLS version 3.7.9 initialized.
04/05/2025 15:34:01 something else than username and password required for authentication
  • [x] check how to satisfy rfbCredentialTypeX509: https://github.com/LibVNC/libvncserver/commit/b5dfe0d91ee68d2b261837543c2416cf0b6abedf for GnuTLS, OpenSSL already had similar functionality
  • [ ] check how to display cert fingerprint to user and let them accept
  • [ ] fix for desktop version
  • [ ] fix for mobile version

bk138 avatar May 04 '25 13:05 bk138

May this be the same issue for I can't connect to RealVNC server at all? I can connect to the TigerVNC server but then I get randomly disconnected after a while. Tested on RaspberryPI 4.

gianmaxfactor avatar May 09 '25 10:05 gianmaxfactor

May this be the same issue for I can't connect to RealVNC server at all? I can connect to the TigerVNC server but then I get randomly disconnected after a while. Tested on RaspberryPI 4.

It's basically the missing VeNCrypt X509 implementation in MultiVNC and (partly) LibVNCClient. If you can provide the logs we can have a look at the security scheme the server indicates. What the numbers mean is listed in https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst

bk138 avatar May 09 '25 12:05 bk138

Thank you Christian, I would like to cooperate although I am quite a newbie at Linux. However I found a very simple clue at /var/log/vncserver-x11.log which just says "Client needs protocol version 3.8"...

<14> 2025-05-09T12:42:38.290Z raspberrypi vncserver-x11[589]: TcpListenerManager: listening on 0.0.0.0::5900
<11> 2025-05-09T12:42:38.296Z raspberrypi vncserver-x11[589]: SModuleUpdateNotification: Last checked for updates more than 150 days ago
<13> 2025-05-09T12:46:29.143Z raspberrypi vncserver-x11[589]: Connections: connected: 10.147.17.5::49336 (TCP)
<14> 2025-05-09T12:46:29.161Z raspberrypi vncserver-x11[589]: SConnection: Client needs protocol version 3.8
<13> 2025-05-09T12:46:29.185Z raspberrypi vncserver-x11[589]: Connections: disconnected: 10.147.17.5::49336 (TCP) ([EndOfStream] Disconnection by client)

gianmaxfactor avatar May 09 '25 12:05 gianmaxfactor

@gianmaxfactor have a look at the client logs. Multivnc for desktop has a menu entry to show them.

bk138 avatar May 09 '25 13:05 bk138

Thank you @bk138 , I forgot to mention my attempts were made from the android flavor (v2.1.8); however, I have installed the windows one (only found the v0.5) and I can't connect either; these are all the logs retrieved from mVNC, not much talkative maybe, hope they help.

09/05/2025 04:36:15 PM VNC server supports protocol version 5.0 (viewer 3.8)
09/05/2025 04:36:15 PM We have 4 security types to read
09/05/2025 04:36:15 PM 0) Received security type 6
09/05/2025 04:36:15 PM 1) Received security type 130
09/05/2025 04:36:15 PM 2) Received security type 13
09/05/2025 04:36:15 PM 3) Received security type 5
09/05/2025 04:36:15 PM Unknown authentication scheme from VNC server: 6, 130, 13, 5

gianmaxfactor avatar May 09 '25 14:05 gianmaxfactor

Hope this is relevant; I'm trying to reach X11 realvnc:

Hello, This [AVNC] issue still breaks the stock VNC setup for the most recent 64 bit Raspberry OS Lite (which is based on Debian 12 Bookworm). I have previously installed xdm and i3, run systemctl set-default graphical.target, confirmed booting into grapical and logging into i3. I enabled VNC through raspi-config menu. This still installed realVNC, not wayVNC.

$ uname -a
Linux af0bl 6.12.25+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux
$ apt list --installed | grep vnc
realvnc-vnc-server/stable,now 7.13.1.57 arm64 [installed]

Sending a connection attempt from AVNC over wifi to the the Pi, results in these entries in /var/log/vncserver-x11.log:

<13> 2025-06-08T13:36:43.852Z af0bl vncserver-x11[8225]: Connections: connected: 192.168.1.70::43934 (TCP)
<14> 2025-06-08T13:36:43.864Z af0bl vncserver-x11[8225]: SConnection: Client needs protocol version 3.8
<13> 2025-06-08T13:36:43.870Z af0bl vncserver-x11[8225]: Connections: disconnected: 192.168.1.70::43934 (TCP) ([EndOfStream] Disconnection by client)

and these logs within AVNC:

06-08 08:36:44.315  8430 10182 I NativeVnc: Received protocol version 5.0
06-08 08:36:44.316  8430 10182 I NativeVnc: VNC server supports protocol version 5.0 (viewer 3.8)
06-08 08:36:44.321  8430 10182 I NativeVnc: We have 2 security types to read
06-08 08:36:44.321  8430 10182 I NativeVnc: 0) Received security type 13
06-08 08:36:44.321  8430 10182 I NativeVnc: 1) Received security type 5
06-08 08:36:44.321  8430 10182 E NativeVnc: Unknown authentication scheme from VNC server: 13, 5
06-08 08:36:44.321  8430 10182 E VncViewModel: Connection failed
06-08 08:36:44.321  8430 10182 E VncViewModel: java.io.IOException: Authentication failed
06-08 08:36:44.321  8430 10182 E VncViewModel: 	at com.gaurav.avnc.vnc.VncClient.connect(VncClient.kt:117)
06-08 08:36:44.321  8430 10182 E VncViewModel: 	at com.gaurav.avnc.viewmodel.VncViewModel.access$connect(VncViewModel.kt:235)
06-08 08:36:44.321  8430 10182 E VncViewModel: 	at com.gaurav.avnc.viewmodel.VncViewModel$launchConnection$1.invoke(VncViewModel.kt:6)
06-08 08:36:44.321  8430 10182 E VncViewModel: 	at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:3)

Originally posted by @AF0BL in #306

Following the AVNC author's replied link, I generated a VNC password, explicitly set Authentication=VncAuth and/or Encryption=PreferOn in /root/.vnc/config.d/vncserver-x11, and restarted the service. With the encryption line, it now fails with Unknown encryption scheme from VNC server: 13, 5, 6, 130.

It seems strange to me that my scheme order (as logged by AVNC viewer) is flipped from the 6, 130, 13, 5 that windows multivnc viewer logged for @gianmaxfactor.

I did try to connect to the pi's realvnc-server from Android multivnc but failed. Realvnc logs for the multivnc attempt match my above quoted AVNC attempts. I didnt see Android multivnc logs.

AF0BL avatar Jun 10 '25 01:06 AF0BL