Bug #23977
RealVNC Viewer can't connect to VM VNC with auto quality enabled
Description
If you attempt to connect to the VM VNC port with RealVNC VNC Viewer you will get and error
"RFB protocol error: invalid message type 152"
If you then reconfigure the connection to use High Quality instead of Auto, it will connect correctly.
I'm guessing the VNC server doesn't support/understand the auto quality setting.
Tested on Mac OS X 10.11.6 with VNC® Viewer 6.1.0 (r27437) x64 (Apr 26 2017 11:04:58)
Associated revisions
Vnc hyveremote (#318)
- feat(middlewared/vm): Add libhyve-remote support for libvncserver.
Ticket: #23977, #24450, #25090 and #25700
- feat(middlewared/vm): Prepare middlewared to identify bhyve with fbuf and bhyve with libhyve-remote support.
- feat(middlewared/vm): As I probably will patch the OS, we don't need to handle two different bhyve binaries anymore.
- We don't need os.path anymore!
History
#1
Updated by Marcelo Araujo about 2 years ago
Updated by Marcelo Araujo - Status changed from Unscreened to Screened
- Priority changed from No priority to Nice to have
- Target version set to 11.0-U1
I bet that it is a screen resolution problem, by default we used to use 1024x768 but recently I added a new option where you can set the screen resolution for the VNC Device. This option would not land on RELEASE, it will be available only on Nightlies.
You can see more info here: https://bugs.freenas.org/issues/23894
I will keep this ticket open, I will test it to make sure it works.
Thank you!
#2
Updated by Stuart Espey about 2 years ago
Updated by Stuart Espey Marcelo Araujo wrote:
I bet that it is a screen resolution problem, by default we used to use 1024x768 but recently I added a new option where you can set the screen resolution for the VNC Device. This option would not land on RELEASE, it will be available only on Nightlies.
You can see more info here: https://bugs.freenas.org/issues/23894
I will keep this ticket open, I will test it to make sure it works.
Thank you!
Another user on the forum with the same issue, same solution:
https://forums.freenas.org/index.php?threads/vms-using-freenas-11-gui-error-connecting-via-vnc-at-linux-setup.54582/
#3
Updated by Don Sev about 2 years ago
Updated by Don Sev Stuart Espey wrote:
Another user on the forum with the same issue, same solution:
https://forums.freenas.org/index.php?threads/vms-using-freenas-11-gui-error-connecting-via-vnc-at-linux-setup.54582/
Yeah, that was me.
Switching to high quality in RealVNC's VNC Viewer solved the problem immediately. I was able to view the vnc on both mobile and PC. Highly recommend a note be added somewhere in the VM GUI, or at least in the documentation.
#4
Updated by Marcelo Araujo about 2 years ago
Don Sev wrote:
Stuart Espey wrote:
Another user on the forum with the same issue, same solution:
https://forums.freenas.org/index.php?threads/vms-using-freenas-11-gui-error-connecting-via-vnc-at-linux-setup.54582/Yeah, that was me.
Switching to high quality in RealVNC's VNC Viewer solved the problem immediately. I was able to view the vnc on both mobile and PC.
Great guys for all the report.
I didn't have enough time to debug this issue, I'm still wondering if there is any problem with screen resolution.
But this bug is a nice one to debug. I will keep you two updated with my progress as soon as I start to work on it.
Thanks again,
#5
Updated by Marcelo Araujo about 2 years ago
- Target version changed from 11.0-U1 to 11.2-BETA1
We might change to libvncserver that is something I'm working on. So, could not find yet the main reason of this problem.
I'm moving this issue targeting to 11.2.
#6
Updated by Daniel Hubbard about 2 years ago
Updated by Daniel Hubbard Marcelo Araujo wrote:
Don Sev wrote:
Stuart Espey wrote:
Another user on the forum with the same issue, same solution:
https://forums.freenas.org/index.php?threads/vms-using-freenas-11-gui-error-connecting-via-vnc-at-linux-setup.54582/Yeah, that was me.
Switching to high quality in RealVNC's VNC Viewer solved the problem immediately. I was able to view the vnc on both mobile and PC.
Great guys for all the report.
I didn't have enough time to debug this issue, I'm still wondering if there is any problem with screen resolution.But this bug is a nice one to debug. I will keep you two updated with my progress as soon as I start to work on it.
Thanks again,
Just wanted to confirm setting quality to high in the client worked or me as well. Luckily this was the second result from Google. Thanks for what you do!
#7
Updated by Philip Cook almost 2 years ago
Updated by Philip Cook - Seen in changed from 11.0-RC to 11.0-U2
Nice to know there is an easy workaround, but it would be nice if it just worked. Still in FreeNAS-11.0-U2 (e417d8aa5).
#8
Updated by Marcelo Araujo almost 2 years ago
Philip Cook wrote:
Nice to know there is an easy workaround, but it would be nice if it just worked. Still in FreeNAS-11.0-U2 (e417d8aa5).
There is a new lib for VNC that I want to integrate on FreeNAS at least on its version 11.2-RELEASE that will solve this problem.
#9
Updated by Marcelo Araujo over 1 year ago
- Status changed from Screened to Fix In Progress
I just added libhyve-remote on FreeNAS!
#10
Updated by Marcelo Araujo over 1 year ago
- Status changed from Fix In Progress to Ready For Release
- Target version changed from 11.2-BETA1 to 11.1
I added libhyve-remote and all the bits necessary to improve VNC server.
Python bits were reviewed by williamgr and C bits by kris.
#11
Updated by Dru Lavigne over 1 year ago
Updated by Dru Lavigne - Target version changed from 11.1 to 11.1-BETA1
#12
Updated by Dru Lavigne over 1 year ago
- Status changed from Ready For Release to Resolved
#13
Updated by Bonnie Follweiler over 1 year ago
Updated by Bonnie Follweiler - Needs QA changed from Yes to No
- QA Status Test Passes FreeNAS added
- QA Status deleted (
Not Tested)
Vnc hyveremote (#318)
Ticket: #23977, #24450, #25090 and #25700