<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">I changed sessionManagerURL in my html
file to vtkWeb.properties.sessionManagerURL instead of
<a class="moz-txt-link-freetext" href="http://localhost:8080/paraview">http://localhost:8080/paraview</a>. Now I get in firefox:<br>
<br>
Use of getPreventDefault() is deprecated. Use defaultPrevented
instead. jquery-1.8.3.min.js:2:0<br>
GET <br>
<a class="moz-txt-link-freetext" href="http://localhost/proxy">http://localhost/proxy</a> [HTTP/1.1 400 Bad Request 16ms]<br>
null Visualizer:42:13<br>
Firefox can't establish a connection to the server at
<a class="moz-txt-link-freetext" href="ws://localhost/proxy?sessionId=7d12745c-6a34-11e6-a5dc-0016d4e2bc28">ws://localhost/proxy?sessionId=7d12745c-6a34-11e6-a5dc-0016d4e2bc28</a>.
autobahn.min.js:114:0<br>
GET <br>
<a class="moz-txt-link-freetext" href="http://localhost/proxy">http://localhost/proxy</a> [HTTP/1.1 400 Bad Request 2ms]<br>
null<br>
<br>
...I think one more thing is needed.<br>
<br>
<br>
Am 24.08.2016 um 21:51 schrieb Daniel Zuidinga:<br>
</div>
<blockquote
cite="mid:c172980e-6f63-d4c2-bdeb-dc7bd8380643@seoaachen.de"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
I had wrong paths in my launcher.config properties.<br>
Now the request gets through and the vtk window opens. But I have
still the ws error. Firefox console:<br>
<br>
Firefox can't establish a connection to the server at <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="ws://localhost/ws">ws://localhost/ws</a>.
autobahn.min.js:114:0<br>
null Visualizer:42:13<br>
Use of getPreventDefault() is deprecated. Use defaultPrevented
instead. jquery-1.8.3.min.js:2:0<br>
No launcher found. Attempting to connect using the direct WS url.
vtkweb-all.js:4456:19<br>
<br>
--- vtk window opens, then:<br>
<br>
Cross-Origin Request Blocked: The Same Origin Policy disallows
reading the remote resource at <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://localhost:8080/paraview">http://localhost:8080/paraview</a>.
(Reason: CORS header 'Access-Control-Allow-Origin' missing).
<unknown><br>
GET <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://localhost/ws">http://localhost/ws</a> [HTTP/1.1 404
Not Found 2ms]<br>
null Visualizer:42:13<br>
Firefox can't establish a connection to the server at <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="ws://localhost/ws">ws://localhost/ws</a>.<br>
<br>
<br>
<div class="moz-cite-prefix">Am 24.08.2016 um 19:18 schrieb
Sebastien Jourdain:<br>
</div>
<blockquote
cite="mid:CABObKxc1zUVvQRdTbrX-8GZJbGWqD8tLyTR_3bVTc2dnzPuKfA@mail.gmail.com"
type="cite">
<div dir="ltr">Actually the hostname might be an issue if you
have several network card.
<div>Can you try to use the computer IP? Or '0.0.0.0' for the
launcher if that work?</div>
<div><br>
</div>
<div>Otherwise I did not spotted any issue in your config.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Aug 24, 2016 at 11:14 AM,
Daniel Zuidinga <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:info@seoaachen.de"
target="_blank">info@seoaachen.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> - apache 2.4.12<br>
- modules are enabled<br>
- launcher.py launches without error, resrouces and apps
section are in the config file as described in the
documentation<br>
are all ports and hostnames right in my configuration
files? apache is localhost and paraview also
<div>
<div class="h5"><br>
<br>
Am 24.08.2016 um 16:22 schrieb Sebastien Jourdain:<br>
<blockquote type="cite">
<div dir="ltr">Hi Daniel,
<div><br>
</div>
<div>Which version of Apache are you running?</div>
<div><br>
</div>
<div>Did you enabled all the modules?</div>
<div><br>
</div>
<div>
<pre style="margin-top:0px;margin-bottom:0px;padding:0px;border:none;outline:0px;font-family:"Source Code Pro",Monaco,Menlo,Consolas,monospace;font-size:0.95em;vertical-align:baseline;color:rgb(77,77,76);line-height:22px;background:none rgb(238,238,238)"><div style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;font-family:inherit;font-size:14.25px;vertical-align:baseline;min-height:22px">$ sudo a2enmod vhost_alias</div><div style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;font-family:inherit;font-size:14.25px;vertical-align:baseline;min-height:22px">$ sudo a2enmod proxy</div><div style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;font-family:inherit;font-size:14.25px;vertical-align:baseline;min-height:22px">$ sudo a2enmod proxy_http</div><div style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;font-family:inherit;font-size:14.25px;vertical-align:baseline;min-height:22px">$ sudo a2enmod proxy_wstunnel</div><div style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;font-family:inherit;font-size:14.25px;vertical-align:baseline;min-height:22px">$ sudo a2enmod rewrite</div></pre>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">For the launcher
configuration, do you have a proper <span style="color:rgb(77,77,76);font-family:"Source Code Pro",Monaco,Menlo,Consolas,monospace;font-size:14.25px;line-height:22px;white-space:pre-wrap;background-color:rgb(238,238,238)">"resources"</span> and <span style="color:rgb(77,77,76);font-family:"Source Code Pro",Monaco,Menlo,Consolas,monospace;font-size:14.25px;line-height:22px;white-space:pre-wrap;background-color:rgb(238,238,238)">"apps"</span> <wbr>section?</div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">I'm guessing you are
looking at the following documentation
pages?</div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">- <a
moz-do-not-send="true"
href="https://kitware.github.io/paraviewweb/docs/guides/apache_front_end.html"
target="_blank">https://kitware.github.io/<wbr>paraviewweb/docs/guides/<wbr>apache_front_end.html</a><br>
</div>
<div class="gmail_quote">- <a
moz-do-not-send="true"
href="https://kitware.github.io/paraviewweb/docs/guides/python_launcher.html"
target="_blank">https://kitware.github.io/<wbr>paraviewweb/docs/guides/<wbr>python_launcher.html</a><br>
</div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">Once you have the
forwarding of the launcher request working,
the next part will be the forwarding of the
ws. But we can talk about it when and if you
run into issue about it.</div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">Seb</div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">On Wed, Aug 24, 2016
at 2:22 AM, Daniel Zuidinga <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:info@seoaachen.de"
target="_blank">info@seoaachen.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>I tried to run the launcher as
described in the docs. But I am still
getting errors when running <a
moz-do-not-send="true"
href="http://localhost/apps/Visualizer/"
target="_blank">http://localhost/apps/Visualiz<wbr>er/</a></p>
<p>Firefox console:</p>
<p>------------------------------<wbr>-<br>
</p>
<p>1. when setting sessionManagerURL in
html set to
vtkWeb.properties.sessionManag<wbr>erURL:</p>
<p>POST <br>
XHR <br>
<a moz-do-not-send="true"
href="http://localhost/paraview/"
target="_blank">http://localhost/paraview/</a>
[HTTP/1.1 503 Service Unavailable
48ms]<br>
Object { error: "The process did not
properly start.…" } Visualizer:42:13</p>
<p><br>
</p>
<p>2. when setting sessionManagerURL in
html to <a moz-do-not-send="true"
href="http://localhost:8080/paraview"
target="_blank">http://localhost:8080/paraview</a><wbr>:</p>
<p>Firefox can't establish a connection
to the server at <a
moz-do-not-send="true">ws://localhost/ws</a>.
autobahn.min.js:114:0<br>
null Visualizer:42:13<br>
No launcher found. Attempting to
connect using the direct WS url.
vtkweb-all.js:4456:19<br>
Use of getPreventDefault() is
deprecated. Use defaultPrevented
instead. jquery-1.8.3.min.js:2:0<br>
Cross-Origin Request Blocked: The Same
Origin Policy disallows reading the
remote resource at <a
moz-do-not-send="true"
href="http://localhost:8080/paraview"
target="_blank">http://localhost:8080/paraview</a><wbr>.
(Reason: CORS header
'Access-Control-Allow-Origin'
missing). <unknown><br>
GET <br>
<a moz-do-not-send="true"
href="http://localhost/ws"
target="_blank">http://localhost/ws</a>
[HTTP/1.1 404 Not Found 12ms]<br>
null</p>
<p><br>
</p>
<p>So the launcher can't start the pv
webserver? But running <a
moz-do-not-send="true"
href="http://localhost:8080/paraview/1"
target="_blank">http://localhost:8080/paraview<wbr>/1</a>
in browser works but says: {"error":
"No session with id: 1"}<br>
</p>
<p><br>
</p>
<p>My apache config:</p>
<p>-----------------------------<br>
</p>
<p><VirtualHost *:80><br>
ServerName localhost<br>
ServerAdmin <a
moz-do-not-send="true"
href="mailto:info@seoaachen.de"
target="_blank">info@seoaachen.de</a><br>
DocumentRoot
/home/daniel/salome_meca/V2016<wbr>/prerequisites/Paraview-v501_<wbr>EDF/share/paraview-5.0/www<br>
ErrorLog "logs/pv-error_log"<br>
CustomLog "logs/pv-access_log"
common<br>
### The following commented lines
could be useful when running<br>
### over https and wss:<br>
# SSLEngine On<br>
# SSLCertificateFile
/etc/apache2/ssl/your_certific<wbr>ate.crt<br>
# SSLCertificateKeyFile
/etc/apache2/ssl/your_domain_k<wbr>ey.key<br>
# SSLCertificateChainFile
/etc/apache2/ssl/DigiCertCA.cr<wbr>t<br>
#<br>
# <Location ${MY-DOCUMENT-ROOT}
><br>
# SSLRequireSSL On<br>
# SSLVerifyClient optional<br>
# SSLVerifyDepth 1<br>
# SSLOptions +StdEnvVars
+StrictRequire<br>
# </Location><br>
# Have Apache pass these requests
to the launcher :9000<br>
ProxyPass /paraview <a
moz-do-not-send="true"
href="http://localhost:8080/paraview"
target="_blank">http://localhost:8080/paraview</a><br>
# Turn on the rewrite engine<br>
RewriteEngine On<br>
# This is the path the mapping
file Jetty creates<br>
RewriteMap session-to-port
txt:/home/daniel/proxy.txt<br>
# This is the rewrite condition.
Look for anything with a sessionId= in
the query part of the URL and capture
the value to use below.<br>
RewriteCond %{QUERY_STRING}
^sessionId=(.*)$ [NC]<br>
# This does the rewrite using the
mapping file and the sessionId<br>
RewriteRule ^/proxy.*$ <a
moz-do-not-send="true">ws://$</a>{session-to-port:%1}/ws
[P]<br>
<Directory
"/home/daniel/salome_meca/V201<wbr>6/prerequisites/Paraview-v501_<wbr>EDF/share/paraview-5.0/www"><br>
Options Indexes FollowSymLinks<br>
Order allow,deny<br>
Allow from all<br>
AllowOverride None<br>
Require all granted<br>
</Directory><br>
</VirtualHost></p>
<p><br>
</p>
<p><br>
</p>
<p>my launcher.json</p>
<p>----------------------------<br>
</p>
<p> "configuration": {<br>
"host" : "localhost",<br>
<br>
"port" : 8080,<br>
"endpoint":
"paraview", <br>
"content":
"/.../www", <br>
"proxy_file" :
"/home/daniel/proxy.txt", <br>
"sessionURL": <a
moz-do-not-send="true">"ws://localhost/proxy?sessionI<wbr>d=${id}"</a>,<br>
<br>
"timeout" :
25, <br>
"log_dir" :
"/home/daniel", <br>
"upload_dir" :
"/home/daniel", <br>
"fields" : ["file",
"host", "port", "updir"] <br>
},<br>
</p>
<p><br>
</p>
<p>What am I doing wrong?</p>
<span>
<p><br>
</p>
<pre cols="72">Daniel Zuidinga
Dipl.-Ing.
SEO Aachen
Passstr. 5
52070 Aachen
Tel : 0241 / 450 912 67
E-Mail: <a moz-do-not-send="true" href="mailto:info@seoaachen.de" target="_blank">info@seoaachen.de</a>
Web : <a moz-do-not-send="true" href="http://www.seoaachen.de" target="_blank">http://www.seoaachen.de</a> (nur zum Teil aktuell)
Xing : <a moz-do-not-send="true" href="https://www.xing.com/profile/Daniel_Zuidinga" target="_blank">https://www.xing.com/profile/D<wbr>aniel_Zuidinga</a>
Bald online: Software Tools für Konstrukteure und Bauteilhersteller
<a moz-do-not-send="true" href="http://www.engineeringonline.de" target="_blank">http://www.engineeringonline.d<wbr>e</a></pre>
</span><div><div><div>Am 22.08.2016 um 22:32 schrieb
Sebastien Jourdain:
</div>
<blockquote type="cite">
<div dir="ltr">Hi Daniel,
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I
want to use paraview web with SSL. As far as I understand
I need apache as a proxy server for that? Or is it
possible with pvpython?
</blockquote>
<div>
</div>
<div>It might be possible with pvpython, but I've never done
it, I've always used apache to rely on a single opened
port and handle the encryption. </div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I
have my own launcher which opens pvpython with a different
port for each user. Is this the right way? Will this work
with ssl?
</blockquote>
<div>
</div>
<div>If pvpython directly support the wss connection, you
can be good. Usually the setup, that I do is that I have
Apache serving only the port 443 (https) for both the
static content and the (wss) websocket endpoint. And I use
a mapping file between the Websocket endpoint that get
returned by my launcher and the host/port I should connect
to on the backend to establish the link between the client
and the actual ParaViewWeb server instance.</div>
<div>
</div>
<div>But that does not mean, that's the only way to do it
and if you don't mind having several port open, I don't
see why it could not work.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Concerning:
<a moz-do-not-send="true" href="https://kitware.github.io/visualizer/docs/" rel="noreferrer" target="_blank">https://kitware.github.io/visu<wbr>alizer/docs/</a>
The web visuailzer should work via npm installation? It
does not work for me:
C:\Users\danie\AppData\Roaming<wbr>\npm\node_modules\pvw-visualiz<wbr>er\bin\pvw-visualizer-cli.js:4<wbr>1
var pvPythonExecs = find(paraview).filter(function<wbr>(file)
{ return file.match(/pvpython$/) ||
file.match(/pvpython.exe$/); });
^
TypeError: find(...).filter is not a function
at Object.<anonymous>
(C:\Users\danie\AppData\Roamin<wbr>g\npm\node_modules\pvw-visuali<wbr>zer\bin\pvw-visualizer-cli.js:<wbr>41:36)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:139:18)
at node.js:968:3
</blockquote>
<div>
</div>
<div>Well, I guess I haven't tried to run the new Visualizer
server on a Windows machine. </div>
<div>But with ParaView 5.2 (yet to be released), we should
have a ParaViewWeb back in the binaries. So we should make
sure our Visualizer command line tool work on that
platform as well.</div>
<div>Although, the command line is more for beginners than
anything else as it only simplify the demo usage. In real
word deployment, with a launcher, the true pvpython
command line should be used instead.</div>
<div>
</div>
<div>Here is an example of what you should see in a working
environment:</div>
<div>
</div>
<div>
<div>$ Visualizer -d ~/Downloads/</div>
<div>
</div>
<div>==============================<wbr>==============================<wbr>===================</div>
<div>| Execute:</div>
<div>| $ /Applications/paraview.app/Con<wbr>tents/bin/pvpython</div>
<div>| -dr</div>
<div>|
/Users/seb/Documents/code/Web2<wbr>/visualizer/server/pvw-visuali<wbr>zer.py</div>
<div>| --content</div>
<div>| /Users/seb/Documents/code/Web2<wbr>/visualizer/dist</div>
<div>| --port</div>
<div>| 8080</div>
<div>| --data</div>
<div>| /Users/seb/Downloads/</div>
<div>==============================<wbr>==============================<wbr>===================</div>
<div>
</div>
<div>[...]</div>
<div>
</div>
--
Daniel Zuidinga
Dipl.-Ing.
SEO Aachen
Passstr. 5
52070 Aachen
Tel : 0241 / 450 912 67
E-Mail: <a moz-do-not-send="true" href="mailto:info@seoaachen.de" target="_blank">info@seoaachen.de</a>
Web : <a moz-do-not-send="true" href="http://www.seoaachen.de" rel="noreferrer" target="_blank">http://www.seoaachen.de</a> (nur zum
Teil aktuell)
Xing : <a moz-do-not-send="true" href="https://www.xing.com/profile/Daniel_Zuidinga" rel="noreferrer" target="_blank">https://www.xing.com/profile/D<wbr>aniel_Zuidinga</a>
Bald online: Software Tools für Konstrukteure und
Bauteilhersteller
<a moz-do-not-send="true" href="http://www.engineeringonline.de" rel="noreferrer" target="_blank">http://www.engineeringonline.d<wbr>e</a>
______________________________<wbr>_________________
Powered by <a moz-do-not-send="true" href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a>
Visit other Kitware open-source projects at <a moz-do-not-send="true" href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensou<wbr>rce/opensource.html</a>
Please keep messages on-topic and check the ParaView Wiki
at: <a moz-do-not-send="true" href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/ParaV<wbr>iew</a>
Search the list archives at: <a moz-do-not-send="true" href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>ParaView</a>
Follow this link to subscribe/unsubscribe:
<a moz-do-not-send="true" href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/paraview</a>
</div>
</div>
</div>
</div>
</blockquote>
</div></div></div>
</blockquote></div>
</div></div>
</blockquote>
</div></div></div></blockquote></div>
</div>
</blockquote>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre wrap="">_______________________________________________
Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Please keep messages on-topic and check the ParaView Wiki at: <a class="moz-txt-link-freetext" href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a>
Search the list archives at: <a class="moz-txt-link-freetext" href="http://markmail.org/search/?q=ParaView">http://markmail.org/search/?q=ParaView</a>
Follow this link to subscribe/unsubscribe:
<a class="moz-txt-link-freetext" href="http://public.kitware.com/mailman/listinfo/paraview">http://public.kitware.com/mailman/listinfo/paraview</a>
</pre>
</blockquote><p>
</p></body></html>