Closed revilo951 closed 1 year ago
Websockets works OOTB with swag, thanks to this default setting https://github.com/linuxserver/docker-swag/blob/master/root/defaults/nginx/proxy.conf.sample#L26. Ensure that your configs are up to date, as your startup log will tell you.
My bad, I missed that.
Thanks for setting me straight.
Fun story, websockets now work on port 80 as of vaultwarden 1.29, so we can actually update the config to replace the port for that. They have kept port 3012 as a fallback for the moment, so nothing is currently broken.
Adds header upgrades needed for websockets to work properly.
Description
Websockets not working correctly using the current template, adding the header upgrades solves that.
Benefits of this PR and context
Working websockets is very handy :)
How Has This Been Tested?
Tested Vaultwarden functions before and after changes, no issues present, websockets working correctly after changes.
Running
vaultwarden/server
andlinuxserver/swag
in docker on Ubuntu Server 20.04.No other areas affected as far as I am able to tell.
Source / References