# How to deploy a secure (\`wss\`) websocket server?

**URL:** <https://discourse.julialang.org/t/how-to-deploy-a-secure-wss-websocket-server/32583>\
**Category:** Web Stack\
**Created:** [December 22, 2019, 5:50pm UTC](https://discourse.julialang.org/t/how-to-deploy-a-secure-wss-websocket-server/32583 "2019-12-22T17:50:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![1115](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/1115/32/4465_2.png) [@1115](https://discourse.julialang.org/u/1115)\
**Post date:** [December 22, 2019, 5:50pm UTC](https://discourse.julialang.org/t/how-to-deploy-a-secure-wss-websocket-server/32583/1 "2019-12-22T17:50:31Z")

</div>

Hi, I am following this example to setup a websocket service,  
[https://github.com/JuliaWeb/WebSockets.jl/blob/master/examples/minimal\_server.jl](https://github.com/JuliaWeb/WebSockets.jl/blob/master/examples/minimal_server.jl)  
This example shows how to handle a URI request like `ws://...`.

However, in a `https` website, using `ws` protocal for websocket is considered as “unsecure”  
[https://stackoverflow.com/questions/26791107/wss-on-http-vs-wss-on-https](https://stackoverflow.com/questions/26791107/wss-on-http-vs-wss-on-https)

Is there any example to setup a server that accepts `wss` URI?

---

<div class="post-metadata">

**Author:** ![travigd](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/travigd/32/4746_2.png) [@travigd](https://discourse.julialang.org/u/travigd)\
**Post date:** [December 28, 2019, 11:23pm UTC](https://discourse.julialang.org/t/how-to-deploy-a-secure-wss-websocket-server/32583/2 "2019-12-28T23:23:10Z")

</div>

For posterity, I briefly answered on Slack.

> If you’re doing this in a production type environment the easiest thing might be to put a reverse proxy that does SSL termination in front of the WebSocket server

> So you’d have an NGINX process that has SSL termination setup and it would forward things to your WebSocket server which is listening on “vanilla” HTTP.