Glad to hear! :)On Mon, 12 Nov 2012 10:40:06 +0100, Anouar Znagui Hassani wrote:
Thank you Hector.
Frankly I forgot to forward that port 29867 to the server.
Once I did that. It worked without any problem.
-- Hector Sanjuan@hecsanjuan_
Thank you Hector.
Frankly I forgot to forward that port 29867 to the server.
Once I did that. It worked without any problem.
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
what's between your browser and the proxy? If the connection cannot reach the proxy, it might be a firewall problem...port 29876 should be accesible from wherever you are connecting.HectorOn Mon, 12 Nov 2012 00:25:22 +0100, Anouar Znagui Hassani wrote:
"Try launching Sunstone, killing th
"Try launching Sunstone, killing the websockify proxy and relaunching the
proxy manually in a console window with the command that is logged at the
beginning of sunstone.log. Leave it running and click on the VNC icon on
Sunstone for the same VM again. You should see some output from the proxy
in
ok, whats the output of the console when you do the
"Try launching Sunstone, killing the websockify proxy and relaunching the
proxy manually in a console window with the command that is logged at the
beginning of sunstone.log. Leave it running and click on the VNC icon on
Sunstone for the s
Hi Hector,
Thank you for your help.
I have read the checklist for troubleshooting but no luck there.
The popup shows now but only with the "connect timeout"
in oned.conf:
VNC_BASE_PORT = 5900
in occi-server.conf:
:host: 0.0.0.0
:port: 4567
:vnc_enable: no
:vnc_proxy_port: 33876
:vnc_proxy_p
Hello,configuration changes are detailed in the compatibility guides of each version. i.e.:http://opennebula.org/documentation:archives:rel3.4:compatibility#cloud_serverswarns about the new variables for sunstone and selfservice etc.Regarding your problem, please do the checklist at:http://openneb
Hello Hector,
During the upgrade from 3.2 to 3.8 the conf files were not updated. Now
they did exactly just like you said.
Thank you!
But now I see the popup with " noVNC ready: native WebSockets, canvas
rendering " and 2 seconds later...:
"Connect timeout"
What does this mean. I feel like
Hello,
the name of some config options have changed since 3.2. The install script
will not replace the value if it is not in the file.
Apart from that
:vnc_proxy_base_port: 0
:vnc_proxy_support_wss: yes (without providing path to the certs)
does not make much sense.
For the VNC configurat
Hello Guys,
After wasting many hours of research I would like to ask a question
regarding the installation and usage of noVNC webproxy in order to open
a graphical window to my running VM.
When I start my VM I get the status "RUNNING" so that is good. When I
click the noVNC icon I get the mess
10 matches
Mail list logo
