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

Hi,

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

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?

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

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.

Problem solved with x509 certificates.