With RC4, I am unable to connect to noVNC with 3 different Chrome clients (error 1006...see screenshot).  IE and TightVNC work fine.  The previous unraid version I had installed (v6b15) did not have this issue and I never had rc1, rc2 or rc3 installed so I cannot speak to those.  Nothing has changed on my internal network.  I can reproduce on a clean build with no plugins or docker containers installed.

 

Chrome Version:  43.0.2357.81 m

 

 

Here is the XML from an impacted VM:

 

<domain type='kvm' id='5'>
  <name>PVRSERVER</name>
  <uuid>27f40955-89c4-5eae-6440-8469608fdce0</uuid>
  <description>PVR</description>
  <metadata>
    <vmtemplate name="Custom" icon="ubuntu.png" os="ubuntu"/>
  </metadata>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='12'/>
    <vcpupin vcpu='1' cpuset='13'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-2.3'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='2' threads='1'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/VMs/PVRSERVER/vdisk1.img'/>
      <backingStore/>
      <target dev='hdb' bus='virtio'/>
      <boot order='1'/>
      <alias name='virtio-disk1'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/Images/mythbuntu-14.04.2-desktop-amd64.iso'/>
      <backingStore/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <alias name='sata0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb0'/>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0' multifunction='on'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='sata0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='dmi-to-pci-bridge'>
      <alias name='pci.1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <alias name='pci.2'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </controller>
    <filesystem type='mount' accessmode='passthrough'>
      <source dir='/mnt/'/>
      <target dir='mnt'/>
      <alias name='fs0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
    </filesystem>
    <interface type='bridge'>
      <mac address='52:54:00:a9:7b:12'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target port='0'/>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/PVRSERVER.org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='vmvga' vram='16384' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

This is not a bug with unRAID as I do not have this issue when using Chrome from either a Mac OS X or Windows 7/8 device.  I think there is something wrong with your browser or browser settings that may be causing this problem.

 

Edit:  That said, I'll leave this post in defect reports for now to see if anyone else comes in reporting it, but if not, we'll move it to general support for further diagnosis.

This is not a bug with unRAID as I do not have this issue when using Chrome from either a Mac OS X or Windows 7/8 device.  I think there is something wrong with your browser or browser settings that may be causing this problem.

 

Edit:  That said, I'll leave this post in defect reports for now to see if anyone else comes in reporting it, but if not, we'll move it to general support for further diagnosis.

I am getting similar experience using both Chrome and IE.  I have switched to using UltraVNC instead as it seems to always work.  Having said that it would be much more convenient if noVNC could start working reliably for me like it used to.

This is really weird that you guys are having issues that I can't recreate. Hmm, will need to ponder this some more.

Yeah...I never had the issue with Chrome.  It just started.

 

Also, something else I have been seeing...is it normal for noVNC to disconnect after about 30 seconds or so of inactivity?  Is there a timeout value?  I am seeing this behavior in IE and don't ever recall seeing it previously.

 

John

I uninstalled Chrome from one of my workstations (also deleted history) and reinstalled (Version 43.0.2357.81 m).  I am once again able to connect to noVNC in Chrome.

 

I can mark this solved or would you rather sit on it for a day or two?

 

John

I uninstalled Chrome from one of my workstations (also deleted history) and reinstalled (Version 43.0.2357.81 m).  I am once again able to connect to noVNC in Chrome.

That is the version I have installed that is not working for me.

 

I am currently 'avoiding' the issue by using the UltraVNC client.  I would like to get the noVNC option working but I do not really know how to go about debugging what my issue with noVNC actually is. Any guidance in this area would be appreciated.

When I reinstalled Chrome, the same version came down that I was having the issue with .  So I am starting to think that it was some kind of configuration/setting/history within Chrome that was causing the issue.

I also encountered an issue with VNC in chrome to my VMs.

It worked fine in opera, IE and firefox.

 

For me the solution was to disable Adblock Plus on the unraid web. After that connections could be made in chrome through VNC.

 

So give it a try. I'd imagine similar plugins in chrome, can cause this as well.

I know the thread is old, but may be useful for some. I had a proxy setup for chrome, this broke the websocket connection to noVNC, making sure my unraid server was in the direct connections cleared this up for me.