-
Notifications
You must be signed in to change notification settings - Fork 1.4k
File attachment upload fails desktop / browser / ios app. "An Error has occured." #14160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thank you for reporting this issue! We've added this to our internal tracking system. |
Hi |
Hi, still facing the same error (v2025.3.0 snap). |
Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. I did want to note that this may be caching related, I had tested this on different clients and saw that when I logged in to a new client (in my case the Bitwarden web interface in an incognito/private browsing window) I was able to view those attachments that I had attempted to upload but received an error or appeared to be uploaded unsuccessfully. @geekitude your behavior matches the issue that is open here: #14150 @matthlsile you mentioned this in the above GitHub issue, I believe these behaviors may be related, but in the case that they are separate issues I will be leaving this issue open as well so we can track reports of both of these issues separately. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again! |
@rmcdowell-bitwarden, thanks for pointing me to the right issue |
I am a long-time bitwarden family plan user. I think this issue is kind of priority. There is something very wrong going on right now. this behavior of the attachments is blocking me from taking a backup of my valut, which is very scary. The attachment shows up in CLI but i am unable to download them from CLI.
|
I'm getting an error when uploading on MacOS (chrome browser and chrome extension) and iOS App. In dev tools it says it's an HTTP 500 error. Please fix this asap! |
I'm affected on all platforms too as well as the web vault. With a HTTP 500 error it is likely a database connection and/or write issue. At least from the error we can deduce it's a server side fault and not client side. |
This is a serious blocker for us. This is core functionality in the Bitwarden product. We may be a start up, Bitwarden is not. I certainly hope this is addressed very quickly because this is a serious problem that never should've made it into production. |
Same issue. This is an absolutely CRITICAL ISSUE. The Bitwarden Service Health should NOT show healthy. IT SHOULD BE RED AND DOWN. Literally WE AS PAYING SUBSCRIBERS CANNOT UPLOAD FILES AND USE THE SERVICE. |
There was a release of the Macintosh native client today. It continues to have the problem. Because of the different context of the problem it seems pretty obvious that this is a backend issue. |
This issue comment is also true for this issue. |
This is happening to me as well. Tried deleting an attachment, all files disappeared. Now 500 error on trying to add any. |
Same issue. Such a critical issue is blocking me from doing my job |
I'd be interested to know if Linux Unified (Beta) self hosted is affected? I'm considering porting out until things stabilise again. |
Steps To Reproduce
Expected Result
File get's uploaded as an attachment after clicking on save.
Actual Result
Red Error card with Error: "An error has occured. An unhandled server error has occured."
File doesn't get uploaded properly.
Screenshots or Videos
No response
Additional Context
Files also can't be uploaded in browser extension (Firefox, Safari and Chrome tested), iOS Bitwarden and in Webvault on bitwarden.com. No error messages there, though.
Operating System
Windows, macOS
Operating System Version
Windows 11 23h2, iOS 18.4, macOS ?
Installation method
Direct Download (from bitwarden.com)
Build Version
2025.3.0
Issue Tracking Info
The text was updated successfully, but these errors were encountered: