mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-10 17:23:04 +03:00
Creating Send with type file via CLI doesn't work #55
Reference in New Issue
Block a user
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 @smsteel on GitHub.
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Failed HTTP Checks:
Config:
Vaultwarden Build Version
1.34.3
Deployment method
Official Container Image
Custom deployment method
services:
vaultwarden:
image: vaultwarden/server:latest
container_name: vaultwarden
restart: unless-stopped
environment:
DOMAIN: "https://localhost"
ADMIN_TOKEN: foobar
EXTENDED_LOGGING: true
LOG_LEVEL: trace
volumes:
- ./vw-data/:/data/
ports:
- 8123:80
Reverse Proxy
none
Host/Server Operating System
Linux
Operating System Version
Ubuntu 24.04
Clients
CLI
Client Version
2025.7.0
Steps To Reproduce
Expected Result
Create file works.
Actual Result
While Send with type text works:
Logs
Screenshots or Videos
No response
Additional Context
No response
@smsteel commented on GitHub:
Can confirm that putting behind
traefik"solves" initial problemExample for local development if anyone needs it for some reason:
@BlackDex commented on GitHub:
I have looked into this. And it is not something we can fix.
The Bitwarden CLI client is sending the
connection: closeheader, but it then still tries to use that same connection to send the file, but, since Rocket adheres to thiscloseit closes the connection as requested by the client.This seems a nodejs or rather a node-fetch issue, which has been resolved in v2.6.13 of node-fetch, but Bitwarden seems to still be using v2.6.12, even though both versions are ancient already.
See: https://github.com/node-fetch/node-fetch/releases/tag/v2.6.13
The only solution I can offer is put a reverse proxy in front of Vaultwarden, which most of the time will not send the
connection: closeheader.Since we can not fix this on our side, I'm going to close this.