Can't get websockets working #2751
Replies: 3 comments 3 replies
-
Hi @nathan-alden-sr . I was about to write how you should use several different clients to test your websockets when I noticed this line.
As far as I know no client needs websockets to log you in, it is just about live-sync that may be available or not depending if your server offers websockets. So this indicates a different problem with your setup. Could you discribe why you are not able to access your vault with other clients than the webvault? |
Beta Was this translation helpful? Give feedback.
-
I keep experiencing intermittent connection issues. I am hosting Vaultwarden on my home network with an Arris BGW210 modem acting as the firewall. I suspect the firewall may not be handling stateful sessions properly, but unfortunately the firmware is crap and I have very little control over this. If anyone has attempted to do this and run into firewall issues, I'd love to hear your experiences. |
Beta Was this translation helpful? Give feedback.
-
I just tested Caddy my self, and it seems to work just fine for me. Anything in between could cause any issue of course. |
Beta Was this translation helpful? Give feedback.
-
I have read virtually every guide including the wiki in this repo, but I simply cannot get websockets working.
I am running Vaultwarden and Caddy in Docker on a Raspberry Pi 4 on my home network, accessible internally and from the internet. Everything works fine, including HTTPS connections and requests/responses; however, all
wss://
URLs fail:Here is my
docker-compose.yml
:Here is my
Caddyfile
:Here's the line from the log I see when I run
sudo docker compose up
:so I know the websockets server is running.
I am able to interact with Vaultwarden as long as I use the browser;
extensions and apps all have trouble even logging inextensions and apps seem to be working now after I fixed the missing Server URL setting (it defaulted tohttp://localhost
).I thought that maybe
wss://
URLs use a different port than 443, which is the only port I am allowing through my AT&T gateway; however, upon researching it it seems that port 443 is used forwss://
, as well.I am not sure how else I can diagnose this issue. Help!
Support string:
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Beta Was this translation helpful? Give feedback.
All reactions