I have bitwarden_rs installed behind a reverse proxy on unraid. Whenever I try to download an attachment I get “An error has occurred”. Any advice on how to troubleshoot this would be appreciated.
Do you get any errors on the bitwarden_rs log?
Can you check the requests in the browser dev tools?
Usually failure to download attachments is due to a misconfigured DOMAIN env variable
Below are the errors I get in the browser console.
Blockquote
Failed to load resource: the server responded with a status of 400 ()
WebSocketTransport.js:86 WebSocket connection to ‘wss://bitwarden.lemaster.us/notifications/hub?id=3I10B_0prEZ8P2RKrEI9Ow==&access_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJuYmYiOjE1ODQzNzY4NzQsImV4cCI6MTU4NDM4NDA3NCwiaXNzIjoiaHR0cHM6Ly9iaXR3YXJkZW4ubGVtYXN0ZXIudXN8bG9naW4iLCJzdWIiOiIwZDY2NmE5YS1kZjY0LTQwZDItOWVhNy01ZjI0MjFlZDgyNmQiLCJwcmVtaXVtIjp0cnVlLCJuYW1lIjoiTG9ubmllIExlTWFzdGVyIiwiZW1haWwiOiJsbGVtYXN0ZXJAZ21haWwuY29tIiwiZW1haWxfdmVyaWZpZWQiOnRydWUsIm9yZ293bmVyIjpbIjMyMGIyODMwLTI4NWEtNGJkNy05NDJmLTBlYWRmODU1NDc1NyJdLCJvcmdhZG1pbiI6W10sIm9yZ3VzZXI…zIwLWI2YjUtMjlkOTNlOGM3ZTFiIiwiZGV2aWNlIjoiZTA3YzI3ZDQtNzY4Zi00OGZhLThlZmItNGE1ZmZhZGI0NTc2Iiwic2NvcGUiOlsiYXBpIiwib2ZmbGluZV9hY2Nlc3MiXSwiYW1yIjpbIkFwcGxpY2F0aW9uIl19.IGNr1nxVCO9fgTyeSjWBPW0g2XVSirX3RDLqg42V6OfOIjt-IVqsEeDaYsVTcpxEs7WaH-AT_Lo778bcta0o0AdJGgsDJzn_y2cw8NgwuZsbRm4uZMvYIYVCx1Hm47uhoXkBqbb2_Q_a1X6NC-IHL6hrnmNzlxheuhbLQsjoy5yr137kDeZ5N9iGGqfBxw7lRCGSEfLqoegfJQcQN1Ls-d70qVYcqbxCUUeqJYnn6oR921S-Sx9L09IT_8dK3TsNfzqwinjI69no0CyKx4fL4FYxYJechuwkQF0GUEN9MQhAtt3P9sLlOsUaojsFIlglgZEyNmDSwGEkre9hwBfDpA’ failed: Error during WebSocket handshake: Unexpected response code: 400
(anonymous) @ WebSocketTransport.js:86
Utils.js:198 [2020-03-16T16:41:14.633Z] Error: Failed to start the transport ‘WebSockets’: Error: There was an error with the transport.
e.log @ Utils.js:198
Utils.js:198 [2020-03-16T16:41:14.635Z] Error: Failed to start the connection: Error: Unable to connect to the server with any of the available transports. WebSockets failed: Error: There was an error with the transport.
e.log @ Utils.js:198
search.service.ts:71 search indexing: 93.392822265625ms
/attachments/11163058-cac8-4a38-b8b5-63b1d9565573/c1efecc4af23eae6f1cf:1 Failed to load resource: the server responded with a status of 404 ()