# \[SOLVED\] Websocket setup on Synology

**URL:** <https://vaultwarden.discourse.group/t/solved-websocket-setup-on-synology/116>\
**Category:** Third Party Help\
**Created:** [May 22, 2020, 9:12am UTC](https://vaultwarden.discourse.group/t/solved-websocket-setup-on-synology/116 "2020-05-22T09:12:29Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![MilesTEG1](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/milesteg1/32/288_2.png) [@MilesTEG1](https://vaultwarden.discourse.group/u/MilesTEG1)\
**Post date:** [April 11, 2021, 5:39am UTC](https://vaultwarden.discourse.group/t/solved-websocket-setup-on-synology/116/15 "2021-04-11T05:39:31Z")

</div>

> [@ncs](#):
>
> Hi everyone,
> 
> I had trouble getting Websocket support on my Bitwarden\_rs Docker + Reverse Proxy Synology setup to work but in the end was able to build a working solution without having to use SSH.
> 
> I’m not sure if my steps will work for everyone but I’ve put them into a note below. Please let me know if you have any feedback or suggestions:
> 
> [Synology Bitwarden\_rs Websocket setup without SSH · GitHub](https://gist.github.com/nstanke/3949ae1c4706854d8f166d1fb3dadc81)
> 
> -Norman

Hello,  
This script make possible websocket notification when using synology DSM Reverse-proxy.  
Thanks for your work.  
I slightly modified the script by setting the ip address instead of localhost to have it working. And add a \ before " for this : "upgrade".  
(I also add some comments, and echo to have a trace in the log)

> <https://gist.github.com/nstanke/3949ae1c4706854d8f166d1fb3dadc81#gistcomment-3692125>

---

_[View the full topic](https://vaultwarden.discourse.group/t/solved-websocket-setup-on-synology/116)._
