Help:VNC Failed to connect to server (code: 1006)

Community Support
1

what do i need? i have followed th equick start guide for ubuntu, 1 worker , 1 frontend server; vm seems to be running

thx

2

tomabroad forum@opennebula.org writes:

what do i need? i have followed th equick start guide for ubuntu, 1
worker , 1 frontend server; vm seems to be running

Generally, I saw the 1006 error when vnc SSL is activated but the
certificate is unknown to the browser.

If you have certificate enable in /etc/one/sunstone-server.conf then you
should try to connect to the websocket proxy:

https://<SUNSTONE>:29876

Then accept the certificate, it should result in a 405 error.

After that, retry to open a noVNC console.

Regards.

Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
signature.asc (342 Bytes)

3

Make sure the port is open as well

4

Hi! I have the same problem. Should I open the port on the host or the front-end machine? I got a bit confused

5

to do so
# service firewalld stop

on whichever machine you’re failing to reach

6

hope this makes it clearer:

your VM will be available on your hypervisor server on the VNC port defined in the template (basically port 5900 + ID of your VM. The VNC data is sent to the NoVNC proxy, which is running on your master server or sunstone-server.

so: VNC port 5900 on hypervisor --> novnc proxy --> Sunstone (port 29876)

You have activated SSL on the last part, probably with a self-signed cert. so you need to accept the risk in your browser when you connect for the first time: sunstone IP:29876 --> accept selfsigned cert. --> VNC over SSL is possible. So on your Sunstone server, you need to open port 29876 (for VNC) and the port for the sunstone web interface (default 9869, maybe 80 / 443 via http proxy).

hope this helps!