# 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:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![jourdain](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jourdain/32/11_2.png) [@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")

</div>

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

---

_[View the full topic](https://discourse.paraview.org/t/enabling-wss-for-paraview-visualiser/15692)._