Hi @sophwats et al,
We are using this container
We connect to the visualizer with https but the container uses unsecured websockets by default instead of wss.
How can wss be enabled?
There used to be a bug in paraview where a colon is missing. I’m not sure if your container contains that fix?
committed 02:02AM - 03 Jun 22 UTC
The value of window.location.protocol ends with ':'.
Hi, I’m accessing paraview visualizer via ngrok using https. I have to allow mixed content in Chrome bc visualizer uses apparently ws:/ and not wss:/ Is there a way to enable wss for visualizer? Or what’s your recommendation to run visualizer...
Reading time: 1 mins 🕑
Likes: 1 ❤
Thanks,
Robert
1 Like
Hi @robert.karban ,
I’ve reached out to the ParaView Team to get some help here.
Thanks for your patience,
Sophie
Thank you.
I figured out that your container doesn’t include the patch for wss but it can be worked around by using
https:///index.html?sessionURL=wss:///ws
Thanks,
Robert
Thanks for sharing the fix and letting us know that you were able to resolve the issue.
Have a great day,
Sophie
Hi @sophwats .
It’s a workaround though.
The container should be updated to include the fix from here:
committed 02:02AM - 03 Jun 22 UTC
The value of window.location.protocol ends with ':'.
Thanks,
Robert
system
Closed
August 7, 2025, 6:43pm
6
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.