# Federation VNC run vm error

**URL:** <https://forum.opennebula.io/t/federation-vnc-run-vm-error/1728>\
**Category:** Product Support\
**Created:** [January 27, 2016, 8:13pm UTC](https://forum.opennebula.io/t/federation-vnc-run-vm-error/1728 "2016-01-27T20:13:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![eduardo\_serrano](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/eduardo_serrano/32/4551_2.png) [@eduardo\_serrano](https://forum.opennebula.io/u/eduardo_serrano)\
**Post date:** [January 27, 2016, 8:13pm UTC](https://forum.opennebula.io/t/federation-vnc-run-vm-error/1728/1 "2016-01-27T20:13:30Z")

</div>

Good morning

Good day

mates

My problem is this

Federation with OpenNebula as master/slave. I have detected a error. running the Master Sunstone(172.16.1.232), I can change to the Slave Sunstone(172.16.1.246). It works well, but if we try to run the VNC console from any vm it fails(code: 1006 slave side).

I do not understand how to solve Could you explain me please!

Also as vnc direct traffic to the master / slave?  
Or what file should be set to this feature of the federation?  
By modifying the part of vnc\_proxy but without positive response.

currently the league thus shown a vm  
[http://172.16.1.232:9869/vnc?host=172.16.1.232&port=29876&token=18vlwzgi038ky02kiend&encrypt=no&title=prueba6&password=null](http://172.16.1.232:9869/vnc?host=172.16.1.232&port=29876&token=18vlwzgi038ky02kiend&encrypt=no&title=prueba6&password=null)

but I guess I should be this way  
[http://172.16.1.232:9869/vnc?host=172.16.1.246&port=29876&token=18vlwzgi038ky02kiend&encrypt=no&title=pru](http://172.16.1.232:9869/vnc?host=172.16.1.246&port=29876&token=18vlwzgi038ky02kiend&encrypt=no&title=pru)

OpenNebula version: 4.14  
I do not see any error in the logs.  
I do not have connectivity issues.  
no use ssl no https

Thanks for your support!

I currently use this platform as a test project, but want to participate this platform as project officer in my company

---

<div class="post-metadata">

**Author:** ![cmartin](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/cmartin/32/4278_2.png) [@cmartin](https://forum.opennebula.io/u/cmartin)\
**Post date:** [January 28, 2016, 4:12pm UTC](https://forum.opennebula.io/t/federation-vnc-run-vm-error/1728/2 "2016-01-28T16:12:25Z")

</div>

Hi,

> [@eduardo\_serrano](#):
>
> Federation with OpenNebula as master/slave. I have detected a error. running the Master Sunstone(172.16.1.232), I can change to the Slave Sunstone(172.16.1.246). It works well, but if we try to run the VNC console from any vm it fails(code: 1006 slave side).

If you are using the zone dropdown in the top-right corner, then you are still using the **master Sunstone** to contact the **slave oned**. This is different than connecting to the **slave sunstone**. In fact, you will notice that the slave sunstone can be stopped, and you will still have access to the **slave oned** from the **master sunstone**.

The arquitecture is explained here: [Data Center Federation — OpenNebula 4.14.2 documentation](http://docs.opennebula.org/4.14/advanced_administration/data_center_federation/introf.html)

Unfortunately, VNC does not work at the moment between different zones (see [Feature #2757: Make noVNC proxy work in a federation to access VMs in any zones - OpenNebula - OpenNebula Development pages](http://dev.opennebula.org/issues/2757)). Sunstone will fail to establish a VNC connection when you are switching to a zone different to where sunstone is running.  
You will need to point your browser to the **slave sunstone** , and this way you will have access to the local vnc proxy.

Regards

---

<div class="post-metadata">

**Author:** ![eduardo\_serrano](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/eduardo_serrano/32/4551_2.png) [@eduardo\_serrano](https://forum.opennebula.io/u/eduardo_serrano)\
**Post date:** [January 28, 2016, 6:30pm UTC](https://forum.opennebula.io/t/federation-vnc-run-vm-error/1728/3 "2016-01-28T18:30:41Z")

</div>

> [@cmartin](#):
>
> You will need to point your browser to the slave sunstone, and this way you will have access to the local vnc proxy.
> 
> Regards

In this part I did not understand,  
is it be the usual way to access?  
excuse my ignorance

Thank you  
for answer

greetings

---

<div class="post-metadata">

**Author:** ![cmartin](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/cmartin/32/4278_2.png) [@cmartin](https://forum.opennebula.io/u/cmartin)\
**Post date:** [February 1, 2016, 10:37am UTC](https://forum.opennebula.io/t/federation-vnc-run-vm-error/1728/4 "2016-02-01T10:37:39Z")

</div>

> [@eduardo\_serrano](#):
>
> In this part I did not understand, is it be the usual way to access?

If you need VNC support from sunstone, then yes, you will need a local sunstone in each zone. Instead of the nice zone dropdown in the top right corner, your users will need to access a different url for each zone.

Regards

---

<div class="post-metadata">

**Author:** ![eduardo\_serrano](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/eduardo_serrano/32/4551_2.png) [@eduardo\_serrano](https://forum.opennebula.io/u/eduardo_serrano)\
**Post date:** [February 6, 2016, 12:25am UTC](https://forum.opennebula.io/t/federation-vnc-run-vm-error/1728/5 "2016-02-06T00:25:49Z")

</div>

Carlos

thank you

for your prompt response

Regards
