mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #1538] Attachments are broken #995
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#995
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sempervictus on GitHub (Mar 25, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1538
Subject of the issue
Attempting to upload attachments from any browser plugin or the electron app results in the app getting signed out immediately and no attachment uploaded.
Attempting to upload attachments through the bitwarden_rs-web interface results in an
m is nullerror (which is interesting given that its Rust). The session is immediately logged out.Deployment environment
Install method: package
Clients used: web vault, desktop, Android
Reverse proxy and version: Apache HTTPD 2.4.46-3
SQLite-backed
Steps to reproduce
Expected behaviour
Attachments work
Actual behaviour
Session crashes resulting in loss of any unsaved data and forcing a full auth back into the client context (app or web).
@BlackDex commented on GitHub (Mar 25, 2021):
Probably the DOMAIN variable is not configured correctly.
Could you post the support string from the/admin/diagnostics page?
@sempervictus commented on GitHub (Mar 25, 2021):
There is none - this is all there is on that page:
^^ which shows the problem - the package installation doesn't restart the service so there's a version mismatch.
Thanks.
@sempervictus commented on GitHub (Mar 25, 2021):
Turns out its still broken:
Domain configuration and HTTPS show match in diagnostics (not looking to post the URL on github - sort of the point of a private server).
@sempervictus commented on GitHub (Mar 25, 2021):
The diagnostics page is incorrectly saying
Uses a proxy No- there's anhttpdin front of it dealing with TLS.@BlackDex commented on GitHub (Mar 25, 2021):
That is where the support string function is for, so if you could post that, that would help.
Also, the proxy is a check for outgoing, i need to rephrase that.
@sempervictus commented on GitHub (Mar 25, 2021):
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
@sempervictus commented on GitHub (Mar 25, 2021):
The HTTPD proxy:
@BlackDex commented on GitHub (Mar 25, 2021):
The only thing missing is logs from bitwarden_rs during the upload and the error you get. Also maybe the Apache logs.
All the rest looks ok as far as i can tell.
@sempervictus commented on GitHub (Mar 25, 2021):
i'm going to guess Apache is doing something stupid, digging through there, but can probably close this unless i find something pointing to the back-end.
@BlackDex commented on GitHub (Mar 25, 2021):
Not sure if you already checked the wiki, but take a look there.
And if you find anything wrong there feel free to update.