Hi Chris,
Sunstone will try to connect to port 35777 which is vnc_proxy_base port +
the vnc port of the VM. This is where websockify is running. Then it will
open a connection to cloud:5901.
So, in theory, your fw rule should be affecting a range in the ~35770s
If the problem persists, run websockify manually and send the output when
you try to open the vnc from sunstone.
Regards,
Hector
En Fri, 31 Aug 2012 08:26:28 +0200, Chris Mutchler
<[email protected]> escribió:
I have my first VM in OpenNebula provisioned and in the running state.
Now
when I go to connect to it over noVNC through the browser, I get a
timeout
error. Nothing appears in /var/log/one/sunstone.error log file unless I
manually start the proxy via shell.
Here are the only entries that appear in the /var/log/one/sunstone.log
file
when I initiate the noVNC session:
Fri Aug 31 00:18:41 2012 [I]: Starting vnc proxy:
/usr/share/one/noVNC/utils/websockify 35777 cloud:5901
Fri Aug 31 00:18:41 2012 [I]: 192.168.1.5 - - [31/Aug/2012 00:18:41]
"POST
/vm/1/startvnc HTTP/1.1" 200 30 0.0274
Fri Aug 31 00:18:49 2012 [I]: 192.168.1.5 - - [31/Aug/2012 00:18:49]
"POST
/vm/1/stopvnc HTTP/1.1" 200 - 0.0618
I've added a firewall rule to the host + front-end machine (they exist
together) for the port range of 5900 - 5999.
1 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state
NEW
tcp dpts:5900:5999
I've also gone through the suggestions on the page for troubleshooting
noVNC. The only thing I can think of is that I am not using a SSL/TLS
certficate. How do I set that up and could that be causing my timeout
message I get in the noVNC window?
Thank you.
--
Hector Sanjuan
OpenNebula Developer
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
