Hi,
We needed to change:
“configuration”:
“host”: “localhost”
by:
“configuration”:
“host”: “${Paraview_IP}”
In the launcher configuration file in order to get it working. It would be
neccesary to correct it in updated documentation?
Regards,
Gabriel.
De: Sebastien Jourdain [mailto:[email protected]]
Enviado el: lunes, 14 de marzo de 2016 18:08
Para: Gabriel Álvarez Castro
CC: [email protected]
Asunto: Re: [Paraview] WebSocket connection failed: Error during WebSocket
handshake: Unexpected response code: 404
Thanks for your feedback and I'm glad that's working as expected now.
The updated version of that documentation is now available here:
http://kitware.github.io/paraviewweb/docs/guides/launching_examples.html
On Mon, Mar 14, 2016 at 9:39 AM, Gabriel Álvarez Castro
<[email protected]> wrote:
Hi,
It’s working now! Thank you very much. I tryed to configure it
as explained in http://paraviewweb.kitware.com/#!/guide/launching_examples “two
machines”, but I understood “sessionURL” referred to the “launcher machine".
Perhaps, it is not enough explained in the guide...
Thanks a lot. Regards,
Gabriel.
De: Sebastien Jourdain [mailto:[email protected]]
Enviado el: lunes, 14 de marzo de 2016 15:28
Para: Gabriel Álvarez Castro
CC: [email protected]
Asunto: Re: [Paraview] WebSocket connection failed: Error during WebSocket
handshake: Unexpected response code: 404
Your launcher config should be as follow:
"sessionURL": "ws://${ApacheHost_or_IP}:8088/proxy?sessionId=${id}",
Assuming that /var/visor/mapping/proxy.txt is the same file (network shared)
with /mnt/nfs/mapping/proxy.txt.
Seb
On Mon, Mar 14, 2016 at 2:57 AM, Gabriel Álvarez Castro
<[email protected]> wrote:
Hi,
No problem. I am attaching my Apache and launcher
configurations… The VirtualHost is defined in front-end machine, and launcher
configuration file of the second machine.
Regards,
Gabriel.
De: Sebastien Jourdain [mailto:[email protected]]
Enviado el: viernes, 11 de marzo de 2016 16:03
Para: Gabriel Álvarez Castro
CC: [email protected]
Asunto: Re: [Paraview] WebSocket connection failed: Error during WebSocket
handshake: Unexpected response code: 404
Hi Gabriel,
do you mind sharing (privately if you prefer) your apache config as well as
your launcher config?
Thanks,
Seb
On Fri, Mar 11, 2016 at 4:12 AM, Gabriel Álvarez Castro
<[email protected]> wrote:
Hi:
We've installed ParaviewWeb 5.0 in a configuration of two machines: Apache on
one machine (Ubuntu 14.04), and the launcher and the ParaViewWeb processes on a
second machine (Ubuntu 15.10). We've the problem that when trying to access the
Visualizer ('Post-processing' link at index.html) the '.../apps/Visualizer' tab
opens but we receive the error 'WebSocket connection failed: Error during
WebSocket handshake: Unexpected response code: 404'. We've tested before the
same ParaviewWeb only in one machine (Ubuntu 15.10) and it worked fine. Could
someone help us please?
Regards:
Gabriel.
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
