starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-07-25 14:00:01 +03:00
Code Issues 32 Packages Projects Releases 18 Wiki Activity

File becomes unavailable after Send modification #981

New Issue
Closed
opened 2026-02-04 23:32:22 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 23:32:22 +03:00
Owner
Copy Link

Originally created by @Nyxtorm on GitHub (Mar 17, 2021).

Subject of the issue

When I create a Send with a file, it works. But if I change the Send's password (for example), the file becomes impossible to download.

Deployment environment

  • Bitwarden_rs version: v1.19.0-b987ba50
  • Web-vault version: v2.19.0
  • Running within Docker: false
  • Internet access: true
  • Uses a proxy: false
  • DNS Check: true
  • Time Check: true
  • Domain Configuration Check: true
  • HTTPS Check: true
  • Database type: SQLite
  • Install method: built from sources
  • Clients used: web vault (for the test)
  • Reverse proxy and version: nginx/1.19.5

Steps to reproduce

  1. Create a Send with a simple .png
  2. Check if you can download it
  3. Make a change (password in my case)
  4. Check if you can download the file again

Expected behaviour

The file should be able to be downloaded after a modification of the Send (change password for example)

Actual behaviour

The file becomes unavailable and its title changes on the Send.

Troubleshooting data

Before modification on the Send :

image

After a change on the Send :

image

Sorry for my bad English and thank you for offering us all this work on this version of Bitwarden!

Originally created by @Nyxtorm on GitHub (Mar 17, 2021). ### Subject of the issue When I create a Send with a file, it works. But if I change the Send's password (for example), the file becomes impossible to download. ### Deployment environment * Bitwarden_rs version: v1.19.0-b987ba50 * Web-vault version: v2.19.0 * Running within Docker: false * Internet access: true * Uses a proxy: false * DNS Check: true * Time Check: true * Domain Configuration Check: true * HTTPS Check: true * Database type: SQLite * Install method: built from sources * Clients used: web vault (for the test) * Reverse proxy and version: nginx/1.19.5 ### Steps to reproduce 1. Create a Send with a simple .png 2. Check if you can download it 3. Make a change (password in my case) 4. Check if you can download the file again ### Expected behaviour The file should be able to be downloaded after a modification of the Send (change password for example) ### Actual behaviour The file becomes unavailable and its title changes on the Send. ### Troubleshooting data Before modification on the Send : ![image](https://user-images.githubusercontent.com/20800786/111450167-6a71c700-8710-11eb-929a-8b13f9bac454.png) After a change on the Send : ![image](https://user-images.githubusercontent.com/20800786/111450219-78274c80-8710-11eb-962c-f5bb7a32c1ea.png) Sorry for my bad English and thank you for offering us all this work on this version of Bitwarden!
OVERLORD added the troubleshooting label 2026-02-04 23:32:22 +03:00
OVERLORD commented 2026-02-04 23:32:31 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Mar 17, 2021):

Fixed in 551810c486

@dani-garcia commented on GitHub (Mar 17, 2021): Fixed in https://github.com/dani-garcia/bitwarden_rs/commit/551810c4862506ed39780850a35ac12df1aca1a9
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear 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
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label troubleshooting
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#981
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?