VNC Failed to connect to server (code: 1006) with cluster IP

[GabrielDias (Roman)]

Hi,

I find this topics, but it doesn`t solve my problem.

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

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

VNC Failed to connect to server (code: 1006)

Hi, I have imported 2 virtual machines. If I try to open VNC console on one of this, I can. But, if i try to open VNC console with the other VM I have this error: VNC Failed to connect to server (code: 1006) Any idea? In all machines I have configured: remotedisplay.vnc.enabled = "TRUE" remotedisplay.vnc.ip = "0.0.0.0" remotedisplay.vnc.port = “500x”

VNC noVNC ready: native WebSockets, canvas rendering Error?

Ok! so firewalld is not running. What about iptables just to be sure? What’s shown if you run: systemctl status iptables If it says not-found… try to check if you can reach 5900 port on the node from the frontend. You can install nmap in the frontend: yum install nmap and try to run: nmap -p 5900 X.X.X.X changing X.X.X.X with the IP of your node, let’s see what happens. Cheers

Vnc server 1006

Hi everyone, i have a problem, i’m trying to create an environment opennebula with this guide, http://docs.opennebula.org/4.14/design_and_installation/quick_starts/qs_ubuntu_kvm.html1. I doing step by step and I was stuck. When I want to connect to my machine via VNC I get an error : Failed to connect to server (code: 1006) [image] Help me solve this problem. Thanks!

Cannot open VNC console

I could set the graphic to the machine and now I get the vnc icon. But I try to connect and have this error: Failed to connect to server (code: 1006) I installed the sunstone and continuous alike. Any suggestions? Besides, there is a way to configure the graphic part for all imported machines? Or the only way is to do machine by machine? Thanks!

I use corosync + pacemaker with OpenNebula.
Each server has own IP, but cluster IP - 192.168.2.139
OpenNebula 5.2.1

192.168.2.130 CloudKVM-1 
192.168.2.131 CloudKVM-2 
192.168.2.132 CloudKVM-3 
192.168.2.137 CloudManage 
10.0.10.1 CephManage 
10.0.10.11 CephKVM-1 
10.0.10.22 CephKVM-2 
10.0.10.33 CephKVM-3
10.0.10.111 CloudNAS

[ceph@CloudKVM-1 ~]$ sudo crm configure show
node 1: CephKVM-1
node 2: CephKVM-2
node 3: CephKVM-3
primitive ClusterIP IPaddr2 \
        params ip=192.168.2.139 cidr_netmask=23 \
        op monitor interval=30s
primitive opennebula-novnc_p systemd:opennebula-novnc \
        op monitor interval=60s timeout=100s \
        op start interval=0 timeout=120s \
        op stop interval=0 timeout=120s
primitive opennebula-sunstone_p systemd:opennebula-sunstone \
        op monitor interval=60s timeout=100s \
        op start interval=0 timeout=120s \
        op stop interval=0 timeout=120s
primitive opennebula_p systemd:opennebula \
        op monitor interval=60s timeout=100s \
        op start interval=0 timeout=120s \
        op stop interval=0 timeout=120s
group Opennebula_HA ClusterIP opennebula_p opennebula-sunstone_p opennebula-novnc_p \
        meta target-role=Started
property cib-bootstrap-options: \
        have-watchdog=false \
        dc-version=1.1.15-11.el7_3.2-e174ec8 \
        cluster-infrastructure=corosync \
        stonith-enabled=false \
        no-quorum-policy=ignore \
        last-lrm-refresh=1485025411

oned.conf

LISTEN_ADDRESS = "0.0.0.0"

sunstone-server.conf

:host: 0.0.0.0
:port: 9869

Sunstone panel opens without problem. All works, but when I try to connect via VNC - get error “VNC Failed to connect to server (code: 1006)”

What did I do to make it work?

[feldsam (Kristian Feldsam)]

Hello, on which nodes VMs runs? Sunstone VNC on background ust connect to node where VM run. So server where opennebula and sunstone run need connection to compute node where VM is running. Also check firewall

[GabrielDias (Roman)]

Each VM may randomly running at one of the 3 nodes.
Firewall disabled permanently.

Sunstone panel running at 3 hosts: 192.168.2.130, 192.168.2.131 and 192.168.2.132, but have ClusterIP with 192.168.2.139.
Respectively sunstone opens at http://192.168.2.139:9869/

As you can see, 3 services OpenNebula including at config corosync and each server will get this ClusterIP.

[GabrielDias (Roman)]

Problem solved with x509 certificates.