Creating a Send File does Not work from browser extension

Help
1

The Send text feature works but the Send file feature does not work, when created from a browser extension (tried Firefox and Chrome). It also does not work from iOS app. Doesn’t look like there are any updates to the browser extensions. I believe the docker is running the latest image.

It does work if you log into the webpage and create the Send file that way.

The log shows this:
[2021-05-17 08:01:12.816][request][INFO] POST /api/sends/file/v2
[2021-05-17 08:01:12.816][response][INFO] 404 Not Found

Versions
Server Installed Ok
1.21.0
Server Latest
1.21.0
Web Installed
2.19.0d
Database
SQLite: 3.33.0

Checks

Running within Docker

Yes

Uses a reverse proxy

Yes

IP header Match

Config/Server: X-Real-IP

Internet access Ok

Yes

Internet access via a proxy

No

DNS (github.com) Ok
Date & Time (UTC) Ok
Domain configuration Match HTTPS

2

I believe the v2 API is from the new browser extension version released a few days ago, and it’s a known issue that Vaultwarden is missing this new API. But the extension should be falling back to the older API for now:

[2021-05-17 18:21:24.840][request][INFO] POST /api/sends/file/v2
[2021-05-17 18:21:24.840][response][INFO] 404 Not Found
[2021-05-17 18:21:24.950][request][INFO] POST /api/sends/file
[2021-05-17 18:21:24.951][multipart::server][INFO] Multipart::with_boundary(_, "----WebKitFormBoundary...")
[2021-05-17 18:21:24.956][response][INFO] POST /api/sends/file multipart/form-data (post_send_file) => 200 OK
3

Thank you for the reply.

Do you mean I should do something to the extension to make it revert back to the v1?

Or do you mean I should try and install an older version of the extension?

4

I mean that it works fine for me on version 1.50.0 of the browser extension.

Are you sure there’s no POST /api/sends/file afterwards, as in my log above?

5

I confirmed I am running Version 1.50.0 of the extension on firefox (for this test).

This is all that appears in the log (set to info).
Previous line is unrelated
[2021-05-17 17:38:08.229][request][INFO] POST /api/sends/file/v2
[2021-05-17 17:38:08.229][response][INFO] 404 Not Found
next line is blank.

attached is a screenshot of the error on the extension

extension-error

6

A 405 error suggests you’ve configured your reverse proxy to block an HTTP method it shouldn’t be blocking, though if you’re blocking POST, a lot of obvious things wouldn’t work, so maybe it’s returning 405 when blocking some other aspect of a request.

7

I think you’re right. Something with the reverse proxy. When I connect directly using the internal IP over 80, I have no problems.

8

Reverting back to extension version 1.49.1 (firefox) makes it all work, again. Sounds like it’s what you were thinking with the v2 API, in extension 1.50?

I’ll stick with the older extension for now.

Thanks for all the help.

9

I have v1.50.0 running, and it works without issues.
So, there is something triggering some blocking on your reverse proxy side either by not allowing POST to some paths, or it triggers some kind of WAF protection because of the first attempt to the v2 path that fails.