[Paraview] ParaviewWeb on EC2

[claude]

Hello!

Following up one of the previous thread on setting up
ParaviewWeb+Visualizer, I am trying to get it going on AWS EC2 with
paraview-5.2. Maybe someone already went through it and know how to
solve this little problem?

* I launched the public AMI (ami-34f3f65e) on Ubuntu-14 with paraviewweb
4.4 which seemed like a good starting point.
* I tested the visualizer on paraviewweb-4.4 and works perfectly.
* I downloaded paraviewweb-5.2 and updated the 'pv' and 'www' symlinks
under /data folder (see 'aws_data_dir' snapshot attached).
* I also updated the paths in the start.sh, apache-TEMPLATE.conf and
launcher-TEMPLATE.json files so that they reflect the correct path for
paraview-5.2 (which are bit different than paraview-4.4). By the way,
having start.sh running as a service at startup configuring properly the
TEMPLATE files with the proper DNS name is admirable (each time I look
at the doc, config files or code, I am amazed by the quality of it,
thumb up!).
* when I navigate to the EC2 DNS, the Visualizer comes up and I can
browse for data files. The files seem to successfully load but nothing
show up in the camera (see snapshot 'aws_ec2_visu'). Looking at the logs
on the machine, they don't report any error (and look similar to what I
can get locally on my machine). There is a couple of errors showing up
in the web console though (in the snapshot attached).

It looks like I am very close to make it work, I am probably missing
something obvious.
I tried the following to solve it by using my configuration on my local
machine:
1. update the apache-TEMPLATE.conf with the following rules:
RewriteCond %{QUERY_STRING} ^sessionId=(.*)&path=(.*)$ [NC]
RewriteRule ^/proxy.*$ ws://${session-to-port:%1}/%2 [P]

2. update the launcher-TEMPLATE.json with the following line:
"sessionURL" : "ws://DNS_NAME/proxy?sessionId=${id}&path=ws",

3. reboot (so that the files get updated)

but this time the UI doesn't even load, meaning I made it worse.

It seems just like a websocket connection issue, right?

Thanks in advance for any ideas to try.
cheers
claude
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aws_ec2_visu.png
Type: image/png
Size: 121230 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170119/2dbc5d11/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aws_data_dir.png
Type: image/png
Size: 86103 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170119/2dbc5d11/attachment-0001.png>