June 5, 20179 yr Has any one tried to use the web VNC to access any vms yet? not working for me. just installed rc2 with no problems during install apart from no web vnc access. just displays blank screen...
June 5, 20179 yr WebVNC didn't work for me prior to upgrade and I was never sure why. It did initially but at some point stopped working, I was running 6.3.4. After upgrade to RC2 it still doesn't work. But I use a VNC client when needed and connect to the same details the webvnc tries to connect to.
June 5, 20179 yr 1 hour ago, Tuftuf said: WebVNC didn't work for me prior to upgrade and I was never sure why. It did initially but at some point stopped working, I was running 6.3.4. After upgrade to RC2 it still doesn't work. But I use a VNC client when needed and connect to the same details the webvnc tries to connect to. It works here also. As yours didn't work before the update I would say that it's not a problem related to the update. You might have an adblocker or anti-virus blocking it. Might also be your problem @sarf
June 5, 20179 yr 12 minutes ago, saarg said: It works here also. As yours didn't work before the update I would say that it's not a problem related to the update. You might have an adblocker or anti-virus blocking it. Might also be your problem @sarf It may well be unrelated in my case and not a concern for myself. Simply says Server disconnected code 1006. I can say I get the same result on four machines. Work laptop running AV Mac not really running anything Windows VM with GPU, Not running anything other than windows and games. Windows VM running blue iris and accessed with TeamViewer... Edited June 5, 20179 yr by Tuftuf
June 5, 20179 yr My webVNC isn't working either as it's trying to attach to port 5700 rather than 5900 reported by unraid as the used port. External VNC client is working fine and when trying to identify port with 5900 it still doesn't work via webui.
June 6, 20179 yr 4 hours ago, phbigred said: My webVNC isn't working either as it's trying to attach to port 5700 rather than 5900 reported by unraid as the used port. External VNC client is working fine and when trying to identify port with 5900 it still doesn't work via webui. Port 5700 is correct for the noVNC client, so that is not the problem. There always seems to be a port in the 5900 range for native VNC clients and a corresponding one in the 5700 range for the web client.
June 6, 20179 yr The noVNC client in unRAID 6.4 will now proxy the websocket request through nginx (Eric explained this to me). This requires that name resolution works properly. For example if you access the GUI using //tower then the browser must know how to resolve the name "tower" into the correct IP address. You can test your VNC by entering the GUI using the IP address of unRAID.
June 6, 20179 yr Interesting.. Tower did not resolve on my network, I've added the option for DHCP hostnames to be registered. Before change, MBP:~ feck$ ping tower ping: cannot resolve tower: Unknown host After change MBP:~ feck$ ping tower PING tower.localdomain (172.19.1.219): 56 data bytes If I access the UI on http://172.19.1.219 WebVNC fails. If I access the UI on https://172.19.1.219 WebVNC works if I access the UI on http://tower or https://tower WebVNC works Also I you take the failing URL http://172.19.1.219/plugins/dynamix.vm.manager/vnc.html?autoconnect=true&host=172.19.1.219&port=5701 -- Fails and edit the hostname to tower it then works over http. http://tower/plugins/dynamix.vm.manager/vnc.html?autoconnect=true&host=172.19.1.219&port=5701 -- Works
June 7, 20179 yr 4 hours ago, Tuftuf said: Personally I class this as a configuration issue and the issue is solved. I have to agree here.
June 7, 20179 yr 21 hours ago, Tuftuf said: Tower did not resolve on my network, I've added the option for DHCP hostnames to be registered. How did you do this? Is this an Unraid setting?
June 7, 20179 yr It's not an Unraid setting. That's a difficult one to answer, it depends on what router or dhcp server you have. For example when I used an Asus ac66u router, the important setting was Advertise routers IP in addition to user specified DNS set to no. I'm using pfsense today and that was ticking the option register dhcp hostnames. If you only use one computer to access Unraid a workaround would be adding it into your own hostfile. Google "modify host file windows"
June 8, 20179 yr I had unraid on port 81, I had to change back to port 80 to get WebVNC to work. Setting docker containers to their own IPs freed me up to do that. Edited June 8, 20179 yr by smdion
June 8, 20179 yr I have the same issue accessing it on my test server's VM (I don't have VM's on my production server so can't test there). I typically use the IP address to access that machine, and unless I use HTTPS to access it, WebVNC gives me the disconnected error. With HTTPS, or a real VNC client, it works as it should.
Archived
This topic is now archived and is closed to further replies.