# enabling wss for paraview visualiser
**URL:** https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692
**Category:** Web Support
**Created:** [November 6, 2024, 5:05am UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692 "2024-11-06T05:05:17Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@roka2024](https://discourse.paraview.org/u/roka2024)
#### Post date: [November 6, 2024, 5:05am UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/1 "2024-11-06T05:05:17Z")
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 via ngrok?
I’m running paraview version 5.11.2 on Rocky linux:
pvpython -m paraview.apps.visualizer --mesa --port 11111 --data /tmp/pvvisualizer/ --host 0.0.0.0 --timeout 0 --debug
Thanks,
Robert
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [November 6, 2024, 3:30pm UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/2 "2024-11-06T15:30:46Z")
You have some `--ssl` args available so you can provide a certificate for your hostname. Just use `--help` to list those parameters.
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [November 6, 2024, 3:32pm UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/3 "2024-11-06T15:32:51Z")
Although, since you are running with ParaView, SSL is not available within pvpython due to security reason. So you will need to use a reverse proxy where you run your visualizer to serve its content over https/wss. Something like Apache, NGINX, traefik…
---
### Author:  [@roka2024](https://discourse.paraview.org/u/roka2024)
#### Post date: [November 6, 2024, 3:58pm UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/4 "2024-11-06T15:58:37Z")
Hi Sebastien,
Thank you for the quick reply!
Very much appreciated.
Yea, I tried to reverse proxy it with nginx, apache, and a custom one without success.
One issue is that visualizer doesn’t seem to accept POST requests that show up when running https and I don’t understand enough of the underlying technology. I just wanna use paraview over the web in a secure way 🙂
I have tried to rewrite it to GET without success.
The main issue is that it’s an https connection from the browser through the ngrok tunnel but then visualizer establishes a non secure web socket somehow which is not allowed.
The easiest would be that visualizer uses wss I think.
Thanks for any guidance.
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [November 6, 2024, 7:18pm UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/5 "2024-11-06T19:18:30Z")
ParaView Web and trame application usually only serve static content and everything else go through websocket. (The post request can be ignored as it is for session launching when a launcher is available)
Since Visualizer is old, the auto detection of protocol has a bug that was fixed maybe a year or so ago for trame. Because of that bug, you will need to manually provide the ws path in the url.
So for example if you were reaching the application with the following url `https://my.domain.com/visualizer/` you should add a query to specify the ws connection.
```auto
https://my.domain.com/visualizer/?sessionURL=wss://my.domain.com/visualizer/ws
```
HTH,
Seb
---
### Author:  [@roka2024](https://discourse.paraview.org/u/roka2024)
#### Post date: [November 6, 2024, 10:00pm UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/6 "2024-11-06T22:00:48Z")
OMG, it helped to make my thing going 🙂
Thank you so much for your quick help!
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [November 6, 2024, 10:17pm UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/7 "2024-11-06T22:17:48Z")
Glad it worked…
This is the [bug](https://github.com/Kitware/wslink/releases/tag/v1.6.5) I was talking about (Fixed on June 2022).
If you patch the JS file in visualizer, you should be able to skip the query param.
---
### Author:  [@roka2024](https://discourse.paraview.org/u/roka2024)
#### Post date: [November 6, 2024, 10:29pm UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/8 "2024-11-06T22:29:34Z")
Oh I see. I understand now.
I installed paraview with dnf. Seems the bug fix didn’t make it to the repo.
What’s the release policy there?
Do you have suggestions how to update the dnf installation?
Or in general how to install paraview and visualizer on (Rocky) Linux?
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [November 8, 2024, 1:10am UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/9 "2024-11-08T01:10:15Z")
Visualizer hasn’t been updated in 6 years and has been removed in 5.13.
---
### Author:  [@roka2024](https://discourse.paraview.org/u/roka2024)
#### Post date: [November 8, 2024, 1:28am UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/10 "2024-11-08T01:28:16Z")
So what’s the suggested alternative that provides the same functionality and similar maturity?
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [November 8, 2024, 9:46pm UTC](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692/11 "2024-11-08T21:46:06Z")
You can keep using it if that correspond to your needs (and even modify/patch it). If not, building an application with trame give you a lot more flexibility, but that is just a framework not an app.
> **[trame | trame](https://kitware.github.io/trame/)**
>
> Trame lets you weave various components and technologies into a Web Application solely written in Python