mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-09 09:13:02 +03:00
Sends - files not uploading - error 61 - no data available #1284
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 @vherrlein on GitHub.
Subject of the issue
Hi,
When you tries to use the send feature through Web UI or iOS app with files and any kind of settings (defaults, different expiry, deletion date and so on), an error occurs with the following message.
Os: { code: 61, kind: Other, message: “No data available” }
Deployment environment
Install method: Kubernetes via Helm Chart
Clients used: web vault, desktop and iOS
Reverse proxy and version: HA Proxy as TCP load balancer in front of Kubernetes cluster + Traefik as reverse proxy
MySQL/MariaDB or PostgreSQL version: Default SQL Lite
Other relevant details:
Steps to reproduce
Using default Send interface, set title and file to upload then click on save.
Expected behaviour
Saving the send record.
Actual behaviour
Error message and the interface stays in the saving form.
error message: Os: { code: 61, kind: Other, message: “No data available” }
Troubleshooting data
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
@vherrlein commented on GitHub:
I tried from :
The error message is the same with any king of file sizes. (From 10KB to 100MB)
@vherrlein commented on GitHub:
Note: Text Sends works as expected.
@BlackDex commented on GitHub:
Looks like your reverse proxy, or cloudflare is blocking something. Either the size is too large or something else. What happens if you try to take cloudflare out of the loop
@vherrlein commented on GitHub:
Sorry for the delay, now I have access to the environment.
Please find below the trace logs.
@BlackDex commented on GitHub:
I Still think it is something locally.
Maybe you can try to enable the trace log_level and see what happens during the uploading of the file.
You should see something like this:
And there will probably be some more
[multipart::server::rows there, depending on the size of the file you upload. So i suggest for the testing to use a very small file.@vherrlein commented on GitHub:
Ho my......
I discovered the main trouble.
My Kubernetes infra had an issue with CoreDNS, a previous maintenance ops removed its config map which put my storage provider "GlusterFS" under an unstable state.
Then when the Pod relying to vaultwarden restarted, it was only able to list partially the persistent disk tree.
The error message "Os { code: 61, kind: Other, message: "No data available" }" came from POSIX commands.
I'm closing that issue.
Thanks allot for your help.
@vherrlein commented on GitHub:
Another tries with:
Debug Version:
Trace Version: