WSS Unexpected response code: 400 about paraviewweb

[jourdain]

What your apache virtual host config looks like?

It should redirect to ws:// not wss://

[0x3bfc]

Yes, I did that
Kindly check out my Apache virtual host config and launcher.config

[0x3bfc]

Also this is a sample of python process log

2016-05-26 08:43:23+0000 [-] Log opened.
2016-05-26 08:43:23+0000 [-] ReapingWampServerFactory starting on 9005
2016-05-26 08:43:23+0000 [-] Starting factory <vtk.web.wamp.ReapingWampServerFactory instance at 0x000000000BA25448>
2016-05-26 08:43:23+0000 [-] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2016-05-26 08:43:23+0000 [-] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

And what I get now is this error:

WebSocket connection to 'wss://MY-APACHE-SERVER:9005/proxy?sessionId=e656549e-231d-11e6-af8d-000d3a10ab7a' failed: Error in connection establishment: net::ERR_CONNECTION_RESET

I'm trying to check out firewall settings and apache proxy configurations.

[0x3bfc]

Also I have a question ....... does self-signed certificate make a connection reset error ??

[jourdain]

Try updating your launcher configuration.

"sessionURL" : "wss://portal.tessra.com/proxy?sessionId=${id}",

"resources" : [ { "host" : "localhost", "port_range" : [9001, 9005] } ],

[0x3bfc]

thanks for your help ... but this raises the first error ...

failed: Error during WebSocket handshake: Unexpected response code: 400

[jourdain]

Well I missed that other issue:

"proxy_file" : "/../proxy.txt",

Should match the file path

C:\Program Files (x86)\pythonLauncher\mapping\proxy.txt

Did you read the documentation?
http://kitware.github.io/paraviewweb/docs/guides/apache_front_end.html
http://kitware.github.io/paraviewweb/docs/guides/python_launcher.html

[0x3bfc]

The issue was the proxy file .... as you mentioned above.. It is working now ... I'm really appreciate your cooperation ...
thanks seb!
👍

[jourdain]

Glad to hear you got it working.

[0x3bfc]

there is another issue .... when starting new session on incognito tab I get the following error

failed: Error during WebSocket handshake: Unexpected response code: 502

It is working only for one session not multi-user scenario!

[jourdain]

http://www.checkupdown.com/status/E502.html

[jourdain]

Did you try from different browser, not browser tab?

[0x3bfc]

Yep, I tried firefox and chrome

[jourdain]

So what was working before?

On Thu, May 26, 2016 at 9:26 AM, Ahmed Abdullah [email protected]
wrote:

Yep, I tried firefox and chrome

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#117 (comment)

[0x3bfc]

the viewer is working only when starting first session ..not sure if it is due to ${host}:${port} or 443 in session url .... then If I try to open the same file I get the error as shown above.

[jourdain]

What? ${host}:${port} This should be gone based on what I asked you to fix.

[0x3bfc]

Yep, I did what you wrote ....

[jourdain]

I think you need to take a minute and look at the documentation and try to understand how things work.
Then you might be able to figure out by yourself what is the piece you missed.

[0x3bfc]

Thanks Seb ... actually I read the documentation multiple times .... but I don't find clear documentation for Parview web - HTTPS setup especially the launcher.config .... do you have a link for it "I mean the launcher.config for wss"

[jourdain]

Did you make it work before switching to wss?

[0x3bfc]

Yes, it was working before wss

[jourdain]

Well not really, you were using direct connection without going through Apache.

[0x3bfc]

I followed the apache configuration in paraview documentation for ws !

[jourdain]

Yes but didn't use the proper configuration for the launcher, which was making the client not going through Apache.

[0x3bfc]

Aha, I got you! ....anyway, I'll read it again ... thanks for your support