Tom Homewood

I was also having this problem on both iOS and Android (self-hosting bitwarden_rs). Browser add-ons in FF and Chrome continued to sync fine. I tried various older versions of the...

@muzzah I think the difference between our setups is that I'm using the unofficial [bitwarden rust server container](https://github.com/dani-garcia/bitwarden_rs). I settled on this option as I found it easier to setup...

- I have tried Chrome already (v119.0.6045.124), but I get "WebTransportError: Opening handshake failed". I am now using Chrome for my testing, as FF seems to add more issues. -...

I think I made some progress - instead of passing a hostname in the `server` GET param, I tried passing the IP address of the network adapter that WSL is...

I made some more progress today by running everything (relay, publisher and moq-js client) on a Pi4. This worked pretty much out-of-the-box, which is great as it proves that most...

I tried running `mkcert` on the client machine (the machine that will recieved the video stream), but I'm still getting a TLS error 46 during handshake. Below are the steps...

I had some (limited) success by using Firefox. In FF, you can make exception for individual certificates, so I visited https://:4443 whilst the relay was running, and accepted the certificate....

Hi, I'm still not able to get Chrome to accept the self-signed certificate, despite mkcert reporting `The local CA is now installed in the Firefox and/or Chrome/Chromium trust store (requires...