search

zocker-160 / pyQVNCWidget

VNC Widget for Python using PyQt5
GNU General Public License v3.0
14 stars 7 forks source link

Issue when connecting with RealVNC Server of Raspberry Pi #5

Closed kazemiprince closed 1 year ago

kazemiprince commented 1 year ago

Hope you're fine. I'm trying to connect to a sever(it's on raspberry pi) but I need to login with username and password but couldn't find how to do it. trying with password only will give this exception: qvncwidget.rfb.RFBHandshakeFailed: b'No configured security type is supported by 3.3 VNC Viewer'

zocker-160 commented 1 year ago

kinda known issue:

Raspberry Pi uses RealVNC Server which sadly does not comply with the RFB 3.3 protocol, because it does enforce an encrypted connection and refuse it otherwise, which according to RFB 3.3 is optional and not required.

This VNC client is actually not the only one with that issue, since even a very known VNC client like Remmina fails to connect to the RealVNC Server shipped with a Raspberry Pi.

Given that this widget does only support the absolute minimum of the RFB specification, this is not going to work without some significant effort to implement an encrypted connection.

zocker-160 commented 1 year ago

UPDATE:

I actually managed to make it work by changing some settings. This didn't work in the past, so I am a bit surprised.

You need to disable encryption in the options and set the password from UNIX to VNC.

I think I will add a note to the readme mentioning this limitation.

EDIT: after doing a bit of testing, it seems a bit buggy, I will look into that.

slevon commented 1 year ago

Hey, just whated to confirm your solution. I changed the authentication of RealVNC to VNC Password and was able to connect to the RPi. However, I do not get an entire desktop, but only the top bar, that I can interact with. See screenshot image

If you need any more information on that, just let me know.

zocker-160 commented 1 year ago

Yes I know, as I said in my comment above, it is bugged and I sadly did not have the time to look into it yet.

It works fine with any other VNC server I have tested so far, only RealVNC on the PI has this weird issue.

zocker-160 commented 1 year ago

fixed in v0.3.x